CS383 HW#4

1. You will work this sprint on the items in your sprint backlog.
2. Be sure each of you has your name attached to one or more backlog items, and can either report them completed or explain why not as part of your team's sprint report in two weeks.
3. Consider for each backlog item: how can the rest of your team, or an external reviewer ascertain or observe whether it was completed successfully. For some items this is easy but for some, not so much.
4. In addition to your team's backlog items, this sprint your team must produce a combined master requirements specification document in LaTeX, to consist of:
   • overview and scope,
   • functional and non-functional requirements,
   • use case diagrams and descriptions, and
   • preliminary class diagrams that focus on relationships between classes.
5. Traceability
   • For each functional and non-functional requirement, identify and label where it is reflected in the corresponding use cases or class diagram.
   • For each use case, identify classes in the class diagram involved in implementing it.
6. In addition to your team's backlog items, each team member should pick a (different) subject for which to develop a sequence diagram. This is a software design notation. At this point, the sequence diagram can go into details about a non-trivial use case, or go finer grained and describe some interesting communication that is going to be needed under the covers to implement a step that is a little vague or under-specified.