Assigment 2 - Application Development - Pass, Assignments of Computer Science

Download Assigment 2 - Application Development - Pass and more Assignments Computer Science in PDF only on Docsity!

Huynh Minh Huy

GCD1001 | UNIVERSITY OF GREENWICH

Assignment 2

APPLICATION DEVELOPMENT

ASSIGNMENT 2 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 30: Application Development

Submission date 28/04/2023 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name Huynh Minh Huy Student ID GCD

Class GCD1001^ Assessor name Nguyen Van Loi

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 (^) Huy

Grading grid

P4 P5 P6 M3 M4 M5 D2 D

Acknowledgement

First and foremost, I want to thank the curators at the University of Greenwich for making these courses available to students. I would like to thank all of the writers and researchers who worked on this data. I would also want to thank teacher Nguyen Van Loi for his excellent and professional lectures and tutorials. Finally, I would like to thank our university's lecturers and responsible personnel for offering an excellent learning atmosphere.

Table of Contents

II. Conclude whether the application adapts all requirements or it needs to be improved later.

• CHAPTER 1: INTRODUCTION.
• CHAPTER 2: PEER REVIEW AND FEEDBACK ANALYSIS.
  • proposed solution and development strategy. I. Formal questionnaire to reviews the business application, problem definition statement,
  • II. Collect review feedbacks.
  • III. Interpret peer – review feedbacks.
• CHAPTER 3: APPLICATION DEVELOPMENT.
  • I. Folder structure of the application.
  • II. Source code samples of the application with explanation.
    • 1. Overview and wireframe of the application.
    • 2. Customer Role.
    • 3. Store Owner Role.
    • 4. Admin Role.
  • III. Final screenshots of the application.
    • 1. Customer Role.
    • 2. Store Owner Role.
    • 3. Admin Role.
  • IV. Screenshots of using Github or GitLab to manage the source code.
  • V. Screenshots of using IIS or Azure for the application deployment.
• CHAPTER 4: APPLICATION EVALUATION.
  • I. Review the performance of the application.
• CHAPTER 5: CONCLUSION.
• Figure 1: Survey form for application........................................................................................................................... Table of Figures
• Figure 2: First Question......................................................................................................................................................
• Figure 3: Second Question.................................................................................................................................................
• Figure 4: Third Question.
• Figure 5: Fourth Question.
• Figure 6: Fifth Question......................................................................................................................................................
• Figure 7: Seventh Question.
• Figure 8: Eighth Question.
• Figure 9: Feedbacks of customers about experiment.
• Figure 10: Folder structure of the application.
• Figure 11: Properties folder.
• Figure 12: wwwroot folder.
• Figure 13: Areas folder.
• Figure 14: Controller folder.
• Figure 15: Data folder.
• Figure 16: Mail folder.
• Figure 17: Migration folder...............................................................................................................................................
• Figure 18: Model folder.
• Figure 19: View folder.
• Figure 20: appsettings.json file.
• Figure 21: appsettings.Development.json file.
• Figure 22: Program file.......................................................................................................................................................
• Figure 23: Initialize file.
• Figure 24: libman.json file.
• Figure 25: Overview of the system.
• Figure 26: Wireframe for home page............................................................................................................................
• Figure 27: Wireframe for login form.
• Figure 28: Wireframe for register form.
• Figure 29: View Book Index..............................................................................................................................................
• Figure 30: Store Owner Layout.
• Figure 31: View category request in detail function.
• Figure 32: Create category request function.
• Figure 33: Edit category request function.
• Figure 34: Delete category request function..............................................................................................................
• Figure 35: View and search customer function.
• Figure 36: View detail customer's information function.
• Figure 37: Display all book in database.
• Figure 38: View book detail in store owner page.
• Figure 39: Create new book in store owner page.
• Figure 40: Edit book in store owner page.
• Figure 41: Delete book in store owner page.
• Figure 42: Display all order from customer.
• Figure 43: Admin main layout.
• Figure 44: View category in details.
• Figure 45: Create category in admin.
• Figure 46: Edit category in admin.
• Figure 47: Delete category in admin.
• Figure 48: Display list of role.
• Figure 49: Create role.
• Figure 50: Update role.
• Figure 51: Delete role..........................................................................................................................................................
• Figure 52: View detail category request in admin.
• Figure 53: Approve category request.
• Figure 54: Create new manager.
• Figure 55: View details of all user in application.
• Figure 56: Disable user account.
• Figure 57: Activate user account when they have been unbanned.
• Figure 58: Reset password function for user.............................................................................................................
• Figure 59: Customer Home Page.
• Figure 60: Register Account.
• Figure 61: Register Confirmation.
• Figure 62: Option 1 - Confirm account in website.
• Figure 63: Option 2 - Confirm account in email.
• Figure 64: Login Page..........................................................................................................................................................
• Figure 65: Home page when the customer login successfully into our website.
• Figure 66: Login via email.
• Figure 67: Login via email confirmation......................................................................................................................
• Figure 68: Login link have been sent to customer email.......................................................................................
• Figure 69: Forgot password.
• Figure 70: Forgot password confirmation.
• Figure 71: Link to reset password.
• Figure 72: Reset password page.
• Figure 73: Profile setting page.
• Figure 74: Manage email....................................................................................................................................................
• Figure 75: Change password.
• Figure 76: Setup two-factor authentication.
• Figure 77: Instructions how to setup 2FA.
• Figure 78: Manage Personal Data...................................................................................................................................
• Figure 79: Book page for customer.
• Figure 80: Product detail.
• Figure 81: Product cart.......................................................................................................................................................
• Figure 82: Checkout page.
• Figure 83: Order page.
• Figure 84: FAQs page.
• Figure 85: Home page for store owner.
• Figure 86: Option for store owner.
• Figure 87: Manage book.
• Figure 88: Create book.
• Figure 89: View in detail.
• Figure 90: Edit book information.
• Figure 91: Edit price success.
• Figure 92: Delete book........................................................................................................................................................
• Figure 93: Manage category request.
• Figure 94: Create category request.
• Figure 95: View each category in detail.
• Figure 96: Edit category request.
• Figure 97: Delete category request................................................................................................................................
• Figure 98: View the customer’s information.
• Figure 99: View customer’s information in detail include the ordered of that customer.
• Figure 100: Manage order.
• Figure 101: Home page for admin when they login into the system................................................................
• Figure 102: Admin Option.
• Figure 103: Manage role.
• Figure 104: Create new role success.
• Figure 105: Edit and Update.
• Figure 106: Edit & Update success.
• Figure 107: Delete role name...........................................................................................................................................
• Figure 108: Manage User Page.
• Figure 109: Add new store owner.
• Figure 110: Add store owner success.
• Figure 111: View user's information in details.
• Figure 112: Disable account.
• Figure 113: Disable success.
• Figure 114: Reset Password.
• Figure 115: Manage Category.
• Figure 116: Create new category....................................................................................................................................
• Figure 117: View detail category.
• Figure 118: Edit Category..................................................................................................................................................
• Figure 119: Edit category success.
• Figure 120: Delete Category.
• Figure 121: Delete success.
• Figure 122: View category request.
• Figure 123: View request in details.
• Figure 124: Option: Approve.
• Figure 125: Approved success.
• Figure 126: Make new request.
• Figure 127: New request from store owner.
• Figure 128: Option 2: Reject.............................................................................................................................................
• Figure 129: Rejected success.
• Figure 130: GitHub Project Home Page.
• Figure 131: All git commit.
• Figure 132: All branch have been merged into project.
• Figure 133: Deploy project by Azure.
• Figure 134: Authorize the Azure app with github account.
• Figure 135: Configure networking..............................................................................................................................
• Figure 136: Configure monitoring.
• Figure 137: Configure Tags............................................................................................................................................
• Figure 138: View detail.
• Figure 139: Deployed successfully.
• Figure 140: Performance of the system.

CHAPTER 1: INTRODUCTION.

The FPT Bookstore System is a web-based software program created to assist bookstore patrons and proprietors in managing their book purchases and sales by streamlining and accelerating the procedures for patrons to choose, order, and buy books as well as for proprietors to manage a user database and a product database. After the Software Requirements Specification document was completed, this three-section document was created to keep track of and collect data throughout the whole development phase of the FPT Bookstore project.  Peer Review and Feedback Analysis.  Application Development.  Application Evaluation.

CHAPTER 2: PEER REVIEW AND FEEDBACK ANALYSIS.

I. Formal questionnaire to reviews the business application, problem definition statement, proposed solution and development strategy. They will have some recommendations based on the viewpoint of the customer after presenting and outlining the features of the FPT Book Store application to customers who inspect and use the system. After reviewing your business application and the associated explanations of issue identification, possible solution, and strategy formulation, opinions and comments are formed. We've created the type of questions below to gather consumer feedback on the system and their suggestions for future improvements. Here is the link to google form which is the form that we used to conduct the data from the survey: https://forms.gle/N6njYpmAwwZPmUaf

Figure 1: Survey form for application.

II. Collect review feedbacks. We conducted a survey of 50 users who have been and continue to interact with our system. Below is the data that we have collected from the reviews, comments and as well as user feelings.

Figure 2: First Question.

Figure 4: Third Question.

The data shows that the majority of respondents (62%) rated their satisfaction levels as a 3 or 4 out of 5, indicating they were moderately satisfied with the products they received. However, a sizeable proportion of respondents (24%) rated their satisfaction levels as a 1 or 2 out of 5, suggesting that they were dissatisfied with their purchase. This feedback is valuable for us to improve on product quality and customer satisfaction. Understanding the reasons behind the dissatisfaction can help us make necessary improvements to prevent such negative experiences in the future.

Figure 5: Fourth Question.

It can be observed from the data that 76% of respondents rated their likelihood of recommending the website and store as either a 3 or 4 out of 5, indicating that they were relatively positive about sharing their experience with others. However, a significant percentage of respondents (18%) rated

their likelihood of recommending as a 1 or 2 out of 5, suggesting that they were not satisfied with their experience. We should take this feedback seriously and make necessary improvements to improve customer satisfaction levels and increase the likelihood of customers recommending their website and store to others.

Figure 6: Fifth Question.

Here are some problems that user encountered when they visit our website. We will look into all the problems that users face to quickly fix and provide a good user experience.

Figure 7: Seventh Question.

III. Interpret peer – review feedbacks. These are some suggestion from users of our system, although there some negative suggestion but we will always listen to users to be able to bring the best experience.

Figure 9: Feedbacks of customers about experiment. Review feedback of the customers. Feedback of customer Review by our teams I can't pay for my order by using online method Visa, Debit, PayPal, etc.

Connecting with banks or other companies to provide payment services is quite difficult because the system is so new. Therefore, in the early stages of the system, the payment method on delivery will be temporarily unavailable. The interface of the system looks quite confusing because it displays everything on the screen and does not follow any standards.

We want to display notable books on the system's home page and all books available in the system when a user visits the book page in order to present a more realistic perspective.

The application looks to be using the system's default design, which makes it too simplistic and incapable of attracting new clients.

We have used CSS to support system decoration and we have used it to redecorate based on its original design so that customers can view it very easily and without the necessary qualities. And in the future, we will update the CSS frameworks for the system to replace the CSS which becomes relatively difficult to maintain the system look and feel. When I register new account and login by this account, I can't add book to cart.

After logging in, the user can either add books directly from the book page or only after viewing the content on the website. I can't add another book to my cart once I've added a book to it.

You mean when you added a book to the cart and you want to add that book again? When a consumer adds a book to the shopping cart, the system displays the shopping cart for the user to validate the book they have just added, and they may raise or reduce the amount or remove the product they do not like. Table 1: Review feedback of customers.