Structure of the app » History » Version 5
Mariana Calado, 31/12/2022 03:06
| 1 | 1 | Mariana Calado | h1. Structure of the app |
|---|---|---|---|
| 2 | 1 | Mariana Calado | |
| 3 | 1 | Mariana Calado | h2. Use Cases Diagram |
| 4 | 1 | Mariana Calado | |
| 5 | 4 | Mariana Calado | First, we start to design the requirements for our system app and for this, we develop a Use Cases Diagram. This is a visual representation of the interactions between a system and the actors that use it. It is used to identify the primary functionality of the system and the actors that interact with it. |
| 6 | 4 | Mariana Calado | |
| 7 | 5 | Mariana Calado | p=. !{width600px}use_cases.drawio.png! |
| 8 | 4 | Mariana Calado | |
| 9 | 1 | Mariana Calado | h2. Activity Diagram |
| 10 | 4 | Mariana Calado | |
| 11 | 4 | Mariana Calado | Then it was important to design an Activity Diagram since it can be used to model the various screens and interactions within the app, as well as the relationships between those screens and the actions that can be performed on them. This helped us understand the overall structure and functionality of the app, as well as identify potential issues or improvements that may be needed. |
| 12 | 4 | Mariana Calado | |
| 13 | 1 | Mariana Calado | |
| 14 | 1 | Mariana Calado | h2. UML Diagram for DataBase |
| 15 | 2 | Mariana Calado | |
| 16 | 2 | Mariana Calado | We store user information in a database: number of steps, the number of calories losted, the walking distance and finally the data: dd/mm/yyyy hh:mm:ss. |
| 17 | 2 | Mariana Calado | |
| 18 | 3 | Mariana Calado | p=. !{width:200px}databaseUML.drawio.png! |