2. Operations Considerations
• User/Uses questions for design
reviews & CONOPS
• Ops SME biases, needs
User-Driven Requirements Matrix
• Development team’s goals
• User groups’ and other
stakeholders’ goals
• Informs requirements definition
process
Technical CONOPS and Contract
• Forces consensus on problem
being solved, changes to be
made, end result and operational
uses
• Documents design trades and
decisions, benefits to users (not
just features)
• Documents interdependencies
between user groups, operators,
subsystems, etc. (OpCon)
User-Driven Development Principles
• Becomes checklist for developers,
surrogate users, SMEs, system
architects & engineers
• Non-adherence requires
concurrence from SE, SA, Ops SME
and Mgmt
,27
Copyright Protected. All rights
reserved by Solid Thinking
Corporation, 2014.
