WEBG301 GCS190905 huynh trần anh khoa assignment

54 26 0
WEBG301 GCS190905 huynh trần anh khoa  assignment

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

Thông tin tài liệu

Higher Nationals in Computing WEBG301 WEB Project ASSIGNMENT Name Huỳnh Trần Anh Khoa ID GCS200252 Class GCS0905C Subject code WEBG301 Assessor name PHAN MINH TAM Assignment due Assignment submitted A.

Higher Nationals in Computing WEBG301: WEB Project ASSIGNMENT Name: Huỳnh Trần Anh Khoa ID: GCS200252 Class: GCS0905C Subject code: WEBG301 Assessor name: PHAN MINH TAM Assignment due: Assignment submitted: ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title WEBG301: WEB Project Submission date Aug 15th, 2022 Re-submission Date Date Received 1st submission Date Received 2nd submission Nguyen Gia Huy GCS200801 Tran Nhat Minh Student Name GCS190905 Student ID 3 GCS200252 Huynh Tran Anh Khoa GCS200396 Nguyen Phu Quang Class GCS0905C 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 HUY  Summative Feedback: Grade: Signature & Date:  Resubmission Feedback: Assessor Signature: Date: Table of Contents WEBG301: WEB Project ASSIGNMENT Chapter 1: Introduction 1 Background information Project aim and objectives Chapter 2: Literature Review Introduction 2 SDLC model 2.1 Introduction to SDLC 2.2 Type of SDLC 2.3 SDCL applied in the project MVC architecture PHP Frameworks 4.1 What is PHP Framework? 4.2 Why use a PHP Framework? 4.3 Common PHP Frameworks 4.4 PHP Framework is used in the project Database Techniques and Tools 11 Chapter 3: Requirements Analysis 1 User’s requirements Use case diagram 2.1 Use case 2.2 Use Case specification Gantt chart Chapter 4: Design 1 Site map Database design 2.1 Database diagram 2.2 Data dictionary WireFrame design 3.1 User interface 3.2 Admin interface Chapter 5: Implementation 11 Application screenshots 11 Sample source code 19 2.1 View 19 2.2 Model 20 2.3 Controller 21 GitHub Repository 23 Chapter 6: Conclusion 24 What went well 24 What did not go well? 25 Lessons learned and further improvements 25 REFERENCES 26 Chapter 1: Introduction Background information Our four-person team was given a job involving web design by the lecturer We agreed on a topic for "MotoBike-Shop" following a meeting and debate as a group Following considerable deliberation, we determined that our website would sell and showcase home furnishings-related goods Our website is a furniture sale and showcasing website Customers may now buy furniture online thanks to this technology The system provides customers with complete product details, including the maker, brand, and cost Users of the system must register by providing personal data After signing up, the user may use the system by logging in with his username and password The customer may select a product and put it in their shopping basket Payments can be made by users with a Visa card, cash, or an electronic wallet, for instance Users may locate furniture based on each company's collections, and they may learn more about the subject of furniture through the "Blog." To reply to client queries, we have a separate page that provides our contact information To attract customers, we also provide certain special coupons When a customer makes a purchase, they may also track the status of their order and the delivery fee Graphical user interface that works well Users may check the features of each product and compare them to choose a better product Project aim and objectives The primary purpose of the project is to develop a software package that allows the sale and administration of home furnishings items This has been divided into six major objectives, which are as follows: • Allows companies to show and sell furniture-related items The system's implementation • Manage product details such as brand, quantity, and status • Product data statistical analysis • Order management • Evaluate the new system's performance Does it offer a better purchasing and order management experience? Page |1 Chapter 2: Literature Review Introduction There are several software lifecycle development models available today, with three typical SDLC techniques being the waterfall methodology, iterative development, and component-based software engineering In this study, our team will explain the techniques as well as discuss some of the reasons for their creation SDLC model 2.1 Introduction to SDLC The Software Development Life Cycle (SDLC) model is a conceptual framework for project management that delineates each stage of a software development project, from planning to maintenance This process is tied to several models, each of which includes a variety of duties and actions It typically consists of six steps: ideation and planning, requirements collecting, design and prototyping, software development, testing and integration, implementation and deployment, and operation and maintenance Depending on the size of the project, some project managers may combine, divide, or omit processes 2.2 Type of SDLC 2.2.1 Waterfall Model Page |2 The Waterfall Paradigm is a sequential model for software development that separates it into predefined phases Each phase must be completed before moving on to the next, with no gaps between them Each phase is meant to accomplish a particular activity during the SDLC phase Winston Royce first debuted it in 1970 2.2.2 Agile model The agile SDLC model is a combination of iterative and incremental processes focusly on customer satisfaction by rapidly delivering a working software product In this model, every process are being cut down to small builds Cross-functional teams are required to be working simultaneously on various areas such as: Planning, analysis, design, coding, unit, and acceptance testing At the end of the process, a working product will be displayed to the customer and stakeholders Page |3 2.2.3 Spiral The Spiral Model is a risk-based approach to software development It is a hybrid of the waterfall and iterative approaches The Spiral Model assists in adopting software development aspects from several process models for software projects based on unique risk patterns, resulting in an efficient development process In the SDLC Spiral model, the development process begins with a limited set of requirements and progresses through each development phase for those needs Until the program is ready for production, the software engineering team adds functionality for the new demand in ever-increasing spirals Spiral Model is illustrated in the diagram below: Page |4 2.2.4 Prototyping model The Prototyping Model is one of the most popularly used Software Development Life Cycle Models (SDLC models) This model is used when the customers not know the exact project requirements beforehand In this model, a prototype of the end product is first developed, tested and refined as per customer feedback repeatedly till a final acceptable prototype is achieved which forms the basis for developing the final product 2.3 SDCL applied in the project Our team chose to use the waterfall mode because this is a small project with few complicated functions The reason why our team chose this model is that: • This model is appropriate for a small group of individuals • Easily collects, records, and organizes work • Easily creates shared goals for the planning and documentation stages •Timelines and deadlines that are clearly stated MVC architecture A data model, presentation information, and control information are required for an application to follow the Model View Controller (MVC) architectural pattern Each of them must be separated into separate things in accordance with the pattern MVC is more of an architectural pattern than a complete program The UI/interaction layer of an application is a key focus of MVC You will still require a business logic layer, maybe a service layer, and a data access layer Page |5 P a g e | 12 1.2 Cart page: P a g e | 13 1.3 Checkout page: P a g e | 14 1.4 Login page: 1.5 Login admin page: P a g e | 15 1.6 Admin main page: 1.7 Category: P a g e | 16 1.8 Product Brand: 1.9 Product Supplier: P a g e | 17 1.10 Product: P a g e | 18 Sample source code 2.1 View Some source code in View file ✓ Add product Brand page P a g e | 19 ✓ Edit Category page 2.2 Model Some source code in Model file ✓ Admin P a g e | 20 ✓ Articles 2.3 Controller Some source code in Controller file ✓ Admin controller P a g e | 21 ✓ Brand controller P a g e | 22 GitHub Repository The source code to this project can be found at: https://github.com/giahuygwf/CarLaravel.git/ P a g e | 23 Chapter 6: Conclusion What went well In this project we have created a relatively complete website Our website is mainly about selling transportation vehicles such as electric-gasoline motorbikes, and electric bicycles This is a commercial transaction site In this project we have created the basic items of the website such as: Home page, in the home page contains categories and images to help customers easily track and search for products • The accompanying information pages contain detailed content about products, functions, and features of vehicles • The detail page helps customers to choose the product type, color, and quantity of products • After the customer has selected the type, color, and quantity of the product The website will take customers to the shopping cart page, where customers can check the products, they have selected and proceed to choose payment methods • For users to be able to search for products quickly, we have created a search bar so that customers can type the information of the products they are looking for • To manage the website effectively, we have created a dedicated admin page to manage the data on the website To be able to manage the website, we have created functions such as: • We have created functions to create, update, edit and delete product information such as brand, product name, supplier Besides, we also create an order function to be able to manage customer orders • In addition, we also create a customer information management function • To manage the administrators, we have also created a function that is decentralized This function helps the main admin manage smaller admins and assign separate management rights for each department P a g e | 24 What did not go well? Although our team has been designing a website that can be most convenient and easy to use for customers However, our website still has many restrictions such as about maketing we have not added yet but promotional offers for products Besides, security is also an issue that our team needs to better Lessons learned and further improvements During the development of the project, our team learned a lot of new knowledge and learned the importance of decentralization in web management, understood more about different types of frameworks used in development project Our website still has a lot of shortcomings, in the future, if possible, we want to improve, upgrade, and add some functions to help customers make purchases more efficiently and easily such as: • Improve the security of the website, the security of customer information • Besides, applying 3D projection technology to allow customers to observe the product 360 degrees • Add features to automatically answer customers' basic inquiries about detailed product information P a g e | 25 REFERENCES Tutorialspoint PHP Frameworks [online] Available at: https://www.tutorialspoint.com/symfony/symfony_introduction.htm [Accessed 12 August 2022] Tutorialspoint PHP Frameworks [online] Available at: https://www.tutorialspoint.com/symfony/symfony_introduction.htm [Accessed 12 August 2022] GeeksForGeeks MVC design pattern [Online] Available at: https://www.geeksforgeeks.org/mvc-designpattern/ [Accessed 10 August 2022] GeeksForGeeks Software Engineering | Classical Waterfall Model [Online] Available at: https://www.geeksforgeeks.org/software-engineering-classical-waterfall-model/ [Accessed 11 August 2022] Posey.2011 Sever Hardware (online) Available at: https://techgenix.com/Server-Hardware-ExplainedPart1/ [Accessed April 4, 2022] Williams.2022 Operating system(online) Available at: https://www.guru99.com/operating-systemtutorial.html [Accessed April 4, 2022] Kali.2018 Web server softwares and purpose of them(online) Available at: https://webhostinggeeks.com/blog/what-are-web-servers-and-why-are-they-needed/ [Accessed April 4, 2022] Tutorials.2017 How to publishing and accessing a website on Internet ? Available at: https://www.tutorialspoint.com/internet_technologies/website_publishing.html [Accessed April 4, 2022] Cademy.2019 What is front end ? Available at: https://www.codecademy.com/resources/blog/what-isfront-end/ [Accessed April 4, 2022] 10 GeeksForGeeks Software Engineering | Classical Waterfall Model [Online] Available at: https://www.geeksforgeeks.org/software-engineering-classical-waterfall-model/ [Accessed 11 August 2022] P a g e | 26 ... Minh Student Name GCS190905 Student ID 3 GCS200252 Huynh Tran Anh Khoa GCS200396 Nguyen Phu Quang Class GCS0905C Assessor name Phan Minh Tam Student declaration I certify that the assignment submission.. .ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title WEBG301: WEB Project Submission date Aug 15th, 2022... Signature & Date:  Resubmission Feedback: Assessor Signature: Date: Table of Contents WEBG301: WEB Project ASSIGNMENT Chapter 1: Introduction 1 Background information

Ngày đăng: 03/12/2022, 15:05

Tài liệu cùng người dùng

Tài liệu liên quan