Mini Project Part 1 (Use case diagram+scripts+CRC cards+Sequence Diagram

Part 2 (State Diagram+Activity Diagram+Mapping Class Diagram to Database Tables

Description

The project aims to perform the UML technique for developing the online food ordering system at University restaurants. The users of the system can view and order from different food menus from restaurants that exist on campus.

All the models must be modeled using a UML tool such as DrawIO, ArgoUML, star UML, MS Visio, or other online UML tools.

find out the functional requirements of the system. The project should include at least eight functions (Login function is not included). The documentation of the project should include the following:

1. A complete UML use case diagram that covers the eight functions plus login function.

a. The diagram must at least contain two actors

b. A base use case represents a functional requirement (TOTAL 8 base use cases).

c. One extending use case must be added for each base use case (TOTAL 8 extending use cases).

d. Included use case must be added to the base use case (Total 4 included use cases).

2.Each group member must write two scripts to describe two base use cases according to the template learned in the class.

a. Each script must include one alternative flow.

b. The script for the extending use cases must be written according to the template learned in the class.

c. One included use case must be written according to the template learned in the class.

d. In general each group member will write 5 scripts (2 scripts for base use cases, 2 scripts for extending use cases and 1 script for included use case)

3.UML class diagram that represents the application domain during the requirements analysis. No need to show the methods of the classes.

a. The whole group must collaborate to build the class diagram.

4.CRC cards (Total 4 CRC cards)

a. Each group member must draw at One CRC card.

5.UML Sequence Diagram (Total 4 Sequence Diagrams)

a. Each group member must pick one base use case to model the sequence diagram.

b. The Boundary, Control and entity objects identified in the base use cases must be shown in the sequence diagram.

6.UML State Diagram (Total 4 State Diagrams)

a. Each group member must select a class from the class diagram and model the state diagram.

7.UML Activity diagram (Total 4 Activity Diagrams)

a. Each group member must pick a base use case and model the activity diagram.

8.Mapping the class diagram to a relational database during the design phase of the software development.​