System Sequence Diagrams Assignment
Table of Contents
1 About This Sprint
This sprint introduces a system analysis view of the real world, and describes how to use the UML use cases as a means for finding out what is relevant to model from the real world for the system you are designing.
This sprint focuses in particular on extracting top-level system events from UNML use cases.
2 User Stories covered in this Sprint
- As a software designer I want to document my understanding of the problem domain so that I can easily transform this into an object oriented software system.
- As a software designer I want to understand how users plan on interacting with the system so that I can design the right API endpoints.
- As a product manager I want to make sure that fixed bugs do not re-appear so that I can build the product incrementally.
3 Learning Material
Please review the sprints on:
4 Experiential Learning
4.1 Sprint Test Plan
Go through the user stories for this sprint and make sure you have a clear understanding of how to solve each of them.
Revisit and update your risks and contingencies section.
Add and/or revise the following items to your glossary:
- Concept
- Class
- Instance
- Object
- Object state
- Class Diagram
- Domain Model (Also: Conceptual Model)
- System Sequence Diagram
- System Event
- Black Box
- Software Architecture
- Layered Software Architecture
- Model-View-Controller Software Architecture
- Pipes-and-Filters Software Architecture
- Unit Testing
- Regression Testing
- Integration Testing
Make sure you understand what each item is, the notation for them, and how to use them either in isolation or together with the other concepts.
4.2 Assignment: System Sequence Diagrams
Create UML System Sequence Diagrams from your UML Use Cases in your first iteration. Create one System Sequence Diagram for each Use Case.
Tasks:
- For each Use Case, create one System Sequence Diagram.
- Add the
:System, and all involved Actors. - Identify the system events from the use case, name the corresponding method call, and add it to your system sequence diagram from the right actor to the
:System - Add return messages from the
:Systemto the actors. - Add loops if applicable.
Document Structure:
The title for this Assignment Document is: System Sequence 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.
- System Sequence Diagrams
- System Sequence Diagram for Use Case <name 1>
- System Sequence Diagram for Use Case <name 2>
- System Sequence Diagram for Use Case <name … >
- System Sequence Diagram 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: Do all Use Cases in Iteration 1 have a corresponding System Sequence Diagram
- Are all actors in each use case represented in the system sequece diagrams
- Is the system treated as a black box
- Do all system events in each use case have a corresponding system event in the same order as in the use case
- Are the system events aptly named
- Are the return messages from the system sufficiently descriptive
- Is the loop construct used correctly
4.3 Update Course Backlog
What’s the next step? What do you need to do in order to understand how to implement the system based on your system sequence diagrams?
Are there any other questions that you want answered? Add them, along with a brief strategy for how to find an answer.
5 Sprint Acceptance Tests
You are done with this sprint when:
- You have created the System Sequence Diagram document
- You have committed/pushed these documents to your project repository
You may also have
- Updated your Sprint Test Plan
- Updated your Course Backlog