CSCI 250 - Scalable Software
Spring 2017
Programming Project 1: Requirements
For Monday, 1/23: (2/30 points for Project 1 Requirements)
- Write a draft of the use cases for your concept.
- Be sure to include the following:
- All actors and their goals
- Every use case, including:
- Main success scenario
- Minimal guarantees
- Success guarantees
- Do not be concerned about extensions.
- Submit as PDF via Moodle. Also, bring a hard copy to class.
For Wednesday, 1/25: (2/30 points for Project 1 Requirements)
- Improve the draft of the use cases for your concept.
- Add a Purpose and Scope section (see p. 13 of the book). This section describes the overall scope and goal of the project. It also lists the stakeholders and their interests.
- Submit as PDF via Moodle. Also, bring a hard copy to class.
For Friday, 1/27: (26/30 points for Project 1 Requirements)
- If there is any project-specific terminology that would be helpful to
define, add a Glossary chapter between Purposes and Scope and the
Use Cases.
- If there are any miscellaneous requirements, add an Other Requirements
chapter after the Use Cases.
- For each use case, add any necessary preconditions (i.e., conditions that
must be true for the use case to start). If a use case has no
preconditions, give it a precondition of "None".
- For each use case, state the trigger that starts the use case.
- If anything can go wrong in a use case, add an Extension (Chapter 8)
to describe how the situation is to be handled.
- Examine each step in your use cases. As outlined on p. 89, rewrite each step as needed to ensure that every step is one of:
- An interaction between two actors
- A validation step to protect an interest of a stakeholder
- An internal change to satisfy an interest of a stakeholder
- Also ensure that every use-case step follows the ten guidelines from
Chapter 7.