ARENA
Software Project Status Online Report
Description
Methodology Used
|
CUSTOMER |
QUALITY APPS |
END-USER |
|||||||
|
Input |
Process |
Output |
|||||||
|
Need |
Feasibility |
|
|
System |
Code |
System |
Release |
Post-Mortem |
Solution |
1. Formulate the problem
2. Analyze the problem
3. Search for solutions
4. Decide on the appropriate solution
5. Specify the solution
Requirements Elicitation
Analysis
System Design
Object Design
Implementation
Test
Milestones
Risks
Deliverables
| Title | Document Type | Date |
| Problem Statement | ||
| High-level Scenarios | ||
| Scenario Description: organizeTicTacToeTournament | ||
| High-level Use Cases | ||
| Use Case Description: OrganizeTournament | ||
| Detailed Use Cases | ||
| Detailed Use Case Description: AnnounceTournament | ||
| UML Sequence Diagram: AnnounceTournament (tournament creation workflow) | ||
| UML Sequence Diagram: AnnounceTournament (sponsorship workflow) | ||
| UML Sequence Diagram: AnnounceTournament (interest group workflow) |
- Changes (Change Requests)
Build Status