Download Application Development .Net Assignment 2 (P+M+D) and more Assignments Web Application Development in PDF only on Docsity!
Tran Nguyen Tan Sang GCS190019 GCS0803A
APPLICATION DEVELOPMENT
ASSIGNMENT 2 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Business
Unit number and title Unit 30: Application^ Development
Submission date September 2021 Date Received 1st submission
Re-submission Date September 2021 Date Received 2nd submission
Student Name Tran Nguyen Tan Sang Student ID GCS
Class GCS0803A Assessor name Thai Thi Thanh Thao
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand
that making a false declaration is a form of malpractice.
Student’s signature
Grading grid
P4 P5 P6 M3 M4 M5 D2 D
Assignment Brief 2 (RQF) Higher National Certificate/Diploma in Computing
Student Name/ID Number: Tran Nguyen Tan Sang / GCS
Unit Number and Title: Unit 30: Application Development
Academic Year: 2021 – 2022
Unit Assessor: Thai Thi Thanh Thao
Assignment Title: Application development with design diagrams and code
Issue Date: September 2021
Submission Date: September 2021
Internal Verifier Name:
Date:
Submission Format:
Format:
- An individual report document in PDF
Submission
- Students are compulsory to submit the assignment in due date and in a way requested by
the Tutor.
- The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/.
- Remember to convert the word file into PDF file before the submission on CMS.
Note:
- The individual Assignment must be your own work, and not copied by or from another student.
- If you use ideas, quotes or data (such as diagrams) from books, journals or other sources,
you must reference your sources, using the Harvard style.
- Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to
comply this requirement will result in a failed assignment.
Unit Learning Outcomes:
LO3 Work individually and as part of a team to plan and produce a functional business application with
support documentation
LO4 Evaluate the performance of a business application against its Software Design Document and
initial requirements
Assignment Brief and Guidance:
Assignment scenario (continued from Assignment 1) Your team has finished the analysis and design for
the system. Next task is development of the system.
Tasks:
After the presentation about your design (from Assignment 1), you need to create a formal
questionnaire that effectively reviews your business application, problem definition statement,
proposed solution and development strategy. This formal questionnaire should be answered by your
colleagues. For any new insights, ideas or potential improvements to your system you need to evaluate
and justify the reasons why you have chosen to include (or not to include) them as part of this business
application. Based on the feedback of your colleagues, amend the design if needed.
Next task is to develop the business application based on the design, chosen technologies and
methodology. When the application is fully built and tested, you need to review its performance
against the Software Requirement Specificationn, analyze the factors that influence its performance
and use them to undertake a critical review of the design, development and testing stages of your
application. Conclude your review by reflectively discussing your previously identified risks. You should
evaluate the strengths and weaknesses of your business application and fully justify opportunities for
improvement and further development.
To conclude, your report document should include:
- Peer review section (questionnaire and answers, your reflection on the feedback)
- Development section (how you develop and test the application, what is the result)
- Review section (review, analyse and critical evaluate your application)
Your team needs to prepare a demo based on this report for the final
demonstration. The working application must also be demonstrated.
Table of Contents
Introduction In this report, we will demonstrate how to deploy the application based on the requirements and SRS that has been deployed previously. From the Peer-review feedback, the exploitation problems of SRS have been corrected and added to the requirements of the system to develop optimally to deliver to customers. Besides, the final product, FPT Learning System, will be deployed to the cloud computing service of IIS. The strengths and weaknesses of the system will be analyzed for development for the next version.
Chapter 1 – Peer Review and Feedback Analysis
- Formal questionnaire to reviews the business application No. Module Question 1 Website Layout In your mind, this application interface should be only built for laptop devices, desktop computers or even mobile devices. Figure 1 Question 1 2 Cookie To make it easier to use the login, do you think the application should save a cookie ("Remember me" function) for easier login later? Figure 2 Question 2 3 Delete data Is it necessary to notify the message to confirm the deletion of a data on the website? Figure 3 Question 3
- Collect review feedbacks Figure 8 Result of Question 1 Figure 9 Result of Question 2
- Introduction..........................................................................................................
- Chapter 1 – Peer Review and Feedback Analysis
- Formal questionnaire to reviews the business application
- Collect review feedbacks
- Interpret peer-review feedbacks
- Evaluate any new insights, ideas or potential improvements
- 4.1. Make website to be responsive:
- 4.2. Use cookie to save login data:
- 4.3. Show confirm notification before deleting:
- 4.4. Create trash:
- 4.5. Login with Google API:
- 4.6. Assign tasks for Training staff:
- 4.7. Improve assigning course function:
- Chapter 2 – Application Development................................................................
- Folder structure of the application
- 1.1. System workflow
- 1.2. Database.......................................................................................................................................................
- 1.3. System structure...........................................................................................................................................
- Source code samples of the application with explanation
- 2.1. Login
- 2.2. View list of accounts
- 2.3. Create account
- 2.4. Edit Account
- 2.5. Delete Account
- 2.6. Assign course to Trainer and Trainee
- 2.7. Logout
- Final screenshots of the application
- 3.1. Identity
- 3.2. Training Staff management
- 3.3. Trainer management
- 3.4. Trainee management
- 3.5. Category management
- 3.6. Course management.....................................................................................................................................
- 3.7. Assign course to trainer
- 3.8. Assign course to trainee
- 3.9. Logout
- 3.10. Change password
- 3.11. Trainer view courses
- 3.12. Trainee view courses
- Screenshots of using GitHub or GitLab to manage the source code
- Screenshots of using IIS or Azure for the application deployment
- Chapter 3 – Application Evaluation
- Performance of the application
- later 2. Conclude whether the application adapts all requirements or it needs to be improved
- 2.1. Compare application with requirement........................................................................................................
- 2.2. System improvement
- Analyze the factors that influence the performance of the application
- The strengths and weaknesses of the application
- 4.1. Strengths
- 4.2. Weakness
- Conclusion
- References
- Figure 1 Question Table Of Figures
- Figure 2 Question
- Figure 3 Question
- Figure 4 Question
- Figure 5 Question
- Figure 6 Question
- Figure 7 Question
- Figure 8 Result of Question
- Figure 9 Result of Question
- Figure 10 Result of Question
- Figure 11 Result of Question
- Figure 12 Result of Question
- Figure 13 Result of Question
- Figure 14 Result of Question
- Figure 15 Bootstrap
- Figure 16 Remember me
- Figure 17 Delete confirmation
- Figure 18 Trash................................................................................................................................................................
- Figure 19 Sign in with GG API
- Figure 20 Question 6 result..............................................................................................................................................
- Figure 21 Ajax application
- Figure 22 System workflow.............................................................................................................................................
- Figure 23 Database
- Figure 24 System structure
- Figure 25 MVC Architecture
- Figure 26 Razor pages
- Figure 27 Manager Area
- Figure 28 Model
- Figure 29 Migration
- Figure 30 Login (Get)
- Figure 31 Login (POST)
- Figure 32 List of Trainees................................................................................................................................................
- Figure 33 List of Training Staffs
- Figure 34 List of Trainers
- Figure 35 Create Trainee account
- Figure 36 Edit Account....................................................................................................................................................
- Figure 37 Edit account
- Figure 38 Delete account
- Figure 39 Assign course to Trainee and Trainer..............................................................................................................
- Figure 40 Assign course to Trainer and Trainee (POST)
- Figure 41 Logout
- Figure 42 Result - login
- Figure 43 List of Training Staffs
- Figure 44 Create training staff
- Figure 45 Edit Training Staff
- Figure 46 Delete Training Staff
- Figure 47 View Training Staff profile
- Figure 48 List of Trainers
- Figure 49 Create Trainer..................................................................................................................................................
- Figure 50 Edit Trainer
- Figure 51 Delete Trainer..................................................................................................................................................
- Figure 52 Trainer Profile
- Figure 53 List of Trainees................................................................................................................................................
- Figure 54 Create Trainee
- Figure 55 Edit Trainee
- Figure 56 Delete Trainee
- Figure 57 View Trainee Profile
- Figure 58 List of Categories
- Figure 59 Create Category
- Figure 60 Edit Category
- Figure 61 Delete Category
- Figure 62 List of Courses
- Figure 63 Create Course
- Figure 64 Edit Course
- Figure 65 Delete Course
- Figure 66 Assign Trainer to Course.................................................................................................................................
- Figure 67 Assign Trainee to Course
- Figure 68 Logout
- Figure 69 Change Password
- Figure 70 Trainers view their courses
- Figure 71 Trainees view their courses
- Figure 72 Source code on Github
- Figure 73 IIS
- Figure 74 Add website and local domain
- Figure 75 Set up IIS Profile
- Figure 76 Cloud
- Figure 10 Result of Question
- Figure 11 Result of Question
- Figure 12 Result of Question
function to ensure that the data will be managed better. Interpret feedback 5: Using Google API is very necessary because it make our system become more security. Almost user want the system use GG API for Sign in function. Interpret feedback 6: According to the user, they want Trainer and Trainee management should be managed by Training Staff, not both Admin and Training Staff. Interpret feedback 7: Assigning multiple courses to trainer at the same time is very convenient because if not it will take us so much time to do this task.
- Evaluate any new insights, ideas or potential improvements 4.1.Make website to be responsive: Base on the survey results, I decide to use Bootstrap library to solve this problem. Why using Bootstrap? - Time-saving - Easy to use - Responsive Grid System - Customizable - Cross-Browser Compatibility - Establish Consistency - Open-Source - Huge Number of Resources and Community Support Figure 15 Bootstrap 4.2.Use cookie to save login data: "Remember Me" is typically used to remember the email address/user name of the user that logs in, so they only need to enter their password on subsequent visits. Contrary to other answers, I would say that the password is almost certainly not remembered as a matter of practice. Alternative forms of this are "remember my email" or "remember user name", which makes it clear that they will need to enter their password again. This function is usually (more or less) safe on a public device; while it shows the username, the person would need to also know the password to access a given account.
Figure 16 Remember me 4.3.Show confirm notification before deleting: Before proceeding to delete data, the system should notify the user to confirm that the user really wants to delete or not to avoid unexpected data loss. Figure 17 Delete confirmation 4.4.Create trash: It is because sometimes we accidentally delete some important data which we are in need. So, this feature help to undo it. It is helpful while showing others that you have deleted their pic or data from your handset and he or she will not able to recognize whether you have deleted or moved that to bin. You can permanently delete that data by going to Bin option menu or Trash option menu.
Figure 20 Question 6 result According to the results of question 6, the management of trainers and trainees should be reserved for training staff only, not for both admin and training staff. 4.7.Improve assigning course function: Assigning multiple courses at the same time to users will optimize the work rather than assigning each person to each science. To solve this problem, I decided to use Ajax technique to be able to create a dynamic list that makes adding more courses more flexible. Figure 21 Ajax application Chapter 2 – Application Development
- Folder structure of the application 1.1.System workflow
Figure 22 System workflow 1.2.Database