Lab 5&6 - Requirement Specification: Use Cases, ERD, and Class Diagrams | Môn Computer Science - Trường Đại học Quốc tế, Đại học Quốc gia Thành phố Hồ Chí Minh

lOMoAR cPSD| 59078336
LAB 5&6 – REQUIREMENT SPECIFICATION MEMBER:
Phạm Đăng Quang - ITCSIU21147
Đoàn Nhân Hậu - ITCSIU21129
Nguyễn Hữu Châu - ITITIU20174
● Purpose: Understanding user requirements ● Submission: Each
group need to submit: o Use Case Diagram and Use Case
Description o Entity Relationship Diagram o Class Diagram ● UML Tools
o https://www.visual-paradigm.com/features/ o https://www.umlet.com o https://creately.com/app/ I. Use Case Diagram lOMoAR cPSD| 59078336 lOMoAR cPSD| 59078336 II. Use Case Description
A use case specification represents the sequence of events along with other information that relates to this use case.
A typical use case specification template includes the following information:
▪ Title: Food Delivery Overall System Use Case Diagram ▪ Identifier: UC1 ▪
User Story: After accessing the application, Customers have to input their username and
password to the Log in screen, they then can search the name of restaurants or foods they
want to eat, the system will show all the restaurants or eateries that sell the foods they have
searched, after that the Customers will pick place the order, in the order screen they are allowed
to choose payment method and vouchers, then confirm it. The Delivery agent and the restaurant
can access to the confirmed order then start to work with it, when the foods have been delivered,
they will confirm the payment Inputs: ● Username ● Password ● Restaurant or food’s name ● Choose to order ●
Choose payment method Outputs: ●
The home page with user’s authorization [If success] ● The login page[If fail] ●
The list of restaurants shows up ● The order page shows up ● List of methods
▪ Preconditions: The Customers has a registered account of the food delivery app that is
created earlier (ID and password), Customers have linked the bank account with the app,
▪ Basic course: Describe the normal processing path Actor: Customers System 1. Open the app 1.1.Display the login page 2. Enter username a nd password lOMoAR cPSD| 59078336 3. Submit 3.1.Check the user’s info.
3.2.If success, return the home page
3.3.Else return the login page
▪ Postconditions: Payment paid III.
Entity Relationship Diagram (Hậu) ● Tutorials about ERD: o
https://www.visual-paradigm.com/guide/data-modeling/what-is-entityrelationship- diagram/
o https://creately.com/blog/diagrams/er-diagrams-tutorial/ ● How to
draw ERD using Visual Paradigm tool:
https://www.visualparadigm.com/tutorials/how-to-model-relational-database-with-erd.jsp
● Some examples: https://circle.visual-paradigm.com/category/entity-relationship-diagram/ IV. Class Diagram
Class diagrams are used when developing an object-oriented system model to show the
classes in a system and the associations between these classes. An association is a link between
classes that indicates that there is a relationship between these classes. lOMoAR cPSD| 59078336
● Tutorials about Class Diagram:
o https://www.visual-paradigm.com/guide/uml-unified-modeling-language/uml- classdiagram-tutorial/
o https://creately.com/blog/diagrams/class-diagram-tutorial/ ● How to draw class diagram using Visual Paradigm tool:
https://www.visualparadigm.com/support/documents/vpuserguide/94/2576/7190_drawingc lass.html
● Some examples: https://circle.visual-paradigm.com/category/class-diagram/