Download C# application development and more Essays (university) Applied Thermodynamics 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 11/10/2022 Date Received 1st submission 11/10/
Re-submission Date Date Received 2nd submission
Student Name Do Nguyen Huy Hoang Student ID GCH
Class GCH0907 Assessor name Nguyen Dinh Tran Long
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 M1 M2 D
Contents
- Task 1 – Software Requirements Specifications and Software Design (P1 – P2 – M1)
- I. Introduction
- Document Purpose
- Product Scope
- Intended Audience and Document Overview...............................................................................................
- Definitions, Acronyms and Abbreviations
- References and Acknowledgments...............................................................................................................
- II. Overall Description
- Product Overview
- Product Functionality
- III. Specific Requirements
- Functional Requirements (P1)
- Name of Use Case: 2. Use Case Model (P1) Error! Bookmark not defined.
- Add Book
- Date Created:
- 24/09/2022
- Last Revision Date:
- 24/09/2022
- Description:
- The owner can add new book to the book list using this use case.
- Actors:
- Owner
- Preconditions:
- The owner must be able to go into the system.
- Postcondition:
- New book added.
- Flow:........................................................................................................................................................................
- The "add" button is first chosen by the owner...............................................................................................
- A form with the following fields is shown by the system and owner input data:
- Tittle................................................................................................................................................................
- The owner presses "ok" on the keyboard.
- The system will refresh the list once again after adding the book.
- Alternative Flows:
- 3.1 Owner selects "cancel"
- 3.1.1 The system reverts to its initial configuration.
- Exception:
- 2.1 If the owner input invalid data, show a message
- IV. Technical Design (M1).................................................................................................................................
- Entity Relationship Diagram (ERD)..............................................................................................................
- Class Diagram
- Activity Diagram
- Gantt Chart
- V. Risk Assessment (P2)
- Task 2 – Technologies evaluation (P3 – M2)...............................................................................................................
- I. Design Tools
- I. UML design tool
- User interface design tool...........................................................................................................................
- Conclude which tools will be used for the design of the application
- II. Front End technology stack
- Front End Programming Language
- HTML/CSS....................................................................................................................................................
- JavaScript Library / Framework
- CSS Framework
- Conclude which Front End technologies will be used for the development
- III. Back End technology stack
- Back End Programming Language...............................................................................................................
- Operating System........................................................................................................................................
- Web Server
- Database
- Hosting
- Frameworks
- Conclude which Back End technologies will be used for the development
- IV. Tools for source control management
- Conclude which tools will be used for the development
- V. Software Development Models
- VI. Illustrate all your findings on how to use these by drawing the overview
- References
- Figure 1. workflow
- Figure 2. Admin wireflow
- Figure 3. User wireframe
- Figure 4. Owner wireframe
- Figure 5. login wireframe
- Figure 6. Delete account wireframe
- Figure 7. Reset password wireframe
- Figure 8. Admin wireframe
- Figure 9. Buy book wireframe.....................................................................................................................................
- Figure 10 Delete book wireframe
- Figure 11. Book detail wireframe
- Figure 12. Update book wireframe
- Figure 13. Register wireframe
- Figure 14. Login wireframe
- Figure 15. Owner wireframe
- Figure 16. Cart wireframe
- Figure 17. Add new book wireframe
- Figure 18. homepage wireframe
- Figure 19. Entity Relationship Diagram (ERD).............................................................................................................
- Figure 20. Class diagram
- Figure 21. Gantt chart
- Figure 22. Visual paradigm
- Figure 23. Lucidchart
- Figure 24. Draw.io
- Figure 25. Javascript
- Figure 26. React
- Figure 27. HTML/CSS...................................................................................................................................................
- Figure 28. JQuery
- Figure 29. React JS
- Figure 30. Tailwind CSS
- Figure 31. Bootstrap
- Figure 32. PHP
- Figure 33. Java
- Figure 34. C#
- Figure 35. Window
- Figure 36. MAC............................................................................................................................................................
- Figure 37. Apache
- Figure 38. IIS................................................................................................................................................................
- Figure 39. NGINX.........................................................................................................................................................
- Figure 40. MySQL
- Figure 41. SQL Server
- Figure 42. Firebase hosting
- Figure 43. Azure hosting
- Figure 44. AWS
- Figure 45. Google cloud
- Figure 46. Laravel
- Figure 47. Spring
- Figure 48. ASP.Net Core
- Figure 49. Google drive
- Figure 50. Github
- Figure 51. Git...............................................................................................................................................................
- Figure 52. Waterfall model
- Figure 53. Scrum model
- Figure 54. V-Model
- Figure 55. Overview
- Table 1. Functional Requirements table
- Table 2. Usecase diagram
Task 1 – Software Requirements Specifications and Software Design (P1 – P2 – M1) I. Introduction
1. Document Purpose
My team and I were involved in a project to develop a website to sell books invested by FPT, based on the company's requirements and the needs of the pros as well as the cost of the project we researched and used. ASP.Net core as the language to develop this project. This project is named FPTBook, will be developed based on ASP.Net core version 3.1 which is long-supported by microsoft and bootstrap on front-end, and we will use microsoft SQL server for database because SQL server and ASP.net Core are both developed by microsoft which makes them integrated with each other and avoids errors. main function of web will be to aid book store customers and owners to manage their book purchases and sales simplifying and speeding up the process of selection, ordering, and purchasing books for customers as well as managing a database of users and a database of products for book store owners.
2. Product Scope
FPT book website will convert numbers from the normal way of selling books and put them on the internet using available programming languages and frameworks to help users easily find the books they need quickly and conveniently. The creation of FPTbook helps users see the demo of the book they want and makes it easy for customers to pay via e-wallets.
3. Intended Audience and Document Overview
This report is working on the Application Development subject. Reports will be presented to the teacher in charge of the subject.The main focus of the report is the deployment functionality, the use case model
4. Definitions, Acronyms and Abbreviations
- ASP.Net Core
- BE: Back-end
- Bootstrap: Bootstrap 5
- DB: SQL Server Database
- FE: Front-end
- MVC: Model-View-Controller
- ERD: Entity Relationship Diagram
- CRUD: Create-Read-Update-Delete
II. Overall Description
1. Product Overview
Figure 1. workflow When user enter to website and do any function website will pop-up to user a login-form and let user login with their account, each account has it own role which will detect if they are admin, owner or customer. Admin: if account has role is admin it will have permission to
- Approve/Reject request from user
- Reset password of any account Owner: if account has role is owner it will have permission to
- CRUD book
- Make request
- View customer’s record Customer: if account has role is customer it will permission to
- View all books
- View book detail
- Search book
- Buy books
2. Product Functionality
As a customer:
- A customer can log in and log out.
- A customer can view the homepage of the store and view all the books in the store.
- A customer can view the details of the book.
- A customer can search book.
- A customer can add a book to cart and purchase.
- A customer can register and have their profile. As a store owner:
- A store owner can log in and log out.
- A store owner can view all books and categories in the store.
- A store owner can add, edit or delete a book in the store.
- A store owner can view the records orders of customers and remove them when finished.
- A store owner can search for books. As an admin:
- An admin can log in and log out.
- An admin can reset the password of the account.
- An admin can add, edit and remove accounts.
- An admin can approval or reject requests from the book owner.
Customer Have a profile View my information to check if they can be wrong or not Customer See the help screen Have a guide for using the website 2 Store Owner see all the categories in my store know how many categories there are in my store. Store Owner view all books in my store know how many books there are in my store and view all details of each (name, author, images, descriptions, price). Store Owner Add new book Add more books in my store Store Owner Update book Update book information in case they have wrong information Store Owner Delete book Remove the book Store Owner Add new category of book Have more books in that genre Store Owner Delete category Remove the category of book. Store Owner View all the record orders of customer Manage the book have been sold. Store Owner Search for books by name or author Find the book easily and quickly Store Owner Login before going to main screen Protect my data in store
Store Owner Logout Protect my data Store Owner Remove the order Finish the order when the customer have been purchased. 3 Admin Login before going to admin screen Protect my data Admin Logout Protect my data Admin View all the accounts of customers Manage the customer accounts Admin Edit the accounts of customers Reset password of customer if I need Admin Delete the accounts of customers Remove the account of customer if I need Admin View all the accounts of Store Owners Manage the Store Owners accounts Admin Edit the accounts of Store Owners Reset password of Store Owners if I need Admin Delete the accounts of Store Owners Remove the account of Store Owners if I need Admin Approval or reject request from store owners Manage the store Admin Input password before doing any action Protect my account and my store Table 1. Functional Requirements table
Name of Use Case: Add Book Date Created: 24/09/202 2 Last Revision Date: 24/09/202 2 Description: The owner can add new book to the book list using this use case. Actors: Owner Preconditions: The owner must be able to go into the system. Postcondition: New book added. Flow:
- The "add" button is first chosen by the owner.
- A form with the following fields is shown by the system and owner input data:
- Tittle
- Category
- Reprint time
- Price
- Image
- Publisher
- The owner presses "ok" on the keyboard.
- The system will refresh the list once again after adding the book. Alternative Flows: 3.1 Owner selects "cancel" 3.1.1 The system reverts to its initial configuration. Exception: 2.1 If the owner input invalid data, show a message
- Update book use case document Name of Use Case: Update book Date Created: 24/08/202 2 Last Revision Date: 29/08/202 2 Description: This use case allows the owner to edit book information. Actors: Owner Preconditions: The owner must be able to go into the system and choose the right book to repair. The book must not be null. Postcondition: Information about the book has successfully been updated. Flow:
- The "edit" button is chosen by the admin.
- A form that permits altering staff information is shown by the system.
- The owner updates the necessary locations with the updated information. Choose the "save" button after making changes to the form.
- The system will update the data about the staff. Alternative Flows: 3.1 The owner selects "cancel" 3.1.1 The system reverts to its initial configuration. Exception: 3.1 If owner input invalid data, send a message
- Add category use case document Name of Use Case: Add category Date Created: 24/08/202 2 Last Revision Date: 24/08/202 2 Description: The owner can add new category to the category list using this use case. Actors: Owner Preconditions: The owner must be able to go into the system and choose the right category to add. Postcondition: New category added. Flow:
- The "add" button is first chosen by the owner.
- A form with the following fields are shown by the system and owner input data:
- The owner presses "ok" on the keyboard.
- The system will refresh the list once again after adding the category. Alternative Flows: 3.1 Owner selects "cancel" 3 .1.1 The system reverts to its initial configuration. Exception: 2.1 If the data is invalid, show a message
- Update category use case document
Name of Use Case: Update category Date Created: 24/08/202 2 Last Revision Date: 29/08/202 2 Description: This use case allows the owner to edit category information. Actors: Owner Preconditions: The owner must be able to go into the system and choose the right category to edit. The category must not be null. Postcondition: Information about the category has successfully been updated. Flow:
- The "edit" button is chosen by the owner.
- A form that permits altering room information is shown by the system.
- The owner updates the necessary locations with the updated information. Choose the "save" button after making changes to the form.
- The system will update the data about the category. Alternative Flows: 3.1 The owner selects "cancel" 3.1.1 The system reverts to its initial configuration. Exception: 3.1 If the owner input invalid data when updating, show a message
- Delete category use case document
