Assignment 1 - Application Development - Pass, Assignments of Computer Science

Download Assignment 1 - Application Development - Pass and more Assignments Computer Science in PDF only on Docsity!

Huynh Minh Huy | GCD

GCD1001 | UNIVERSITY OF GREENWICH

Assignment 1

APPLICATION DEVELOPMENT

ASSIGNMENT 1 FRONT SHEET Qualification BTEC Level^5 HND Diploma in Business Unit number and title Unit 30: Application Development Submission date 03 /04/2023 Date Received 1st submission Re-submission Date 06 /05/2023 Date Received 2nd submission Student Name Huynh Minh Huy Student ID GCD Class GCD1001^ Assessor name Nguyen Van Loi 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 (^) Huy Grading grid P1 P2 P3 M1 M2 D

Table of Contents

Contents

CONTENTS .............................................................................................................................................................. IX Revisions

• SOFTWARE REQUIREMENTS SPECIFICATION
• CHAPTER 1: DESIGN TOOLS.
  • I. TOOLS TO DESIGN UML.
  • II. TOOLS TO DESIGN USER INTERFACE.........................................................................................................
• CHAPTER 2: FRONT END TECHNOLOGY STACK.
  • I. FRONT END PROGRAMMING LANGUAGE.
  • II. HTML/CSS/SCSS/SASS/LESS ETC.
    • 1. HTML.
    • 2. CSS.
    • 3. SCSS.
    • 4. SASS.
    • 5. LESS.
  • III. JAVASCRIPT LIBRARY / FRAMEWORK.
    • 1. AngularJS.
    • 2. ReactJS.
    • 3. jQuery.
    • 4. VueJS.
  • IV. CSS FRAMEWORK.
    • 1. Bootstrap.
    • 2. Tailwind CSS.
• CHAPTER 3: BACK END TECHNOLOGY STACK.
  • I. BACK END PROGRAMMING LANGUAGE.
    • 1. C#.
    • 2. Java.
    • 3. Kotlin.
  • II. OPERATING SYSTEM.
    • 1. Window.
    • 2. Linux.
    • 3. MacOS.
  • III. WEB SERVER.
    • 1. Apache HTTP Server.
    • 2. Microsoft IIS........................................................................................................................................
    • 3. Nginx......................................................................................................................................................
  • IV. DATABASE.
    • 1. Microsoft SQL Server.......................................................................................................................
    • 2. MySQL.
    • 3. PostgreSQL.
  • V. HOSTING.
    • 1. Azure.
    • 2. Amazon Web Service (AWS).
    • 3. Google Cloud.
  • VI. FRAMEWORK.
    • 1. .NET.
    • 2. Laravel.
    • 3. Django.
• CHAPTER 4: TOOLS FOR SOURCE CONTROL MANAGEMENT................................................
  • I. GIT, GITHUB, GITLAB, ETC........................................................................................................................
    • 1. Git............................................................................................................................................................
    • 2. Github.
    • 3. Gitlab.
• CHAPTER 5: SOFTWARE DEVELOPMENT MODELS.
  • I. INTRODUCE SEVERAL SDLC MODELS: SCRUM, WATERFALL, V – MODEL, ETC....................................
    • 1. Waterfall...............................................................................................................................................
    • 2. V - model.
    • 3. Agile Model..........................................................................................................................................
    • 4. Spiral Model.
• REFERENCES..........................................................................................................................................
• Figure 1: UML Diagram Tool........................................................................................................................... Table of Figures
• Figure 2: Draw.io.
• Figure 3: Lucidchart.
• Figure 4: Visual Paradigm.
• Figure 5: UX/UI Tools.
• Figure 6: Sketch.
• Figure 7: Figma.
• Figure 8: Front End Programming Language.
• Figure 9: HTML.
• Figure 10: CSS.
• Figure 11: SCSS.
• Figure 12: SASS.
• Figure 13: LESS.
• Figure 14: AngularJS.
• Figure 15: ReactJS.
• Figure 16: jQuery.
• Figure 17: Vue.js.
• Figure 18: Bootstrap.
• Figure 19: Tailwind CSS.
• Figure 20: Backend programming languages.
• Figure 21: C#.........................................................................................................................................................
• Figure 22: Java.
• Figure 23: Kotlin.
• Figure 24: Window.
• Figure 25: Linux.
• Figure 26: macOS.
• Figure 27: Web Server.
• Figure 28: Apache Http Server.
• Figure 29: Microsoft Internet Information Services (IIS).
• Figure 30: Nginx.
• Figure 31: Database.
• Figure 32: Microsoft SQL Server.
• Figure 33: MySQL.
• Figure 34: PostgreSQL.......................................................................................................................................
• Figure 35:Hosting.
• Figure 36: Azure.
• Figure 37: Amazon Web Services (AWS).
• Figure 38: Google Cloud
• Figure 39: Framework.
• Figure 40: .NET Framework............................................................................................................................
• Figure 41: Laravel.
• Figure 42: Django.
• Figure 43: Git.
• Figure 44: Github.
• Figure 45: GitLab.
• Figure 46: Waterfall SDLC Model.
• Figure 47: V-shaped SDLC Model..................................................................................................................
• Figure 48: Agile SDLC Model.
• Figure 49: Spiral SDLC Model.
• Table 1: UML diagramming tool comparison table. Table of Tables
• Table 2: UX/UI design tools comparison table.
• 1 INTRODUCTION (P1) REVISIONS IX
  • 1.1 DOCUMENT PURPOSE
  • 1.2 PRODUCT SCOPE
  • 1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW
  • 1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
  • 1.5 REFERENCES AND ACKNOWLEDGMENTS.................................................................................................
• 2 OVERALL DESCRIPTION (P1)
  • 2.1 PRODUCT OVERVIEW
  • 2.2 PRODUCT FUNCTIONALITY
• 3 SPECIFIC REQUIREMENTS (P1 & M1)
  • 3.1 FUNCTIONAL REQUIREMENTS (P1)
  • 3.2 USE CASE MODEL (P1)
  • 3.3 WIREFLOW (P1)
• 4 TECHNICAL DESIGN (M1)
  • 4.1 ENTITY RELATIONSHIP DIAGRAM (ERD)
  • 4.2 CLASS DIAGRAM
  • 4.3 ACTIVITY DIAGRAM
  • 4.4 GANTT CHART
• 5 RISK ASSESSMENT (P2)
  • 5.1 RISK ASSESSMENT
  • 1.0 Huynh Minh Huy FPT Book System 02/04/ Version Primary Author(s) Description of Version Date Completed

1. Introduction (P1)

1.1 Document Purpose

The purpose of the Software Requirements Specification (SRS) document is to collect and analyze all suggestions related to the system and its user requirements. It also involves strategizing the utilization of the product to gain a better understanding of the project, establish concepts that can be developed later, and record work-in-progress ideas, which may be modified during the product's development. This particular SRS document is for the Web-based FPT Book Software System and aims to provide a comprehensive overview of the product for an online book buying and selling system. It outlines the target audience, user interface, functional, hardware, and software requirements, and the product's value proposition for the customers. Moreover, it assists in the Software Delivery Life Cycle (SDLC) operations for designers and developers. The expected audiences for this SRS document include book buyers and store proprietors managing FPT Book's book sales, as well as the development team, requirements team, requirements analyst, design team, and other stakeholders within the creating organization.

1.2 Product Scope

The FPT Book will be a web-based software system that will help bookshop owners manage book sales and purchases by making it easier and faster for consumers to pick, order, and buy books online, as well as giving bookstore owners with information about their customers and items. The project will be adopted in companies, with both store owners and consumers having access to the website. This website seeks to improve the user experience and make it easier for customers and store owners to conduct business. It also seeks to make store owners' jobs easier.

1.3 Intended Audience and Document Overview

To ensure that the system administrator, end-point users, and shop owners are all adequately covered, this document is organized into six sections. It is strongly recommended that readers study the article in its entirety, section by section, to obtain a comprehensive understanding of the system. The six sections of this paper are as follows:

1. The document's contents will include the header title of each section to assist readers in _understanding the paper's arrangement. A brief summary of the text's organization will be provided.

2. The Revisions section contains detailed information about the document's status, including the_ _version number, author's name, description, and creation date.
3. The Introduction section provides an overview of the text and the project, including its goals,_ _objectives, acronyms, and references.
4. The Overall Description section summarizes everything the SRS says about the product and how_ _it functions.
5. The Specific Requirements section includes the project's functional requirements, as well as_ _diagrams such as the use case model and wire flow to demonstrate how the system works.
6. The Risk Assessment identifies and evaluates potential risks that development teams may face_ during the development process. To effectively comprehend the FPT Book software system, readers should begin by examining the Content and Revisions sections to understand the document's organization and version. The Introduction provides an overview of the project, its objectives, and key terminologies. To understand how the system works, readers should refer to the Overall Description and Specific Requirements sections, which provide a summary of the system's purpose, constraints, and dependencies, as well as detailed information about its functionality, performance, and other requirements. After reviewing the Specific Requirements section, readers should then proceed to the Design section, which describes the system's architecture, components, and data flow, including diagrams and other visual

2. Overall Description (P1)

2.1 Product Overview

The COVID-19 pandemic has caused various challenges, particularly for customers who are restricted from participating in social activities such as going out and visiting crowded places. Consequently, book sales have been significantly affected and revenue has become extremely difficult to generate as many customers are unable to purchase books due to restrictions on leaving their homes during the pandemic. In response to this challenge, customers have expressed a desire for bookstore owners like FPT Book to create a web application. To meet this demand, we have planned to develop a web application system that caters to three primary audiences: administrators, customers, and bookstore owners. This web application aims to simplify the process of buying and selling books for customers, making it easy to find and manage books they want and purchase them directly on the website. Various payment options such as transfer, COD, etc. are also available. In addition, bookstore owners can easily manage their book sales (by week, month, year, etc.), generate lists of popular books based on order quantity, and more. Customers will be able to perform several functions online, including product search, registration, login, logout, account update (updating their profile), and purchasing products. The store staff or admin can perform functions such as registration, member login, logout, account update, and book sales management (adding, editing, and deleting books, book titles, book types, bookshelves, etc.). They can also manage customer groups, including potential customer groups necessary for promoting policy groups. The FPT Book software system is a web-based solution designed to manage book purchases. It replaces the traditional manual paperwork method of recording book and user information. This system interacts seamlessly with other systems such as the owner's email, the book distributor's system, and the browsers used by FPT Book customers. All financial transactions and confidential member information are securely stored and retrieved within the system.

2.2 Product Functionality

1. Customer.  Registration  Log in  Log out  Profile updated  Search  View all orders  Checkout  Book detailed  Purchase. 2. Store Owner.  Log in  log out  Add/update/delete/search books  Request new book category from Admin  Display all customer records ordered 3. Admin.  Log in  Log out  Display customer account information  Reset customer passwords  Display store owner account information  Reset store owner passwords  Approve or reject new book category requests from store owners

3.2 Use Case Model (P1)

3.3 Wireflow (P1)

The following diagram showcases the wireflow of the system in accordance with the customer's function. Initially, customers can access the website by logging in with their account details. For those who do not have an account, they need to sign up and create a new account. Once logged in, customers can view the list and specifications of the books they wish to purchase. They can also manage and view their previous orders. Additionally, customers can utilize the Help Screen to handle their profile and receive guidance in selecting a book topic.

4.2 Class Diagram

4.3 Activity Diagram