The Interaction Modeling is the third leg of the tripod and describes interaction with the system.
Moreover, The class model describes an object in the system and relationship among them.
State model describes life history of an object.
Interaction model describes how the object interacts to produce useful results.
Moreover, Interaction model and state software model describe the whole behavior of the system.
Interaction can be modeled at the different level of abstraction. At the higher level, a use case describes how a system interacts with outside actors.
Also, Each use case represents a piece of functionality that a system provides to its user.Use cases are helpful for capturing informal requirements.
Sequence diagram provides more detail and shows the messages exchanged among a set of objects over the time.
Moreover, Sequence diagrams are good for showing the behavior sequence seen by users of a system.
Also, Activity diagrams provide further detail and show the flow of control among the steps of computation.
Activity diagram documents the steps necessary to implement an operation or a business process in a sequence diagram.
Use case Models
Use Cases identifies the functionality of a system and organize it according to the perspective of users.
A use case diagram describes how a system interacts with outside actors.
It is a graphical representation of the interaction between the elements and system.
Each use case represents a piece of functionality that a system provides to its user.
Use Cases describe complete transactions and are therefore less likely to omit necessary steps.
- First, determine the system
- Ensure that actors focused
- Also, Each use case must provide value to users.
- For example, dial a telephone number is not a good use case for a telephone system v.
- Relate use cases and actors
- Also, Remember that use cases are informal
- Use cases can structure Use Case Diagram