ASM 1 Application Development 1640 FPT Greenwich (Merit Super Sale)

Điểm của bài asm còn tùy thuộc vào người chấm. Chỉ cần paraphase bài này là có thể pass. 1 trong nhưng tool paraphase mình recommend là quillbot.The submission is in the form of 1 document.● You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3 andmargins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation andreferences must follow the Harvard referencing style. ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title Unit 2: Networking Infrastructure Submission date Date Received 1st submission Resubmission Date Date Received 2nd submission Student Name Student ID Class Assessor name 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 P1 P2 P3 P4 M1 M2 D1 ❒ Summative Feedback: Grade: Lecturer Signature: ❒ Resubmission Feedback: Assessor Signature: Date: Table of Contents I Network Network definiton Ξ First of all, network also known as computer networking, which can be understand as a group of computers utilizing a principles of general communication protocols over digital connections for the intention of sharing resources located upon or accommodated by network nodes ... https:www.dnsstuff.comdatabreach 10 1 Dobran, B., 2 019 Information Security Risk Management: Build a Strong Program Online Available at: https:phoenixnap.combloginformation security riskmanagement garg, r., 20 21 Threats... List and give examples with dates 12 Propose a method to assess and treat IT security risks (M1) 18 TASK DESCRIBE AT LEAST ORGANIZATIONAL SECURITY PROCEDURES (P2) .20 Definition... Dan Swinhoe, 20 21 The 15 biggest data breaches of the 21st century, s.l.: s.n Ohri, A., 20 21 What Is DMZ Network Online Available at: https:www.jigsawacademy.comblogscyber security whatisdmz ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Business Unit number and title Unit 30: Application Development Submission date 27122022 Date Received 1st submission Resubmission Date Date Received 2nd submission Student Name Nguyen Huy Hoang Student ID GCH200739 Class GCH0908 Assessor name Dinh Duc Manh 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 P4 P5 P6 M3 M4 M5 D2 D3  Summative Feedback: Grade: Assessor Signature:  Resubmission Feedback: Date: Internal Verifier’s Comments: Signature Date: Table of Contents Task – Peer Review and Feedback Analysis (P4 – M3) I Introduction II Peer review and feedback analysis List of questions Review and Interpret feedbacks Evaluate any new insights, ideas or potential improvements 16 Task – Application Development (P5, M4) 17 Folder structure of the application 17 Source code samples of the application 19 Order Management Cart Checkout Owner feature: 19 Other Controller: 24 View: 26 Final screenshot 28 Screenshots of using GitHub to manage the source code 48 Task – Application Evaluation (P6 – M5) 53 Performance of the application 53 Customer 54 Store Owner 61 Admin 66 Strengths and weaknesses of the application 69 Gantt chart 71 Task – Peer Review and Feedback Analysis (P4 – M3) I Introduction The projects creator will present and describe the system in this second section while also gathering data from a survey We sell books on our FPTBook, an online library, for a profit We, a threeperson team, collaborate to create this website II Peer review and feedback analysis List of questions Question Scope Open Question Add about the experience of user when using FPTBook Closed Question Ask about the experience in Homepage in which the books are showed Closed Question Ask about the detail pages Closed Question Ask about the store owner page Closed Question Ask about admin page Open Question Add about point of view of user when using it Closed Question Add about login feature Review and Interpret feedbacks The survey states that this section is to find out 12 participated in the survey According to the results, 60% of respondents prefer our project in the range of to 5, while 40% fall into range This means that practically everyone has been pleased with our method The responses to this query show us that the system has only almost pleased everyone, most features are take opinion of 33.3% normal and 66.7% good We take pride in the fact that our systems user interface scored 100% on scales and That indicates that our page is attractive and appealing Sign in page: In terms of UI design, the login page features a nav bar that the factor page does not The layout of the factor page is superior to that of the UI design page since it has more icons, colors, images, and suitable buttons with links The Sign In page is superior than the UI Design page Profile page, Checkout page, Order page: The user has a profile page in UI design where they may examine their info and cart However, the user just has an order page where they may see their order on the real website In UI design, users have a Checkout page where they can verify their order, which has the same purpose as the order page but a nicer layout Because it has greater information and usefulness, UI design is superior than page design Store Owner Delete a book in book list: The delete function in UI design and the factor design seem to be the same Book Detail: The UI design of the book detail page is minimal and does not contain many functions, unlike the factor page It does not mention the route to the product page, book category, or book title The book detail page is superior than the UI design page Add new book: The UI design for adding a new book is minimal, with few functions and data fields compared to the real page The add new book page is superior than the UI design page Update book page: The update book page of UI design is simpler and has fewer functions and data fields than the factor page, making it superior to the UI design page Customer order page: Because of its clever and scientific arrangement, the customer order book page of UI design outperforms the order book design The customer order book of UI design outperforms factor design Make request category page: Make request genre page design does the same purpose as UI design but has a superior layout Genre list page: The genre list design is where users may browse available genre in the database and see whether admin accepts or rejects their genre request Admin Detail page for customer and storeowner: The UI design page has a detail page where they may check customer and storeowner data and change their account password if necessary, however the factor design page does not Request category: Request category page design does the same job as UI design page but has a superior layout Delete, update, new roles: The role control page design performs the same function as the UI design page but has a better layout Strengths and weaknesses of the application Strengths: ☺ The websites operations are generally logical, consistent, and comprehensive The components of the page are not redundant, and they all work in tandem Minimalized design but also provide an eyecatching design Web responsive also is good ☺ Their function and significance from customer interface to user experience ☺ Website Pages all provide an excellent user experience, including database processing The site pages are arranged in a logical order ☺ The content on the website is completely focused on the fundamental objective of the page, with no frills or distractions ☺ The user interface is nearly never malfunctions or crashes due to any flaws ☺ The security (authentication and authorization) has been designed pretty good by integrating with Identity Platform ☺ The navigation on this page is welldesigned There are no stuck pages, and all of the pages are in the exact order ☺ Controller operates pretty well Call controller actions via router are hardly getting errors Additionally, it is feasible to reroute the same content group Its possible to redirect to another page ☺ No webpage has been broken, no webpage has been unstructured, and no data from the model has been misplaced Ascertain that users obtain accurate data Weaknesses:     The validation of the system is not really good Some web pages have been designed obsolete and sparing The loading speed of the website is really slow Some website functions (searching for productscategorybrand, adjusting the number in cart) that are not optimized may create a bad user experience  Lack of functional option for users, the website is still quite sketchy in providing users with features, smart filters as well sorting functions by many different criteria  The system has some minor typographical and syntactic errors  The system is still operational, and functions such as the shopping cart and access to user information should not be prohibited if the account or password is wrong Improvement in Future With time, the FPTBook will need to be enhanced to include a module for email notifications In the future, the system will also be developed and implemented in Java so that it may be installed as an executable file Additionally, articles and research papers will be stored in a portion of the system The system will be enhanced to include an area for online book purchases and to show a photo of the individual who signs in Implementing a shopping cart into the library management system will make this feasible Making it possible to increase the number of times a book may be borrowed from the library system would also help the system Users will be able to borrow the same book more than once thanks to this The following are the upcoming projects that will be completed in the future: ➢ A customers may create a generic installation method that could be used to the installation of ASP.Net applications like the big popular library management system ➢ A customers may create a Distributed Health Management System that can integrate ASP.Net systems like the Library Management System, as well as an Information Management System that can combine ASP.Net systems like that ➢ The Library Management System, for example, may be integrated with a students Warehouse Management System using ASP.Net Future plans for this facility include the addition of many more features, including the ability for teachers to add online lectures and video tutorials, as well as the ability for customer to submit assignments online Another feature that could be added is group chat, which would allow customers to discuss a variety of engineeringrelated topics Gantt chart Week No Task name Title Project Preparation Assigned to 1.1 Meeting to choose Net core version HienHD 1.2 Set up project from scratch HoangNH 1.3 Analysis Business Process for coding HoangNH, HienHD 1.4 Gather and prepare UIUX Design TuND InitiationPlanning 2.1 Project Planning, assign tasks All team 2.2 Technical Specification All team 2.3 Design Database architecture All team Development 3.1 Buildcustomer authentication policy base with identity platform HoangNH 3.2 Build authorization with role management HienHD 3.3 Design book, category management TuND 3.4 Design order management HoangNH Week Week Mon Tue Wed Thur Fri Sat Mon Tue Wed Thur Fri Sat Mon Tue Wed Thur Fri Sat 3.5 Build category request functionality 3.6 Build account management for admin functionality HienHD 3.7 Build owner page with functionality HoangNH 3.8 Designbuild layout for website TuND 3.9 Build Cart, Checkout functionality HoangNH 3.10 Build Authorization in views HienHD HienHD 3.11 Complete Owner functionalities HoangNH 3.12 Complete Admin functionalities HienHD 3.13 Design style for pages TuND QA 4.1 Testing TuND 4.2 System Test All Team 4.3 Design review All Team Implementation 5.1 Deployment All Team Conclusion 6.1 Outcome Document Project Completed CONCLUSION TuND The library system was put into place, and it complied with all the standards Data validation and error checking were adequately handled by this system, however other aspects of software engineering testing were not fully completed owing to time constraints I was able to effectively finish the project and present a system that is operating and meets the system requirements even though there was not enough time to develop and construct the system From a personal standpoint, this project has really helped me understand how the theories and techniques I learned in class—like software engineering and programming—actually work Additionally, creating this system has really aided me in building my confidence in ASP.NET programming, JavaScript scripting, and project management

ASSIGNMENT 1 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Business

Unit number and title Unit 30: Application Development

Submission date 24/12/2022 Date Received 1st submission

 Summative Feedback:  Resubmission Feedback:

3.1

Internal Verifier’s Comments:

Signature & Date:

Software Requirements Specification for FPTBook Library

Prepared by Group 2

Members:

• Nguyen Duc Tu – GCH200690

• Nguyen Huy Hoang – GCH200739

• Hoang Dinh Hien – GCH200791

Table of Contents

I Introduction 9

1 Document purpose 9

2 Product scope 9

3 Intended audience and document overview 9

4 Definitions, acronyms, and abbreviations 10

II Overall descriptions (P1) 13

1 Product overview 13

2 Product functionality 13

1 Store owner 13

2 Customer 14

3 Admin 14

III Specific requirements(P1, P2) 14

1 Functional requirements 14

2 Use case model 18

3 Wire flow 19

1 Other pages 20

2 Customer 26

3 Store owner 28

4 Admin 34

1 Entity relationship diagram (ERD) 39

2 Class diagram 40

1 Admin diagram 40

2 Store owner diagram 41

3 Customer diagram 42

3 Activity diagram 43

1 Admin diagram 43

4 Gantt chart 45

V Risk assessment 49

1 Risk assessment 49

VI Evaluation report (P3, M2) 57

1 Design tools 57

1.1 Tool to design UML 57

1.2 Justify and Evaluation The Use of Our Preferred Selected UML design tool 63

2 Tools to design user interface wireframe 64

3 Tools to design the application 65

2 Justify and Evaluation the Use of Front end technology stack 70

3 Back-end technology stack 74

1 Back-end programming language/Framework 74

2 Operating system 77

3 Web Server 78

3 Hosting 78

4 Database 80

5 Architectural Pattern Model 81

4 Tools for source control management 84

5 Software development models 85

6 Illustrate all Your Findings on How to Use These By Drawing The Overview 90

VII References 91

I Introduction

1 Document purpose

This report gives an overview about the software requirement specification which specifies system architecture and business processes design of an online library that our group produced Version 1.0 of this document is now available The whole mechanism is explained in this SRS Readers will have a greater grasp of the system, the business challenge, and its solutions after reading this article We'll discuss technology design and risk assessment later

2 Product scope

The library selection offered by FPTBook is designed to be appealing to people of all ages We try to provide a wide range of literature, from children's books to novels on morality Since the beginning of the literature, there has been a globe representing the whole world Customers that regularly subscribe get access to all books Our objective is to get entry to a trustworthy intelligence source The works' legal copyright protection will take care of customers' worries Our present objective is to elevate the FPTBook collection's standing around the world We want to break even on the library within the first year

of operation, or possibly even lose money Then, in order to grow our income, we aim to build a robust and active community It is very helpful for any educational institution where content modifications may be made easily in accordance with needs The project is simple to execute in a variety of circumstances, and because all of the modules are interchangeable, we are able to add new features as and when we are needed C# was chosen as the language to employ for the project's development because it has several advantages over other languages in terms of performance, tools, cross-platform compatibility, libraries, cost 1, free availability 2, and the development process

3 Intended audience and document overview

Our team will act as the client and developer in this project, and our teacher will also assume the client position Functional requirements, use cases, diagrams, Gannt charts, and risk assessment are all covered in this SRS There will be several more, one of which will be for individual examination Briefly,

in real-world case study, this document is intended for developers, project managers, testers, etc

4 Definitions, acronyms, and abbreviations

a) Entity Relationship Diagrams (ERDs): A kind of structural diagram used in database architecture are entity relationship diagrams (ERDs) Other

names for them include ER Models, ER Diagrams, and ERDs The many symbols and connections on an ERD graphically represent the core elements included in the system scope as well as their connections (Visual Paradigm, 2022) Data structure diagrams (DSDs), which emphasize interactions between components inside entities rather than relationships between things themselves, are linked to ER diagrams ER diagrams are often combined with data flow diagrams (DFDs), which depict the information flow for systems or processes

b) SRS: A software requirements specification (SRS) is a document that outlines the criteria for how the system must operate (tutorialspoint, 2022)

All the needs specified by the user in an inconsistent way are included in the software requirements specification Only an excellent specification can lead to outstanding software These days' systems and software are so complicated that it would be silly and dangerous to start the design process before understanding what you were planning to construct Software requirements specifications are another name for software documentation

❖ UML stands for Unified Modeling Language It is a multipurpose modeling language for software development that is used in the study,

development, and usage of software systems UML is intended to provide a simple and well-liked method for illustrating the main architectural elements of a software system

UML is now the industry standard for developing object-oriented software UML blueprints are used by business users, developers, and anybody else that requires data modeling (The Economic Times, 2022) The primary goal of UML is to provide a uniform method for visualizing a system's design process It resembles blueprints used in other engineering disciplines quite a bit

II Overall descriptions (P1)

- Add product: Add items to the library

- Update product: change the product's details

- Eliminate product: delete out-of-stock or inappropriate items

- Login: The shop owner's login account

(Each product type has its own category.)

2 Category request

If the new book category does not already exist, submit a request to the Admin

3 Record customer

Display all of the records that the client has requested

2 Customer

- Product search: look for the product you wish to see/purchase

- View product detail: displays extensive information about a certain book

- Checkout: displays information about the chosen product

- Create an account: Customers may create an account

- Assistance: displays a list of available help topics

3 Admin

1 Customer manager

- Display all Customers' account details

- Change the password on the customer's account

2 Manage Store Owners

- Display the account information for all Store Owners

- Change the password on the shop owner's account

3 Category acceptance

Allow the Admin to accept or reject the Store Owner's request for a new book category

III Specific requirements(P1, P2)

1.1 Functional requirements

• The Home Screen

• The Product Screen

• The Register Screen

• Checkout Page

• The About Screen

• The Help Screen

• View the page with the optimal user experience

• After enrolling on the site, you have the option of becoming a member

• Find out more about the FPTbook library

View the website's homepage, which includes the navigation bar, search box, product photos for books, store logo, and contact information

View the website's nice library interface

On the Product Screen, you can see a list of every book See how many books the business has, then pick my

favorite

View the product detail screen to see the book in detail View the book's comprehensive information, including

the title, author, publisher, price, cover image, and description

Check out my profile on the Profile Screen View my registration details and previous orders

A Register Screen with the following fields is available on the website:

Username, Password, Re-Password, Full Name, Date of Birth, Phone, Gender, Address, and Email are all required

Sign up as an FPTbook Library client member

includes: Title, Category, Selected Quantity, Description, and Price

Visit the help screen Utilize the lists of accessible assistance subjects to solve

my problem

2 Store owner Manage the store's books and data and submit requests to the

administrator for the addition of new book categories

Complete my obligation at work

Utilize the Help and Search options Enter an email address to find a specific client

Use the help feature to access the Book Screen Manage the book: add, edit, and delete

Add a book and its classification Simpler to manage my book

Request Screen for Access Category Ask the administrator to create a new book category

Once the Admin has made a choice, you will be informed via message whether it was approved or denied

Improve my store management

After a user login using my account, "Welcome Store Owner" is shown

More efficiently running my shop

3 Admin Manage the accounts of both the store owner and the customer

and decide whether to accept or reject the store owner's demands

Improve my store management

Get to the customer information screen Reset passwords for all Customers' accounts and see

Users should be able to access the system via an Android application on their phones An android application serves as the system's user interface

No additional training is necessary since everyone is acquainted with how mobile apps are generally used The system is simple because it is friendly

user-❖ Available Resources Needed

The system is utilized around-the-clock, 365 days a year, and is completely accessible to the user The systems must be available twenty-four hours a

❖ Security Requirements

Only librarians and system administrators should be able to modify databases using the FPTbook after authorized requirements

Only College students and employees are allowed access to the FPTbook following permission processes

❖ Demand for Reliability

Due to the value of data and the harm that erroneous or incomplete data may cause, the system must be completely dependable The system will be active 24 hours a day, seven days a week It shall handle expected and non-expected errors in ways that prevent loss in information and long downtime period

2 Use case model

Use case Summary:

Actor Description

Admin A category in the library system may be added, deleted, or edited by the administrator Additionally, they are in charge of adding, editing,

and removing new owners and clients to the database

Owner A book in the library system must be added, deleted, and edited by the owner Additionally, they are in charge of editing and removing

users as well as adding new users to the system The procedure of issuing and returning a book is likewise handled by the owner

Customer The person who views and checks out a book from the library is the system's user

Additionally, customers have the option to modify their personal information and see the books they owe the library

Manage User Manage User in FPTBook Must be logged in as Admin User status is

suitable with action

Book must be in customer’s cart and the number of available books is enough

Book is disappeared in customer’s cart and checked out

Must be logged in as User, Owner, Admin

User status is suitable with action

Add Owner Admin add more account

to be owner

Must be logged in as Admin, owner account is not available

Account is becoming Owner account Admin

Search Book Search the book available

Must be logged in as Admin There is category request from owner

Category request is handled by admin Admin

The Homepage page, which appears by default when users visit the system, is seen in the picture above The store's home page serves as its

introduction, on this page, visitors may browse all of the books in the shop Users may look for books by title or genre

This is the Product Detail page; it displays the details of the chosen book from the Product page

This is the Help page; if the user encounters a problem while using the website, the solution may be found on this page

This is the Sign-Up page; the user enters his or her login, password, and re-password, then clicks the Submit button to go to the next page If the user presses the cancel button, they will be sent back to the Home Page

In order to register as a member of the website, users must fill out this page He or she may click the cancel button to go back to the previous page, click the submit button to successfully register their information and go back to the home page, or click the back to home button to go back to the home page

Users may log in using their email address and password on this page as either customers or business owners They may click the registration button to become a member even if they don't currently have an account

2 Customer

The user will be forwarded to the default home page with the message Welcome Customer and enjoy the customer services if they log in using a

customer account If a user clicks the logout button, they will be sent to the Home Page and their account will be successfully logged out To access the page as a customer role, the user must login by account again

Customers may see the following details on this profile page: Customer data entered upon signup and preordered, where consumers may review the order details they have chosen

This is a book administration page where users may add, edit, remove, and examine book information When a user pushes the delete button to

remove a book in the system, the website displays a notice board to check if the user wishes to delete; if the user presses delete, the chosen book is destroyed; if the user clicks cancel, the delete operation is aborted The book will be withdrawn

When the user clicks the Detail button on the chosen book, they are sent to the Book Detail page, where they may examine the book's information in the system

When a user clicks the Add button on the book management page, they are routed to this page where they may add a new book by clicking the Add button and then being returned to the book management page, or they can cancel the process and return to the book management page

Users will be sent to the book update page to amend data for the chosen book when they click the update button on the book management page If the user clicks the update button, the book will be updated; if the user clicks the cancel button, the update process will be aborted and the user will be sent back to the book management page

This is the Order page, where visitors may check the customer's order and search for individual customers by email For example, if the shop owner selects an order with ID number three in the first table, the second table will provide order details such as ID Book, Book Title, Price, Quantity, and Total Price

4 Admin

When a user successfully joins in with the admin account at the login page, they are sent to the Welcome Admin page and may utilize the admin

capabilities If a user wishes to log out, they must hit the logout button and will be taken to the client's homepage; their account will be successfully logged out of the website The administrator may access the accounts detail and give that account a role for the website

Users with administrative privileges may approve or cancel account roles Users might also modify the role of accounts if others required to do so

IV Technical design(M1)

1 Entity relationship diagram (ERD)

The diagram above represents the relationships that is there between different entities of this project but does not represent the actual schema for the system to be used in the implementation of this database

2 Class diagram

1 Admin diagram