Assignment 1 for Application Development - 1670, Assignments of Web Application Development

Assignment 1 for Application Development - 1670 (Distinction Grade)

Typology: Assignments

2021/2022

Available from 12/21/2022

tri-minh-1
tri-minh-1 🇻🇳

4.7

(144)

36 documents

1 / 41

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
ASSIGNMENT 1 FRONT SHEET
Qualification
BTEC Level 5 HND Diploma in Business
Unit number and title
Unit 30: Application Development
Submission date
10/12/2022
Date Received 1st
submission
Re-submission Date
Date Received 2nd
submission
Student Name
Phan Minh Tri
Student ID
GCD201632
Class
GCD0904
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
Phan Minh Tri
Grading grid
P1
P2
P3
M1
M2
D1
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29

Partial preview of the text

Download Assignment 1 for Application Development - 1670 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 10/12/2022 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Phan Minh Tri Student ID GCD Class GCD0904 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 Phan Minh Tri

Grading grid P1 P2 P3 M1 M2 D

 Summative Feedback:  Resubmission Feedback:

Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date:

Software Requirements Specification for FPT Book system

Version 1.

Prepared by

Group Name: One

Phan Minh Trí GCD201632 [email protected] Võ Minh Quốc GCD201870 [email protected] Huỳnh Thị Kim Lâm GCD201561 [email protected]

Instructor: Nguyễn Văn Lợi

Course: 1670 –^ Application Development

Date:

1 Introduction (P1)

Currently, internet shopping demand is expanding in various categories of items such as fashion, toys, hobbies, DIY, furniture, electronics... and unique books. As a result, the FPT corporation has decided to apply digital transformation to their book-selling business by developing a book-selling website under the name FPT Book. This system is designed to help customers who prefer online shopping to local shopping buy books more conveniently, as well as to help bookstore owners manage their book purchases and sales by simplifying and speeding up the process of selecting, ordering, and purchasing books for customers, as well as managing a database of users and a database of products.

1.1 Document Purpose

The primary goal of this SRS document is to offer the most detailed description of the FPT Book system, including system features, interfaces, what the system will perform, the limitations it must work under, and how the website system will respond to external stimuli. This paper, meant for stakeholders, will be posted to the FPT corporation.

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

This document must cover the system administrator, end-point users, and shop owners. We strongly advise you to study the article from beginning to end, section by part, to obtain a complete knowledge of it. This paper is broken into six sections:

1. Each section's header title will be included in the document's contents. To assist readers, grasp _what the paper is about, briefly describe the arrangement of the text.

  1. The Revisions section gives extensive information on the status of the document. It shows the_ _version number, the author's name, a description, and the date it was developed.
  2. The Introduction gives an overview of the text and the project, including its aims, purpose, acronyms_ _and abbreviations, and references.
  3. Everything the SRS stated about the product and how it works is summarized in the Overall_ _Description.
  4. The section on Specific Requirements contains the project's functional requirements, and diagrams_ _like the use case model and wire flow show how the system works.
  5. The Risk Assessment identifies and assesses the hazards that development teams may face during_ the development process. People who want to read and comprehend this SRS document should begin by reviewing the Content and Revisions sections to establish the structure and version of the text. They should then read the Introduction to get a sense of the project and to understand what the acronyms and abbreviations mean. Then, to discover how the system is put together, consult the Overall Description and Specific Requirements

sections. Finally, examining the Risk Assessment discloses what dangers may occur during the construction of the project.

1.4 Definitions, Acronyms and Abbreviations

No Abbreviations Definitions Acronyms 1 SRS Software Requirements Specifications None 2 ERD Entity Relationship Diagram None 3 UC Use Case None 4 MVC Model – View – Controller None

2 Overall Description (P1)

2.1 Product Overview

FPTBook is a web-based software system that helps bookstore customers and owners manage their book purchases and sales by simplifying and speeding up selecting, ordering, and purchasing books for customers, as well as managing a user database and a product database for bookstore owners. The system has three primary roles: client, shop owners, and administrator. The following diagram depicts a quick yet extensive description of this system:

2.2 Product Functionality

The system allows:

  • Customer:
    • Register to the system

3.2 USE CASE MODEL (P1)

This is a use case model

3.3 WIREFLOW (P1)

The diagram below displays the overall wireflow of the system based on the customer's function. To begin, clients just log in to the website if they already have an account. Customers who do not already have an account must register to establish one. Customers may review the list and details of the books they want to purchase after successfully logging in. Customers may also manage and view prior orders. Customers may also use the Help Screen to manage their profile and seek assistance in choosing a book topic.

4 Technical Design (M1)

4.1 ENTITY RELATIONSHIP MODEL (ERM)

4.3 ACTIVITY DIAGRAM

4.4 GANTT CHART

Table of Contents

Chapter 1 – Design Tools

I. Tools to design UML ❖ Draw.io is a proprietary tool for creating diagrams and charts. You can use the software's automated layout option or design a custom layout. They provide a wide range of shapes and hundreds of graphic components to let you create a one-of-a-kind diagram or chart. The drag-and- drop tool makes it easy to construct a visually appealing diagram or chart. Figure 1 : Draw.io ❖ Lucidchart works with Confluence, as well as Microsoft Team, Slack, and G Suite. Lucidchart can handle complicated system diagrams as well as mind maps. Because of its simple drag-and-drop user interface, Lucidchart is popular with non-technical development team members. Figure 2 : Lucidchart ❖ Microsoft Visio Pro gives Office users basic UML tools. Companies may add Visio Pro to their Microsoft Office Pro subscription. Organizations use Visio Pro to develop UMLs within the Microsoft Office ecosystem. Microsoft Visio Pro may not have as many functionalities as some of the products mentioned above. Visio Pro is ideal for big enterprises that require seamless integration of UMLs inside their corporate Office environment. Figure 3 : Microsoft Visio

➢ Because of the following criteria, I choose Draw.io to create the UML for my software instead of the other tools: ✓ Easily generates high-quality diagrams ✓ Has many preconfigured shapes for a variety of diagramming purposes. ✓ Shape grouping is possible. ✓ Intelligent connectors ✓ Compatible with Google Drive ✓ Exports in a few formats. ✓ Diagrams may be created collaboratively.  Reason that I choose Draw.io; Based on the features, Draw.io is the ideal solution for my requirements, particularly when it comes to using diagrams such as use case, ERD, system architecture, and others. The key reason is because draw.io is free to use, which saves me and others money and allows me to quickly create II. Tool to design User Interface ❖ Bootstrap Studio is a sophisticated desktop application for website design and prototyping. It has a plethora of built-in components that you can drag and drop to create flexible web pages. The app is built on the massively popular Bootstrap framework and produces clean, semantic HTML. Figure 4 : Bootstrap Studio ❖ Bootstrap Studio’s Features

  • Beautiful and User-Friendly Interface
  • Live Preview
  • A Large Component Library
  • Reusable Smart Components
  • Live JavaScript Editing in an Advanced CSS Editor
  • Google Fonts may be easily imported.