A new open source approach for requirements and architecture
A new open source approach for requirements and architecture WHY?!
Traceability?
Why do I care? Document the project Plan better Reduce uncertainty QA Bug fixing
Mustard Mapped Uniform System for Tracking Architecture Requirements and Design
Requirements Requirement Requirement
Requirements Architecture Interfaces Requirement Interface Component Requirement Component
Requirements Architecture Interfaces Requirement Interface Component Requirement Component
Work Items Work Item Work Item
Work Items Architecture Interfaces Work Item Interface Component Work Item Component
Requirements Architecture Work Items Interfaces Requirement Interface Component Work Item Requirement Component Work Item
Requirements Architecture Work Items Verifjcation Interfaces Criteria Requirement Component Work Item Requirement Component Work Item Verifjcation Criteria
Requirements Architecture Work Items Verifjcation Interfaces Criteria Requirement Component Work Item Requirement Component Work Item T ags Verifjcation Criteria
Wait. This is waterfall. That doesn't really work, right?
Requirements Architecture Work Items Interfaces Requirement Interface Component Work Item Requirement Component Work Item
Developer friendly?
haxor@laptop mustard$ cat > req.yaml text-based: kind: req title: Be able to use a text editor description: | Creating objects in Mustard is done with YAML and MarkDown ^D
haxor@laptop mustard$ cat > arch.yaml diagram: kind: c title: Diagram drawing description: | Draw diagrams using PlantUML markup, like: @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response @enduml ^D haxor@laptop mustard$ cat > arch.yaml
Track changes over time?
haxor@laptop mustard$ git log
haxor@laptop mustard$ git branch haxor@laptop mustard$ vi arch.yaml haxor@laptop mustard$ git send-email
PM friendly?!
Using this for a OSS project?
http://github.com/CodethinkLabs
Recommend
More recommend
