














































Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Describe to the code of Web Development
Typology: Study Guides, Projects, Research
1 / 54
This page cannot be seen from the preview
Don't miss anything!















































Summative Feedback: Resubmission Feedback:
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
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)
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.
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.
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.
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)
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.