11:21
EM.411 meeting
Eric Rebentisch
Requirements communicate intent across a boundary
Hence require precision
A Unifying Language
Working on NLP related to requirements and processes
Capella and Slate
Modeling languages for system engineering
Elon Musk discussion
Going through Musk’s Principles of System Design
I think his biography goes through these
Allocation
Budget and resources, I think
Requirements
Lots of ways that they can fall short
If a requirement is trying to cover too much ground, it’s best to break it down
Cascade from needs to requirements
Get more and more specific and precise
But still Solution neutral, I think
Syntax schema feels a lot like propositional logic / coding
Told to check requirements quality
Requirements quality analysis
Requirements authoring tool
IBM Rational DOORS
Rationale should cover coupled with each requirement
For agile, the user story serves the purpose of requirements
How does uncertainty of what you’re building balance with requirements
This applies to startups too
Needs -> Goals -> Requirements
Fleshing out this whole chain feels like it might be the most useful