Full backlog divided into sprints.
Some sort of list, like a tick list, of the items with annotations saying “done”, “in progress” etc.
We need the product owner and scrum master.
Snapshots on how we incrementally improve the task we are working on.
- Update the requirements, for example include the forum, the feedback form etc.
- Sort out the first sprint, it will need to be updated.
- Tasks he explicitly gave us:
- Divide the backlog into sprints.
- Have some sort of list, like a tick list, with annotations about the tasks like “done”, “in progress” etc.
- We need the product owner and scrum master.
- Snapshots on how we incrementally improved the tasks we are working on.
CS2002 - Sequence Diagrams I (Lecture Notes)
When developing diagrams, we should go back and forth. For example, you might have make changes to the use case diagram when developing the class diagram and vice-versa. Normally the sequence diagram is the last one and is closely related to the class diagram.
Message is the act of calling a method which is related to another class.
The name of the use case must contain a verb.
All the methods used in the sequence diagram must exist in the class diagram.
A trace is the sequence of messages sent.