Assignment 1 Application Development - MERIT, Assignments of Web Application Development

Download Assignment 1 Application Development - MERIT and more Assignments Web Application Development 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 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name Phan Minh Tiến Student ID GCD

Class GCD1001^ Assessor name Nguyễn^ Văn Lợi

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 Tiến

Grading grid

P1 P2 P3 M1 M2 D

 Summative Feedback:  Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

• I. INTRODUCTION
  • 1. Product Purpose
  • 2. Product scope
  • 3. Intended audience and document overview
  • 4. Definitions, Acronyms and Abbreviations
  • 5. References and acknowledgment.........................................................................................................................
    • a) References
    • b) Acknowledgments
• II. OVERAL DESCRIPTION (P1)
  • 1. Product Overview
  • 2. Product function
  • 3. User Characteristic
  • 4. Design and Implementation Constraints
  • 5. Assumptions and Dependency
• III. SPECIFIC REQUIREMENT
  • 1. Functional Requirement
  • 2. Use Case Model
  • 3 WireFlow(P1)
    • a) User Interface
    • b) Wireflow
• IV. TECHNICAL DESIGN (M1)
  • 1. Entity Relationship Diagram
  • 2. Class Diagram
  • 3. Activity Diagram
  • 4. Gantt Chart
• V. Risk Assessment......................................................................................................................................................
• VI. EVALUATION REPORT (P3-M2)
  • 1. Design tools.........................................................................................................................................................
    • a) What is UML?
    • b) Draw.io............................................................................................................................................................
    • c) Lucidchart
  • 2. Tool to design User Interface(UI)
    • a) Wondershare Mockitt
    • b) Figma
    • c) Maze
    • d) Wireframe.cc
  • 3. Front End technology stack.................................................................................................................................
    • a) Front End Programming Language
    • b) JavaScript Library / Framework
    • c) CSS framework
    • d) Conclude which Front End technologies will be used for the development
  • 4. Back-end Technology Stack
    • a) Back-end Programing Language
    • b) Operating System
    • c) Database
    • d) Frameworks
    • e) Conclude which Back End technologies will be used for the development
  • 5. Tool for source control management:
    • a) Git, GitHub, GitLab, etc
  • 5. Hosting
  • 6. Software Development Model............................................................................................................................
    • a) Introduce several SDLC models: Scrum, Waterfall, V-model, etc...................................................................
  • 7. Illustrate all your findings on how to use these by drawing the overview
• References
• Figure 1: System workflow Table of Figures
• Figure 2: UC Model
• Figure 3: Register new account page
• Figure 4: Login page
• Figure 5: Detail Book page
• Figure 6: Home Page
• Figure 7: List of book page
• Figure 8: Create new book page
• Figure 9: Create new Store page
• Figure 10: Manage your store.....................................................................................................................................
• Figure 11: View history of customer order
• Figure 12: Check book in the Cart before Order
• Figure 13: Admin Screen
• Figure 14: Account Management Screen
• Figure 15: Wireflow
• Figure 16: Entity Relationship Diagram
• Figure 17: Class Diagram
• Figure 18: Activity Diagram
• Figure 19: Gantt Chart
• Figure 20: What is Unified Modeling Language?
• Figure 21: Draw.io
• Figure 22: Lucidchart
• Figure 23: Wondershare Mockitt
• Figure 24: Figma
• Figure 25: Maze
• Figure 26: Wireframe.cc
• Figure 27: Common Front-end programing language
• Figure 28: Common javascript library
• Figure 29: Trending CSS framework............................................................................................................................
• Figure 30: Java
• Figure 31: CSharp (C#).
• Figure 32: Window operating system
• Figure 33: Linux Operating system
• Figure 34: What is database?......................................................................................................................................
• Figure 35: Laravel
• Figure 36: Microsoft .net framework..........................................................................................................................
• Figure 37: git
• Figure 38: github
• Figure 39: GitLab
• Figure 40: Heroku
• Figure 41: Azure
• Figure 42: Software Development Model
• Figure 43: Overall chart of operating model of internal training manage

I. INTRODUCTION

This is a project that we created to build a web-based system to manage book management activities for members who want to sell books online or who want to buy books online. Specifically, this system can be used to manage customer and seller accounts of the course. Moreover, the system also helps users to manage books, orders, and carts.

This section provides an overview of the content of the SRS document. The purpose of this document is to describe the sections, the functions, the tools used, and the list of acronyms and definitions provided. While describing high-level product features, it also focuses on the skills stakeholders require to meet their needs. This document contains comprehensive system requirements and below will be my report.

1. Product Purpose

After identifying the customer's requirements, we have started to design and implement the project, but to perfect the product in the best way, we have written this document to collect and analyze ideas, possible errors and system requirements in relation to customers. Furthermore, we also need to look at how developers anticipate the applications, the usage of the product to better understand the concepts outline the project and organize it for later development. As well as generated ideas can also be discovered but discarded for the sake of product development. In summary, the purpose of this SRS document is to provide a comprehensive overview of the software product, its parameters and goals. The project's target audience, as well as the user interface, hardware and software requirements, are described in this document. It establishes customer, team and audience perception of the product and its capabilities. It then assists any designer or developer in software development life cycle (SDLC) processes.

2. Product scope

FPTBook will provide store owners and buyers with the ability to manage transactions between them, making the transaction as simple as possible, while the store owner also has the ability to manage his/her book inventory. Admin can manage accounts of Customer and Store Owner, FPTBook will work well on any device suitable for all types of users.

3. Intended audience and document overview

We wrote this Software Requirements Specification with the main purpose of presenting our system, clearly about the functions, database diagrams, or possible bugs of the program that we have not known yet the name. This is considered a report, a relatively complete product of our team. The intended audience of this document is focused on customers who are bookstore owners or those who want to find a reputable bookstore that can read our brochure so that they can easily communicate. , use it, there are also some people involved in project development such as investors, and the production team (requirement group). requirements, etc) requirements analyst, design team, member of the development organization, ..) can also read references on this.

4. Definitions, Acronyms and Abbreviations

No Acronyms Abbreviations 1 UI User Interface 2 SL Seller 3 CUS Customer 4 SRS Software Requirement Specification 5 CRUD Create, Read, Update, Delete 6 ERD Entity Relationship Diagram 7 MVC Model-View-Controller 8 UC Use Case

5. References and acknowledgment

a) References

Without the assistance and direction of several resources, the establishment of this FPT book store would not have been possible. First and foremost, we want to thank our employer, FPT, for giving us the tools and funding we needed to succeed. We also want to express our gratitude to the writers and publishers who have agreed to let us sell their books in our shop. Our bookstore is now a center for a variety of book genres thanks to their significant contributions. We also applaud the personnel who have worked incredibly hard to deliver top-notch customer service, as well as the different suppliers and distributors who have helped us maintain a steady supply of books. Finally, we would like to express our gratitude to our clients for their support and comments, which have enabled us to grow and improve our bookstore.

b) Acknowledgments

We would like to express our sincere gratitude to the members of our team who tirelessly worked to create the FPT book store website and mobile application. We are able to offer our consumers a fluid and user- friendly purchasing experience thanks to their knowledge and dedication. We also want to express our gratitude to the marketing team for their work in publicizing and enhancing the exposure of our bookstore. We are especially appreciative of the customer service team, who has helped our clients quickly and made sure they are happy. We also want to express our gratitude to our families and friends for their support during our journey. Finally, we would want to convey our sincere gratitude to our mentor for his or her invaluable advice and inspiration.

II. OVERAL DESCRIPTION (P1)

1. Product Overview

The application created for this project is a web-based system used to manage the activities of selling and buying books online. As a result, it is a completely new, modern and self-contained product.Specifically, users can perform basic tasks such as: login, log out of the system, retrieve, create new passwords, edit

2. Product function

This section will list the requirements for our product - management application. To effectively capture the needs and functions of the system in order to use it effectively please read carefully. As mentioned above, some functions have been mentioned and this section will talk more about it.

Provide a login function  Through the first page of the application, user can login into the system. Register a new account as role wanted  Through the first page of the application, user can register new account Provide functions to manage account  Through functions available into the system, user can manage their account like: change password, edit their profile. Administrate the user account  User with the role Seller has ability to create new Store (1:1 just create only 1 available in the system) and ability to manage it  User with the role Seller has ability to Create new Books and ability to manage it  User with role Seller can update, delete book and store of their store, not other’s  User with role Seller view list Order history ordered from their store  Customer can ability to create, manage their order and view list Order History  Both Seller and Customer can ability to buy book by add book to cart and checkout  User with role Admin has ability to manage Customer accounts, and Store Owner Account and approve or reject requests made by the Store Owner. Provide detailed, information and listing book  Both Seller and Customer have ability to see all book from all the store through the selling page  Admin has ability to see Customer Screen, Store Owner Screen, and Category Approval Screen. Provide search function  Seller and Customer have ability to search their favorite book through searching function Provide sorting function for searching  Seller has ability to sort their book and easy to search through it

3. User Characteristic

There are 3 roles of users in the system: Customer, Seller (Store Owner), and Admin.

 The role of the Customer is quite simple, they are the people who want to buy books and simply scroll to find the favorite book that they need to buy, select it with 1 mouse click. If it is difficult, you can use the function searching available in the system to easy to find their book.  Sellers are users who want to open a bookstore and they test it by selling books online or simply a user who wants to sell some of their own books. This role requires the user to have some internet knowledge and be able to handle basic tasks like CRUD new books, CRUD their owner Store.

Note that: 1 Seller just can have 1 store for their own, if they want to Create new Store, they must delete the account's previous store.  Admin is user who manage Customer accounts, and Store Owner accounts and approve or reject requests made by the Store Owner.

4. Design and Implementation Constraints

 Hardware requirements:  For the system to be able to use stably, your system needs to have at least 4GB of RAM.  The maximum waiting time for each action and request from the user's browser is 5 seconds.  Software requirements  Database: SQL Server  Display language: English  Programming standards:  Programming languages: C#, CSS, HTML, JavaScript  Frame: Boostrap  System architecture model: MVC model  For the user, this system allows web access to all functions. User-friendly interface, easy to use. Users with the role of Seller or Customer or Admin can freely use the product if they have an internet connection. Customer information will be confidential, avoiding the attack of attackers.

5. Assumptions and Dependency

People who use corporate computers, personal computers, personal laptops or smartphones with Internet connection are called users. At the same time, all users can access the system. Company tweaks or additional functional needs are all factors that can affect the performance and results of the developed application. Problems can occur but are not expected such as:

 The problem occurred during the connection of the MVC architecture model between the departments  Network error  There is a security hole

III. SPECIFIC REQUIREMENT

1. Functional Requirement

Functional requirements capture the intended behavior of the system. This behavior may be expressed as services, tasks or functions the system is required to perform.

2. Use Case Model

Figure 2: UC Model Customer Function:  View All Book: Customers can see all the books available on the websites of different store owners, from here customers can view each book in detail with the View Detail function.  Search Book: Search for the right book for the customer and be able to view the book's details  Add to Cart: The customer can add the desired item to the shopping cart.  Manage Cart: Customers can also review their shopping cart and perform their shopping cart editing management

 Checkout: Customers can check out the products in the cart to complete the purchase of the book

3. WireFlow(P1)

a) User Interface

Figure 3: Register new account page

Figure 5: Detail Book page

Figure 6: Home Page

This is our home page for our program:

Figure 8: Create new book page

Figure 9: Create new Store page