Appendix A - Need Statements
Sample exercise need statements for TSPi projects
Learning Objectives
- Understand the provided need statements for sample exercises
- Identify key functions and constraints
- Select an appropriate need statement for practice
Overview
Appendix A provides ready-to-use product need statements to anchor TSPi team projects. Use them to avoid ambiguity and focus on process practice.
Need: Counter/Analyzer
| Function | Description |
|---|---|
| LOC Counting | Count lines of code by type (blank, comment, code). |
| Difference Counting | Compare versions to find added/modified/deleted LOC. |
| Reporting | Summaries by file/project; output in standard format. |
| Usability | Clear messages; consistent interface. |
Suitable for parsing, metrics, and tool-building practice.
Other Need Statements
- Analyzer Variants: Extend with language-specific parsing or complexity metrics.
- Application Examples: Student registration or scheduling systems for full-stack practice.
Using Need Statements
- Select a need statement; baseline as product scope.
- Derive SRS, scenarios, and strategy from it.
- Use as anchor for all TSPi artifacts (plans, designs, tests).