Download Application Development (1670) - ASM1- Grade M and more Study Guides, Projects, Research 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 Nhat Linh Student ID GCD Class GCD0905 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 Linh Grading grid P1 P2 P3 M1 M2 D
ASSIGNMENT 1
Subject: Application Development (1670)
Table of Contents
- TASK 1. SOFTWARE REQUIREMENTS SPECIFICATIONS AND SOFTWARE DESIGN (P1 – P2)
- I. Introduction (P1)
- Document Purpose
- Product Scope.....................................................................................................................................
- Intended Audience and Document Overview
- Definitions, Acronyms and Abbreviations
- References and Acknowledgments
- II/ Overall Description (P1)
- Product Overview
- Product Functionality
- III. Specific Requirements (P1)
- Functional Requirements
- Use Case Model
- Wireflow
- IV/ Technical Design (M1)
- Entity Relationship Diagram
- Class Diagram
- Activity diagram
- Gantt Chart
- V/ Risk Assessment (P2)
- TASK 2. TECHNOLOGIES EVALUATION
- I/ Design Tools
- Tools to design UML
- Tools to design User Interface..........................................................................................................
- Conclude which tools will be used for the design of the application
- II/ Front End technology stack..................................................................................................................
- Front End Programming Language
- HTML/CSS/SCSS/SASS/LESS etc.
- 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
- Git, GitHub, GitLab, etc.....................................................................................................................
- Conclude which tools will be used for the development
- V/ Software Development Models
- Introduce several SDLC models: Scrum, Waterfall, V-model.
- explanations 2. Conclude which SDLC model will be used for the development (Waterfall, Scrum, etc.) with
- VI/ Illustrate all your findings on how to use these by drawing the overview
- REFERENCES
- Figure 1: Workflow Table of Figures
- Figure 2: Use Case Model
- Figure 3: Login wireflow
- Figure 4: Admin wireflow
- Figure 5: User wireflow
- Figure 6: Owner flow
- Figure 7: Entity Relationship Diagram
- Figure 8: Class diagram.................................................................................................................................
- Figure 9: Activity diagram of customers.......................................................................................................
- Figure 10: Activity diagram of store owners
- Figure 11: Activity diagram of admin
- Figure 12: Gantt Chart
- Figure 13: Lucidchart
- Figure 14: Gleek.io
- Figure 15: Diagrams.net
- Figure 16: Cacoo
- Figure 17: Gliffy
- Figure 18: Sketch
- Figure 19: Adobe XD
- Figure 20: UXPin
- Figure 21: Marvel
- Figure 22: Figma
- Figure 23: Javascript
- Figure 24: React
- Figure 25: HTML
- Figure 26: CSS
- Figure 27: SCSS
- Figure 28: SASS
- Figure 29: LESS..............................................................................................................................................
- Figure 30: jQuery
- Figure 31: Vuejs
- Figure 32: React
- Figure 33: Bootstrap
- Figure 34: Tailwind
- Figure 35: Java
- Figure 36: C#
- Figure 37: PHP
- Figure 38: Window
- Figure 39: MacOS
- Figure 40: Linux
- Figure 41: Apache
- Figure 42: OpenResty
- Figure 43: Cloudflare
- Figure 44: MongoDB
- Figure 45: MySQL
- Figure 46: PostgreSQL
- Figure 47: Azure............................................................................................................................................
- Figure 48: AWS
- Figure 49: Google Cloud
- Figure 50: ASP.NET Core
- Figure 51: Spring MVC
- Figure 52: Laravel
- Figure 53: Git
- Figure 54: GitHub
- Figure 55: GitLab
- Figure 56: Scrum
- Figure 57: Waterfall
- Figure 58: V-model
- Figure 59: Overview......................................................................................................................................
One of the unique features of FPT Book is the ability to provide a demo of the book that users are interested in. This feature will give users a preview of the book and help them make informed decisions before making a purchase. Additionally, the website provides customers with the option to pay for their purchases using e-wallets, which adds to the convenience of the platform. For book store owners, FPT Book provides an intuitive and easy-to-use interface that allows them to manage their inventory efficiently. The website allows owners to add new books, update existing ones, and track their inventory in real-time. Owners can also manage their sales and customer database with ease, helping them to streamline their operations and improve their bottom line. In summary, FPT Book is a one-stop-shop for all your book-related needs. With its user-friendly interface, advanced search algorithms, and unique features such as book demos and e-wallet payments, FPT Book is set to revolutionize the way we buy and sell books online.
3. Intended Audience and Document Overview This report serves as a comprehensive analysis of the Application Development subject, with a particular focus on the deployment functionality and use case model. The aim of this report is to provide an in- depth understanding of the development process and the key elements that were considered during the project. The deployment functionality is a critical aspect of any application development project, and this report delves deep into the various strategies and techniques that were employed to ensure seamless deployment. The report also outlines the key challenges that were faced during the deployment process, as well as the solutions that were implemented to overcome these challenges. 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 5. References and Acknowledgments GeeksforGeeks (2019, 07 Jun) “Scrum (software development)”. [Online]. Available at: https://www.geeksforgeeks.org/scrum-software-development/ Simplilearn (2022, 12 Jul) “What is Git: Features, Command and Workflow in Git”. [Online].
Available at: https://www.simplilearn.com/tutorials/git-tutorial/what-is-git#features_of_git W3school (2022) “What is GitHub?”. [Online]. Available at: https://www.w3schools.com/whatis/whatis_github.asp Isabella Gabbert (2022, 05 October) “Overall Satisfaction with Google Drive”. [Online]. Available at: https://www.trustradius.com/reviews/google-drive- 2022 - 10 - 04 - 09 - 54 - 49 Redwerk (2021, 01 February) “ASP.NET Core Advantages and Disadvantages”. [Online]. Available at: https://redwerk.com/blog/asp-net-core-pros-and-cons/
Accounts with an admin role have permission to approve or reject requests from users and reset the passwords of any account. Accounts with an owner role have permission to create, read, update, and delete books, make requests, and view customer records. Accounts with a customer role have permission to view all books, view book details, search for books, and purchase books. This system ensures that users have the appropriate level of access and functionality based on their account role. It also provides security by ensuring that only authorized users can access certain features of the website.
2. Product Functionality As a customer: Customers can log in and log out of their account. Customers can view the store homepage and browse all available books. Customers can view detailed information about a specific book. Customers can search for books using keywords or filters. Customers can add books to their cart and complete the purchase. Customers can register for an account and create a profile. As a store owner: Store owners can log in and log out of their account. Store owners can view all books and categories available in the store. Store owners can add, edit, or delete books from the store inventory. Store owners can view customer order records and mark them as fulfilled when completed. Store owners can search for books using keywords or filters. As an admin: Admins can log in and log out of their account. Admins can reset the password of any account in the system. Admins can add, edit, or remove user accounts. Admins can approve or reject requests from the book owners, such as requests to add new books to the store inventory. This system ensures that each user has a specific set of permissions based on their role, providing a secure and efficient way to manage the online bookstore.
III. Specific Requirements (P1)
1. Functional Requirements AS A I WANT TO SO THAT I CAN Customer View the homepage of the website view the website's interface and interact with it view a list of books categories understand how many categories are available in the store view all books in the store find out how many books are in the shop and their descriptions on the website (name, image, price). Choose a category to see all of the goods in that category. know how many products in that category and their details view book details know more about each book in the shop so that I can determine whether or not to buy it see all the information of book including name, author, images, descriptions, price. Learn more about the book before deciding to purchase it. search for book by name of book or author quickly and simply locate a book Have a cart See all the books that I choose and purchase 1 time. Login before purchase Protect my account Logout Protect my information Have a register screen Register for new account and have my profile. Have a profile View my information to check if they can be wrong or not See the help screen Have a guide for using the website
Edit the accounts of customers Reset password of customer if I need Delete the accounts of customers Remove the account of customer if I need View all the accounts of Store Owners Manage the Store Owners accounts Edit the accounts of Store Owners Reset password of Store Owners if I need Delete the accounts of Store Owners Remove the account of Store Owners if I need Approval or reject request from store owners Manage the store Input password before doing any action Protect my account and my store
2. Use Case Model Figure 2 : Use Case Model As depicted in the use case diagram, the system has three primary users: customers, store owners, and admins. Customers can register as members and log in and out of the system. They have the ability to view all books available in the store, along with detailed information about each book. Customers can also search for specific books and complete a purchase once they find the desired item. Store owners can log in and out of the system and view all books available in the store. They have the ability to add new books, edit existing books, and remove books from the store inventory. In addition, store owners can also add, update, or delete categories, but these actions require approval from the admin.
By creating an account, customers are able to enjoy a more personalized and streamlined shopping experience. They can easily view their order history, manage their payment and shipping information, and receive updates and notifications about new books and special offers. Overall, the login and registration process is designed to be simple and intuitive, allowing customers to quickly and easily create an account and begin exploring the website's extensive collection of books. With a focus on user experience and customer satisfaction, this approach is sure to delight customers and drive sales for the online bookstore. Figure 4 : Admin wireflow Once logged in, admins have access to all customer and store owner accounts. They can add new accounts, edit existing accounts, and delete accounts as needed. Additionally, admins have the ability to reset passwords for any account if necessary.
Figure 5 : User wireflow The customer wireflow for the website involves a straightforward and intuitive process for customers to browse and purchase books. Upon visiting the website, customers are presented with a comprehensive display of all books available in the store, allowing them to browse and explore at their leisure. If a customer desires more detailed information about a particular book, they can simply click on it to view the book's details. The detail window will then show the book's title, author, category, image, and price, giving customers all the information they need to make an informed purchase decision. When a customer decides to purchase a book, they can easily add it to their cart with a single click. The cart window then displays a list of all the books that the customer has chosen, allowing them to review their selections before proceeding to the purchase window. The purchase window is where customers can complete their transaction by inputting their shipping and payment information. This final step is designed to be straightforward and streamlined, ensuring that customers can quickly and easily purchase the books they want without unnecessary delays or complications. Overall, the wireflow provides a seamless and intuitive user experience that makes it easy for customers to browse, select, and purchase books from the store. This approach is sure to delight customers and
