Team1 UML Diagrams (Sprint 2)
UML class diagrams serve to describe the information about classes in a program and the relationships between individual classes.
All Object Oriented languages are inseparable from the concept of classes, and understanding the design of classes in a program is half the battle. UML class diagrams were developed to describe the information about classes and the relationships between classes in an abstract way, without the limitations of the language. This is the role of UML class diagrams.
All the methods already completed by team1 will be shown in a class diagram
A sequence diagram shows the dynamic collaboration between multiple objects by describing the temporal order in which messages are sent between them.
The focus of a sequence diagram is on the sequence of messages, that is, the description of how messages are sent and received between objects. The temporal order in which messages are transmitted between objects is represented.
Advantages of sequence diagrams: emphasise the order in which message events occur, making it easier to illustrate the process of event flow.
The way to navigate a sequence diagram is to view the messages exchanged between objects from top to bottom.
All the methods already completed by team1 in sprint2 will be shown in a sequence diagram
