ASM2 1670 web development, Study Guides, Projects, Research of Web Application Development

Describe to the code of Web Development

Typology: Study Guides, Projects, Research

2021/2022

Uploaded on 12/08/2023

tuan-anh-djang
tuan-anh-djang 🇻🇳

5

(3)

2 documents

1 / 54

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
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
Đăng Tuấn Anh
Student ID
GDH210341
Class
GCH1101
Assessor name
Đinh Đức Mnh
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
Anh
Grading grid
P4
P5
P6
M3
M4
M5
D2
D3
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36

Partial preview of the text

Download ASM2 1670 web development and more Study Guides, Projects, Research 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 Lê Đăng Tuấn Anh Student ID GDH

Class GCH1101^ Assessor name Đinh^ Đức Mạnh

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 Anh

Grading grid

P4 P5 P6 M3 M4 M5 D2 D

Summative Feedback:Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Figure 1. Survey question(1) ...................................................................................................................................... 5 Figure 2. Survey question(2) ...................................................................................................................................... 6 Figure 3.Survey question(3) ....................................................................................................................................... 7 Figure 4. Answer question 1 ....................................................................................................................................... 8 Figure 5. Answer question 2 ....................................................................................................................................... 8 Figure 6. Answer question 3 ....................................................................................................................................... 8 Figure 7.Answer question 4 ....................................................................................................................................... 9 Figure 8.Answer question 5 ....................................................................................................................................... 9 Figure 9. Answer question 6 ....................................................................................................................................... 9 Figure 10. Answer question 7 .................................................................................................................................. 10 Figure 11. Answer question 8 .................................................................................................................................. 10 I/ INTRODUCTION

In assignment 1, I designed and analyzed the bookstore e-commerce website with 3

main roles as well as providing various diagrams, technologies, and mockups relating to the

database,

function, and interface of the system. The system is expected to support many modern and

convenient

functions for customers to be able to buy books rapidly. Regarding store owners and admin, it also

offers a

range of management tools relating to accounts, books, categories, and orders, making them easily

control

the system.

In assignment 2, a document with 3 sections was written to provide readers a piece of insightful

information about the bookstore system. In order to explain the system, I will present it in

thefollowing

order:

  • Peer review and feedback analysis
  • Application development
  • Application evaluation II/ PEER REVIEW AND FEEDBACK ANALYSIS (P4)
  1. Formal questionnaire to review the business application, problem definition statement, proposed solution, and development strategy. My purpose is to develop an e-commerce application that can provide a convenient and enjoyable shopping experience for book lovers. However, my team is lacking knowledge about

satisfying customers' experience and ways to improve their trust in the system. Therefore, a formal questionnaire will be designed to assist my team to gain new insights, ideas, and potential improvements to my system. Below is my formal questionnaire: Figure 1. Survey question(1)

Figure 3 .Survey question(3)

  1. Collect review feedbacks. Figure 4. Answer question 1 Result of the question number one is quite positive, with 50% of people satisfied and 30% very satisfied with the functions of the system. Figure 5. Answer question 2 Result of the question number two is also positive, with 80% of participants rating 4 or 5 for the performance of the system. Figure 6. Answer question 3

Figure 10. Answer question 7 In question 7, customers almost did not encounter any problems when up to 80% said there were no difficulties and there were only a few cases of problems when paying. Figure 11. Answer question 8 The results of question 8 were positive, with 80% of participants rating their satisfaction with the service and website as 4 or 5.

  1. Interpret peer-review feedback
    • Interpret question 1: Through the results obtained from the first question, with 50% of participants selecting 4 grade and 30% among them selecting max grade - grade 5, we can conclude that the functions of the system met customers' basic demands. However, there are also a few people who think the system is lacking some different functions, so we will provide more functions in the next update.
    • Interpret question 2:

The bar graph shows positive feedback from the participants, with 60% of them choosing level 4 and 20% of them choosing level 5. We conclude that the performance of the system is quite optimal, so we will continue to keep the performance constant.

  • Interpret question 3: From the results obtained from the survey, the user experience with the normal interface is nothing short of impressive with 50% of participants choosing a score of 3 and only 30% 20% of participants choosing a score of 4 and 5.
  • Interpret question 4: Through feedback from participants, we found that the easy to buy of the bookstore system are the most care to you feature that helps our e-commerce website attract customers. So, we will take a plan in the near future to develop this.
  • Interpret question 5: In question 5, most people agree that the convenience of the system and the of the books are the two factors that influence their purchase intention. So, we decided to make the book-buying process simpler with functions that make them control their order conveniently such as removing an item in their cart, removing all items in their cart, or increasing the quantity of the item.
  • Interpret question 6: The result of question 6 reveals that most people search for their desired books by the title of the book the book but I still have function search for author and category. Therefore, we will build functions for search books by title , author and category.
  • Interpret question 7: Most people think our system is working fine don't have difficult , but there are also some who think that the performance of the system doesn't work well and needs improvement.
  • Interpret question 8: The results from question 8 have with % of them choosing level 4 and 20% of them choosing level 5 it means customer satified the service also web online bookstore. In general, thanks to feedback, we discovered opportunities not previously considered such as the ability to track order function. So, in the next update, we will support all functions that customers expected from our system. I gained a lot of useful recommendations from participants and we try to build a book-selling system that can meet the expectations and recommendations of our customers as below: ➢ Send a notification when users successfully make an order to ensure that their orders were processed ➢ Ensure that the website is mobile-friendly and has a responsive design that adjusts to different screen sizes. ➢ Make sure the search functionality is robust and allows users to easily find the books they're looking for by title, author, genre, or keyword. ➢ Provide a seamless and easy-to-use checkout process that includes multiple payment options. ➢ Offer fast and reliable shipping options with tracking and delivery notifications to keep users informed about the status of their orders.

c. Make the website to be responsive

A responsive website provides a better user experience for customers. It ensures that the website is accessible and easy to use on any device, whether it's a desktop computer, tablet, or mobile phone. This can lead to increased customer satisfaction and loyalty. In this part, we will use Bootstrap a popular front-end framework that provides a set of predesigned CSS components to build responsive websites and applications. Bootstrap provides a mobile-first approach to web design, meaning that the framework is optimized for smaller screens first and then scales up to larger screens.

d. Send a notification when customers order

A notification confirms that the customer's order has been received and is being processed, which can help reduce anxiety and provide peace of mind. Moreover, customers appreciate being kept informed about their orders and are more likely to be satisfied with their overall shopping experience.

III / APPLICATION DEVELOPMENT (P5)

  1. Folder structure of the application

ASP.NET Core is a popular web development framework that is widely used for building scalable and robust web applications. It follows the Model-View-Controller (MVC) pattern, which provides a clear separation of concerns between the different components of the application. In our e-commerce application for selling books online, we have used ASP.NET Core to implement the platform. The layout structure of the application is quite easy to see, thanks to the MVC pattern. The application consists of several key folders, including Data(Models), Controllers, and Views. The Data folder contains 3 roles, Admin and Owner , Customer, which are responsible for handling the different roles in the platform. The Data folder is where the database is connected and where all the data access logic is stored also contains all the objects that are stored in the database, including books, users, and orders. The Controllers folder is where all the user's controllers are located. These controllers are responsible for handling incoming requests from users and returning the appropriate response. Finally, the Views folder contains the user interface, which is responsible for rendering the HTML that is displayed to users. Overall, the use of ASP.NET Core in our e-commerce application for selling books online provides several key benefits, including scalability, robustness, and a clear separation of concerns. By following the MVC pattern and organizing the application into different folders and roles, we have created a platform that is easy to understand, maintain, and scale as needed.

Inside this method, you are defining the initial data that will be inserted into the database. This is typically done to provide some default records for tables, often used during development or for initializing a new database. User Data: The code defines initial data for the Users table. It creates three user records with their respective properties such as user_id, name, username, password, email, phone, address, role, and image_url. Category Data: Initial data for the Categories table is also defined. It creates two category records with properties like category_id and name. Product Data: The code provides initial data for the Products table. It creates several product records with properties like product_id, user_id, category_id, name, author, description, quantity, price, and image_url. Each product represents a book and includes details such as name, author, description, quantity, price, and an image URL. Data for Other Tables: The code snippet shown here focuses on the Users, Categories, and Products tables, but similar data seeding logic could be applied to other tables in your database as well. In summary, this code is an extension method for Entity Framework Core's ModelBuilder used to populate the database with initial data for users, categories, and products. This data will be inserted into the respective tables when the database is created or when migrations are applied. It's a common practice for setting up initial data for testing or application initialization.

using System.ComponentModel.DataAnnotations;: The first line includes the System.ComponentModel.DataAnnotations namespace, which is commonly used for defining data validation attributes and annotations. public class Users: This line defines a class named Users. This class represents user information in the application. [Key]: The [Key] attribute is used to specify that the user_id property is the primary key of this entity. In other words, it uniquely identifies each user in the database. The following properties represent user information: user_id: An integer property representing a unique identifier for the user. name: A string property representing the user's name. username: A string property representing the user's username. password: A string property representing the user's password (note that in practice, passwords should be stored securely, typically hashed). email: A string property representing the user's email address. phone: A string property representing the user's phone number. address: A string property representing the user's address. role: A string property representing the user's role or permissions within the system. image_url: A string property representing the URL of the user's profile image.