Higher Nationals in Computing
WEBG301: WEB Project
ASSIGNMENT
Learner’s name: Lê Đặng
Đan Duy ID: GCS210811
Class: GCS1101
Subject code: WEBG301
Assessor name: PHAN MINH TAM
Assignment due: Assignment submitted:
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
Guidelines and tips
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
Web Application Development for Car Sales Platform, Schemes and Mind Maps of Web Application Development
The design and development of a car sales web platform, detailing the system architecture, database schema, and user interface. It covers key functionalities such as car listings management, search and filter options, payment and transaction processing, and security measures. The document also emphasizes the use of php frameworks and the mvc architecture for efficient development and maintainability. It further discusses database management tools like sql and their role in handling customer data and product information. The document also addresses user roles, use cases, and system requirements, ensuring a user-friendly and secure environment for browsing, comparing, and purchasing vehicles. The document concludes with advantages and disadvantages of the project, highlighting areas for improvement such as coupon management and security enhancements. (447 characters)
Typology: Schemes and Mind Maps
2024/2025
1 / 66
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Web Application Development for Car Sales Platform and more Schemes and Mind Maps Web Application Development in PDF only on Docsity!
Higher Nationals in Computing
WEBG301: WEB Project
ASSIGNMENT
Learner’s name: Lê Đặng
Đan Duy ID: GCS
Class: GCS
Subject code: WEBG
Assessor name: PHAN MINH TAM
Assignment due: Assignment submitted:
ASSIGNMENT FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title WEBG301: WEB Project Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission
- T ống Anh Tu nấ 1. GCS Group members
- Vũ Nh tậ Minh
- Lê Đ ngặ Đan Duy Student ID
- GCS
- GCS
- Tr ần Vũ Hào 4. GCS Class Assessor name Phan Minh Tam 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 P M D
Table of Contents Contents WEBG301: WEB Project ASSIGNMENT......................................................................................................... 1 Chapter 1: Introduction...................................................................................................................................... 5 1.1 Background information.......................................................................................................................... 5 1.2 Project aim and objectives..................................................................................................................... 6 Chapter 2 ................................................................................................................................................................ 8 Literature Review................................................................................................................................................. 8 2.1....................................................................................................................Introduction ......................................................................................................................................................................... 8 2.2.................................................................................................................SDLC model ..................................................................................................................................................................... 8 2.2.1..................................................................................................Introduction to SDLC .................................................................................................................................................................. 8 2.2.2................................................................................................Type of SDLC models .................................................................................................................................................................. 9 2.2.3...................................................................................SDCL model applied in project .................................................................................................................................................................. 9 2.3............................................................................................................ MVC architecture ....................................................................................................................................................................... 11 2.3.1..................................................................................................Intruduction to MVC ................................................................................................................................................................ 11 2.3.2..........................................................................................Main components in MVC ................................................................................................................................................................ 12 2.4............................................................................................................ PHP Frameworks ....................................................................................................................................................................... 13 2.4.1.......................................................................................... What is PHP Framework? ................................................................................................................................................................ 13 2.4.2.....................................................................................Why use a PHP Framework? ................................................................................................................................................................ 13 2.5..............................................................................................Common PHP Frameworks ....................................................................................................................................................................... 14 2.5.1.............................................................................PHP Framework is used in project ................................................................................................................................................................ 15 2.6........................................................................................................................Database ....................................................................................................................................................................... 15
2.6.1..............................................................................................Introduction Database ............................................................................................................................................................... 15 2.6.2............................................................................................Common tool Database ................................................................................................................................................................ 16 2.6.3...................................................................Select Database tool for CarSale project ................................................................................................................................................................ 16 2.7.....................................................................................................Techniques and Tools ....................................................................................................................................................................... 18 2.7.1...................................................................................................MySQL Workbench ................................................................................................................................................................ 18 2.7.2...................................................................................................................... GitHub ................................................................................................................................................................ 19 2.7.3.................................................................................................... Visual Code Studio ................................................................................................................................................................ 20 Chapter 3 ............................................................................................................................................................. 22 Requirements Analysis.................................................................................................................................... 22 3.1....................................................................................................... User’s requirements ....................................................................................................................................................................... 22 3.1.1........................................................................................... Functional requirements ................................................................................................................................................................ 22 3.1.2....................................................................................Non-Functional requirements ................................................................................................................................................................ 22 3.2.........................................................................................................................Use case ....................................................................................................................................................................... 24 3.2.1.....................................................................................................Use case diagram ................................................................................................................................................................ 24 3.2.2..............................................................................................Use Case specification ................................................................................................................................................................ 24
maintained a stringent change management procedure throughout the development process to guarantee that modifications were appropriately evaluate, approve, and recorded to protect the platform’s integrity.
1.2 Project aim and objectives Web-based Car Sales Platform: The aim of this project is to develop a comprehensive, user-friendly web platform for buying and selling cars. The platform will provide an efficient and secure environment where users can browse, compare, and purchase vehicles, as well as list their own cars for sale. It will cater to individual buyers and sellers, as well as car dealerships. Project Objectives
- User Interface and User Experience: Design a clean, intuitive interface that ensures an excellent user experience. Implement responsive design to ensure compatibility across various devices (desktops, tablets, smartphones).
- User Registration and Authentication: Develop a secure user registration system with email verification. Implement authentication mechanisms to protect user accounts and personal information.
- Car Listings Management: Enable users to create, edit, and delete car listings. Allow users to upload images and videos of their cars. Provide detailed forms for users to input car specifications (make, model, year, mileage, price, etc.).
- Search and Filter Functionality: Implement advanced search functionality allowing users to search for cars based on various criteria (price range, make, model, year, mileage, etc.). Provide filtering options to narrow down search results.
- Detailed Car Pages: Create detailed car pages displaying all relevant information about each vehicle. Include photo galleries, videos, and user reviews on car pages.
Implement notification systems to inform users about new messages, updates on their listings, etc.
- Payment and Transaction Management: Integrate secure payment gateways to facilitate online transactions. Implement a transaction management system to track the buying and selling process.
- Reviews and Ratings: Allow buyers and sellers to leave reviews and ratings. Display ratings and reviews on user profiles and car listings to build trust within the community.
- Administrative Tools: Develop an admin dashboard for managing users, listings, and transactions. Implement moderation tools to review and approve car listings and user activity.
- Data Security and Privacy: Ensure data encryption and secure storage of user information. Comply with relevant data protection regulations and privacy laws.
- Analytics and Reporting: Implement analytics tools to track user behavior and platform performance. Provide reporting features for users to monitor their listings' performance and for administrators to analyze overall platform usage.
- Marketing and SEO: Optimize the platform for search engines to increase visibility. Develop marketing tools to help sellers promote their listings.
- Scalability and Performance: Ensure the platform is scalable to handle increasing user traffic and data. Optimize the platform for fast loading times and
reliable performance.
- Customer Support: Integrate customer support features, including live chat and a comprehensive FAQ section. Provide resources and assistance for users encountering issues with the platform.
completion within time and cost estimates, and works efficiently and effectively in the current and planned Information Technology infrastructure.
2.2.2 Type of SDLC models
- WaterFall mode: This mode follows a linear process, the steps will be performed in sequence order.
- Agile model: is a flexible software development model. Aim to be able to bring product quickly to customers. When it comes to problem or upgrades, the agile model makes the product easy to adapt.
- Spiral model: This is a flexible software development that requires iterations in multiple cycles. This mode mainly makes it easier to manage risks and how to overcome them.
- V-shape model: Aim to create quality product. Help us save time thank to implementation in stages, if there is an error we can fix it.
- Scrum model: The Scrum model is an effective method appplied by any business in project management and software development. The Scrum process allows teams to smoothly align customer requirements quickly and in line with evolving business goals. 2.2.3 SDCL model applied in project We choose the Agile model to incorporate into the Car Store project Flexibility and Adaptability
- Changing Requirements: In a Car Store project, customer preferences, market trends, and business needs can change frequently. The Agile model allows for easy adaptation to these changes, enabling the project team to respond swiftly and effectively.
- Iterative Development: Agile’s iterative cycles, known as sprints, allow for continuous reassessment and adjustment, ensuring that the project evolves in alignment with new insights or changes. Customer-Centric Approach
- Frequent Customer Feedback: Agile emphasizes regular feedback from customers and stakeholders. In a Car Store project, this ensures that the product is continuously aligned with customer needs and expectations, leading to higher customer satisfaction.
- Incremental Delivery: By delivering the product in small, usable increments, customers can see tangible progress early and provide feedback, ensuring the final product meets their requirements. Improved Collaboration and Communication
- Cross-Functional Teams: Agile promotes collaboration across different teams (e.g., developers, designers, marketing). This is
- Daily Standups and Regular Meetings: Continuous communication helps in identifying and resolving issues quickly, ensuring that the project remains on track. Risk Management
- Early Detection of Issues: Agile’s iterative nature allows for regular testing and review of the product, enabling the early identification and resolution of issues. This reduces the risk of major problems late in the project lifecycle.
- Prioritization of Features: By focusing on delivering the most important features first, Agile ensures that the highest value elements of the Car Store are completed, even if time or resources become constrained. Faster Time-to-Market
- Continuous Delivery: Agile allows for continuous integration and delivery of features, enabling the Car Store to launch critical functionalities sooner. This can be crucial in a competitive market where early entry can provide a significant advantage.
- MVP Development: Agile supports the creation of a Minimum Viable Product (MVP), allowing the Car Store to go live with core features and add enhancements over time based on user feedback. Enhanced Quality
- Regular Testing and Refinement: Agile promotes continuous testing and improvement, ensuring that each iteration of the product is of high quality. This is essential for a Car Store, where a bug-free and user- friendly interface is critical for customer trust and satisfaction.
- Refactoring: Agile encourages regular refactoring of the codebase, ensuring that the software remains clean, maintainable, and scalable. Employee Engagement and Satisfaction
- Empowered Teams: Agile methodologies empower teams to take ownership of their work, leading to higher job satisfaction and better performance.
- Continuous Learning: The iterative nature of Agile encourages continuous learning and improvement, keeping the team engaged and
motivated.
2.3.2 Main components in MVC 2.3.2.1 Model Figure 2: MVC architecture pattern 2.3.2. View
- The object that we want to manage within a system. We can simply understand that it is similar to entity relationship. For example, in the project we have managed the following objects. A model is equivalent to an object inside the database.
- Role: is the bridge between the view and the controller. It has important functions such as retrieving, modifying data, deleting or adding data from the database.
- The front-end display, View is the part that shows the user about the request results and the system’s function.
- Role: is the display bridge and user interaction with the system. View plays the role of describing the functions of the controller in the most optimal way. Besides, the view supports displaying results when controller interact with the model. 2.3.2.3 Controller
- The part that processes information through receiving user requests, retrieving data from the model, processing data and outputting results.
- Role: obviously the controller plays the role of the central
handling of the system user’s request. Controller is understood as the back-end. As a bridge to the model (database), processing and display control.