Interaction Diagrams Assignment
Table of Contents
1 About This Sprint
This sprint discusses how to identify and model interactions between entities in UML interaction diagrams. The sprint also covers how the interaction diagrams produce material that is used to create UML Class Diagrams.
The sprint particularly focus on the dynamic behaviour inside the system to address each system event.
2 User Stories covered in this Sprint
- As a software designer I want to understand how domain concepts interact so that I can select the best way to implement these interactions.
- As a software designer I want to model both the dynamic behaviour as well as the static structure of the application so that I can communicate both to the developers.
- As a software implementer I want to know which methods and attributes each class contains so that I can implement them.
3 Learning Material
Please review the sprints on
4 Experiential Learning
4.1 Assignment: Interaction Diagrams
Describe what will happen inside the system for your system events in terms of UML Interaction Diagrams. You may choose yourself whether you prefer UML Sequence Diagrams or UML Collaboration Diagrams. You may wish to try using both to get a feel of which one you prefer.
Tasks:
- Go back to your list of UML Use Cases and their corresponding UML System Sequence Diagrams, and extract the System Events therefrom.
- Starting with your most important Use Case, create UML Interaction Diagrams for all the System Events.
- Continue until you have created no fewer than 10 UML Interaction Diagrams and have completed a full Use Case. I.e., if you are in the middle of a use case with your tenth interaction diagram, you complete the use case and create slightly more than ten interaction diagrams.
Document Structure:
The title for this Assignment Document is: Interaction Diagrams for System <system name>
.
The assignment document shall contain the following items:
- Title Page, according to the Title Page Instructions (Link)
System Description
A brief description (2-3 paragraphs) of your interpretation of what the goal of the system is.
Prioritised List of Use Cases
Repeat your prioritised list of Use Cases.
System Events
List the System Events you have extracted from your UML System Sequence Diagrams:
- System Events for Use Case <name 1>
- System Events for Use Case <name 2>
- …
- System Events for Use Case <name N>
Interaction Diagrams
Your UML Interaction Diagrams, organised per use case and titled with the system event.
- Interaction Diagrams for Use Case <name 1>
- Interaction Diagrams for Use Case <name 2>
- …
- Interaction Diagrams for Use Case <name N>
Commit and push this document to your project repository.
Conditions of Satisfaction:
When marking this part of the assignment we are looking for the following:
- Does the title page contain a table with authors and author contribution?
- Size of assignment: Are there at least 10 interaction diagrams?
- Are all relevant objects (and only objects) involved in the interaction diagrams?
- Are all methods (messages) suitably named?
- Are returned objects and objects passed as parameters also represented in the interaction diagram?
- Will the interaction diagram actually sufficiently address the system event?
- Are there interactions that are missing to fully satisfy the system event?
5 Sprint Acceptance Tests
You are done with this sprint when:
- You have an understanding of how the dynamic behaviour of the system is used to identify the static structure
- You have an understanding of how you may use your previous analysis, in terms of Use Cases, System Sequence Diagrams, and Domain Model to initiate your design of the dynamic behaviour.
- You have created an Interaction Diagrams document.
- You have committed/pushed these documents to your project repository.
You may also have
- Updated your Sprint Test Plan
- Updated your Course Backlog