Closed AliNasra closed 1 year ago
A UML design is a thorough representation of the project, incorporating multiple variations: Class Diagrams: They are very reminiscent of the OOP classes tackled in CMPE 160, incorporating classes with their fields, methods, and connections. This part focuses on the actors and elements of the system. You can check those examples. Sequence Diagrams: Such diagrams accentuate the interactions among actors of a system through lifelines. Each diagram corresponds to a specific action. You can check those examples. Use Case Diagrams: These diagrams demonstrate the functionalities multiple users can access and use and the different actions they might take. You can check those examples. Activity Diagrams: Such diagrams adopt the flow chart model. You can check those examples. State Diagrams: They are very similar to CMPE 240's state diagrams with little additions. They include all the possible states of the application and the corresponding outputs and subsequent transition conditions. You can check those examples.
Lucidchart is a very beneficial website used for drawing such diagrams. In addition, it includes tutorials, detailing the syntax and general rules for creating those diagrams.
Thanks for your efforts @AliNasra. The information you've provided was very useful.
Problem Definition
As mentioned in the class, we are supposed to design a UML diagram, an important tool for any project's visual illustration. The group members need to get acquainted with the trappings of this edifice.
Acceptance Criteria
A report should be submitted to the group detailing the foundational principles of a robust UML design. After thorough discussions and deliberations, a UML diagram that reflects the design requirements of the project should be created.