Fixed requirements authored by Brayden Martin's avatar Brayden Martin
......@@ -19,16 +19,16 @@
# Requirements
• Action Plan
• who did what and who will do what
• provide time actuals and time estimates per person
• Design storyboards
• Low-fidelity sketches of principle user stories
• System architecture
• Use a UML component diagram
• key components identified (tiers)
• packages and nested components identified if necessary
• required and provided interfaces of components are identified
• associations between components
• deployment nodes (devices or execution environments)
• epics annotated
\ No newline at end of file
- Action Plan
- who did what and who will do what
- provide time actuals and time estimates per person
- Design storyboards
- Low-fidelity sketches of principle user stories
- System architecture
- Use a UML component diagram
- key components identified (tiers)
- packages and nested components identified if necessary
- required and provided interfaces of components are identified
- associations between components
- deployment nodes (devices or execution environments)
- epics annotated
\ No newline at end of file