Download Assignment 2 for Application Development - 1670 and more Assignments Web Application Development in PDF only on Docsity!
ASSIGNMENT 2 FRONT SHEET
Qualification BTEC Level^5 HND Diploma in Business
Unit number and title Unit 30: Application Development
Submission date Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Phan Minh Tri Student ID GCD
Class GCD0904 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 Phan Minh Tri
Grading grid
P 4 P5 P6 M3 M4 M5 D2 D
Summative Feedback: Resubmission Feedback:
Grade: Assessor Signature: Date:
Internal Verifier’s Comments:
Signature & Date:
Table of Contents
- Chapter 1 – Introduction
- Chapter 2 – Peer Review and Feedback Analysis
- solution, and development strategy I. Formal questionnaire to reviews the business application, problem definition statement, proposed
- II. Collect review feedbacks
- III. Interpret peer – review feedbacks
- IV. Evaluate any new insights, ideas potential improvements
- Chapter 2 – Application Development
- I. Folder structure of the application
- II. Source code samples of the application with explanation
- Overview and wireframe of the application
- Customer Role
- Store Owner Role
- Admin Role.................................................................................................................................................
- III. Final screenshots of the application
- Customer Role
- Store Owner Role
- Admin Role.................................................................................................................................................
- IV. Screenshots of using GitHub to manage the source code
- V. Screenshots of using Azure for the application deployment..........................................................................
- Chapter 3 – Application Evaluation
- I. Review the performance of the application
- II. Conclude whether the application adapts all requirements, or it needs to be improved later
- III. Analyze the factors that influence the performance of the application
- Factors affecting performance of application
- Analyse the phase
- Evaluation
- IV. Evaluate the strengths and weaknesses of the application
- Chapter 5 – Conclusion
- Figure 1: Survey form for the application Table of Figures
- Figure 2: Consumer initial impressions and what they enjoy most about our system.
- Figure 3: What consumers are least interested in and the most problematic aspect of our system.
- Figure 4: Overall evaluation of the customer
- Figure 5: Feedbacks of customers about experiment
- Figure 6: Folder Structure
- Figure 7: Properties folder
- Figure 8: wwwroot folder
- Figure 9: Areas folder..................................................................................................................................................
- Figure 10: Controller folder
- Figure 11: Data folder
- Figure 12: Model folder
- Figure 13: View Model
- Figure 14: appsettings file...........................................................................................................................................
- Figure 15: Program file
- Figure 16: Role class....................................................................................................................................................
- Figure 17: Overview of the system
- Figure 18: Wireframe for login form...........................................................................................................................
- Figure 19: Wireframe for Book Index
- Figure 20: Wireframe for Category Request
- Figure 21: Wireframe of Register form
- Figure 22: View Book Index
- Figure 23: Add to Cart Function
- Figure 24: Checkout Function
- Figure 25: Create new Category Function
- Figure 26: Create new Book function
- Figure 27: Confirm request function...........................................................................................................................
- Figure 28: Reject request function
- Figure 29: Customer Home Page
- Figure 30: Register Page
- Figure 31: Customer Function
- Figure 32: Cart Page
- Figure 33: Previous Order of customer.......................................................................................................................
- Figure 34: Detail Order Page
- Figure 35: Store Owner Home Page
- Figure 36: Manage Book Page
- Figure 37: Order List of customers
- Figure 38: Manage Category Page
- Figure 39: Admin Home Page
- Figure 40: Manage Customer Page
Chapter 2 – Peer Review and Feedback Analysis
I. Formal questionnaire to reviews the business application, problem definition statement, proposed solution, and development strategy
❖ After presenting and describing the functionalities of the FPT Book Store application to consumers
who see and shop at the system, they will have some suggestions based on the customer's point
of view. Opinions and comments are formed after studying your business application and
corresponding explanations of issue identification, suggested solution, and strategy formulation.
❖ We've created the type of questions below to gather consumer feedback on the system and their
suggestions for future improvements.
Figure 1 : Survey form for the application
II. Collect review feedbacks
❖ We get data regarding how clients feel after interacting with our system after gathering feedback
from 50 different individuals.
❖ The first set of data are regarding consumer initial impressions and what they enjoy most about
our system.
Figure 2 : Consumer initial impressions and what they enjoy most about our system.
❖ Following that will be data on what consumers are least interested in and the most problematic
aspect of our system.
Figure 3 : What consumers are least interested in and the most problematic aspect of our system.
❖ 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.
Because this is a freshly established system,
connecting with banks or other businesses to offer
payment services is very challenging. As a result,
the payment method on receipt will be employed
in the system's early phases.
The interface of the system looks quite confusing
because it displays everything on the screen and
does not follow any standards
To provide a more natural perspective, we want to
present prominent books on the system's home
page and all books accessible in the system when
the user visits the book page.
The application looks to be using the system's
default design, which makes it too simplistic and
incapable of attracting new clients.
We utilized the bootstrap library to support the
system's decorating, and we used it to redecorate
based on its original design so clients can view it
very easily and without the essential qualities.
When I register new account and login by this
account, I can't add book to cart
After logging in, the user may only add books to the
cart after seeing the information on the site, or
they can add books straight from the book page.
I can't add another book to my cart once I've added
a book to it.
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 IV. Evaluate any new insights, ideas potential improvements
❖ Following the collecting of survey responses, we chose the following remarks to enhance our
system:
Feedback from customer Expected solution of our teams
I'd want to be able to utilize alternative
payment options when purchasing a book
instead of only cash on delivery.
We will endeavor to integrate our system with domestic
banks and major e-wallets so that clients may use the
system using online payment methods.
I believe you should redesign your system
to attract more consumers.
To fulfill Search Engine Optimization (SEO) criteria and
attract new clients, we will remodel all the system's pages
using our own ideas.
After I've put all the books I desire to my
cart, the system should allow me to go to
the order page.
When a client adds a book to the cart, the system displays
the number of books added to the cart so that the
consumer may see and change the cart at any moment.
Table 2 : Review ideas of customers
Chapter 2 – Application Development
I. Folder structure of the application Figure 6 : Folder Structure
❖ The Properties folder includes a launchSettings.json file that provides all the information needed
to launch the application. Configuration data describing what action to do when the program is
performed, including IIS settings, application URLs, authentication, SSL port information, and so
on.
Figure 7 : Properties folder
❖ Controller oversees all incoming requests. This folder contains all of the controllers required for
the project. Controllers oversee managing end-user interaction, changing the model, and selecting
a view to show the UI. Each controller class derives from a Controller or ControllerBase class. Each
controller class has "Controller" as a suffix on the class name; for example, the default
"HomeController.cs" file may be found here. As seen below.
Figure 10 : Controller folder
❖ The Data folder is including all migrations when we change the database and ApplicationDbContext
file which is used for setting all tables in database.
Figure 11 : Data folder
❖ A Model represents the application's data, while a ViewModel represents the data that will be
shown in the user interface. All domain or entity classes are stored in the model’s folder. Please
keep in mind that the user may add folders of his own to the project to make logical grouping.
Figure 12 : Model folder
❖ A view is the user interface that shows ViewModel or Model data and allows the user to edit it.
Typically, a folder with the name of the controller is established, and any views linked to it are kept
in it. As seen below, BookController related view Index.cshtml is stored in Book folder.
Figure 13 : View Model
II. Source code samples of the application with explanation
- Overview and wireframe of the application
❖ We suggested utilizing Heroku in Assignment 1 to make releasing our system simpler, however we
made a mistake. Because Heroku does not support ASP.NET, we modified our project design to use
Microsoft Azure instead of Heroku for this publication.
Figure 17 : Overview of the system ❖ MockFlow is what I use to create the wire frames for each page of our application. Figure 18 : Wireframe for login form
Figure 19 : Wireframe for Book Index Figure 20 : Wireframe for Category Request Figure 21 : Wireframe of Register form
❖ Once you've put the books you desire to your cart, the checkout function will assist you in
completing your order.
Figure 24 : Checkout Function
- Store Owner Role
❖ Using the below method, the store owner may create a new category and submit it to admin for
approval or rejection.
Figure 25 : Create new Category Function
❖ After a new category is accepted for inclusion in the system, the shop owner may use the function
below to add a new book to the system with that category.
Figure 26 : Create new Book function
