Download FPTBook: Enhancing Book Selection and Management for Bookstores and more Summaries International Law in PDF only on Docsity!
ASSIGNMENT 1 FRONT SHEET
Qualification BTEC^ Level^5 HND^ Diploma^ in^ Business Unit number and title Unit^ 30:^ Application^ Development Submission date 29/5/2023 Date Received 1st submission 29/5/ Re-submission Date Date Received 2nd submission Student Name Vu Minh Hoang Student ID GCH Class GCH1005 Assessor name Nguyen Duc Giang 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 HOANG Grading grid P1 P2 P3 M1 M2 D
Summative Feedback: Resubmission Feedback:
Grade: Assessor Signature: Date:
Version <X.X>
Prepared by
Group Name: < Group 12 >
<GCH200668 #> Huypqgch200668@fpt.edu.vn <GCH200497 #> Hoangvmgch200497@fpt.edu.vn <GCH18499 #> ManhGCH18499@fpt.edu.vn
Instructor: < NGUYEN DUC GIANG>
Course: <1670 >
Date: <29/5/2023 >
Contents
development tools and techniques, specifically focusing on those employed during the development of this application. Additionally, in the design phase, we will utilize selected tools from the previous stage to generate design diagrams for our solution, aligning them with the specified needs.
2. Product Scope.
FPTBook is a web-based software system designed to enhance and expedite the process of selecting, ordering, and purchasing books for customers, while also efficiently managing user and product databases for book store owners. Our goal is to optimize business operations and enhance the overall shopping experience for customers. One of the key responsibilities of our team is to build a website that facilitates user account management for the book-selling system. This includes tasks such as creating, modifying, and deleting user accounts, managing orders, updating order statuses, browsing and selecting products, and placing orders. Our system caters to both administrators and users, specifically catering to the needs of online booksellers.
3.Intended Audience And Document Overview.
The audience for this paper includes programmers, project managers, marketers, users, testers, and writers of documentation. The system will be briefly discussed before the function and demand are examined. By the time everything is said and done, we'll have diagrams showing how the system works, like an ERD, use case diagram, class diagram,... The program mainly has two main users that are: Administrators: Administrators of the FPT bookshop and patrons have utilized this content. They make sure that this information is thorough enough for each task so that users may use the product and comprehend its essential components. User (Customer): Customers will have the right to log in to the system to be able to view products, product prices and have different options to choose from,... The use of software development tools and methodologies, as well as the selection of applications for development, are some of the research's most important topics that will be covered in this article. This
page describes their objectives as well as who may participate in and use them. The characteristics of the products as well as the responsibilities and pursuits associated with each position in the sales system are covered in this section. The product's limitations, which cover hardware, software, and user requirements, come next. Make a high-level model of the user interface to identify potential project risks. The document's reading directions are as follows:
- You might be the owner of a bookshop, a client, or a system developer as an administrator.- Pay close attention to functional elements like "functional necessity" and "use case #."
- FPTBook developers and representatives should read the paper attentively and take notes as they go. The intended readership of this paper includes programmers, project managers, marketers, users, testers, and documentation writers. The paper will provide a brief overview of the system, followed by an analysis of its functions and demands. To illustrate how the system operates, diagrams such as an Entity-Relationship Diagram (ERD), use case diagram, and class diagram will be included. The system primarily caters to two main types of users: Administrators: These are the administrators of the FPT bookshop and other stakeholders who need a comprehensive understanding of the system's features and components to facilitate its effective use. Users(Customer): Customers have the ability to log in to the system, view products, access pricing information, and choose from various options. The paper will delve into important topics such as the use of software development tools, methodologies, and the selection of applications for development. It will also outline the objectives of these tools and who can participate in and utilize them. Additionally, the paper will cover the characteristics and responsibilities associated with each position in the sales system. Furthermore, the paper will address the limitations of the product, encompassing hardware, software, and user requirements. A high-level model of the user interface will be created to identify potential project risks. The recommended reading approach for different individuals is as follows: Bookshop owners, clients, and system developers (administrators) should pay close attention to functional elements such as "functional necessity" and "use case #."
programmer to think of before. Maybe that's also a trend that current programming languages are heading towardsBootstrap is a free collection of open source and tools for creating a complete webiste template. With predefined interface properties such as size, color, height, width, etc., designers can create many new products but still save time when working with this framework in the process. web interface design. ERD Entities Relationship Diagram The erd model is abbreviated by the word Entity Relationship Diagram, which is understood as the association entity model, also known as the associated entity. This model is also known as er (short for Entity Relationship model). SRS Software requirements specification SRS document is an acronym for Software Requirement Specification, translated into Vietnamese as a requirements specification document. SRS is a document used to describe the functional and non-functional requirements of a
system in detail. UML Unified Modeling Language UML (Unified Modeling Language) is a language for the specification, visualization, construction, and documentation of software systems. UML provides an opportunity to write system designs, including concepts such as business processes and system functions. In particular, it is useful for declarative languages, database schemas, and reusable software components. UML was developed by Rational Rose and several collaborating groups, it quickly became one of the standard languages for building Object Oriented software systems. It is a worthy successor to modeling languages such as Booch, OOSE/Jacobson, OMT and several others. Bootstrap Bootstrap Bootstrap is a free collection of open source and tools for creating a complete webiste template. With predefined interface properties such as size, color,
Figure 1 : Flowchart
2.Product Functionality.
In our system, the functions are all doing a different job so each job has a separate function: User:
- Register Admin:
- View all accounts
- View account detail - Edit account detail
- Delete account
- Add new account Staff:
- View all products
- View product detail
- Edit product detail
- Delete product
- View all orders
- View orders detail
- Accept orders
- Reject orders Customer:
- View all products
- Search products
4.Class Diagram.
5. ERD.
Figure 3 Erd Chart III. Specific Requirements.
1.Functional Requirements.
ID AS A I WANT TO < PERFORM SOME TASK > So That I can
Customer Review all my orders View what I have purchased in the past Customer Manage all product Add new products or modify old one Customer Manage all category Add new category or modify old one Customer Manage all author Add new or modify old one Customer Manage all publisher Add new or modify old one Customer View and take order Decide to take order or refuse
2. Use Case Model.
Figure 4 Use Case diagram Based on our group's Use Case diagram, the system will involve three main roles: Customer, Admin, and Staff. The user will first register for an account and log in. Based on the transmitted data, the system will determine the role of the registered user account and provide them with the appropriate functions and interfaces. These functions for each role will include:
