The document discusses considerations for a user-driven development approach, including gathering user requirements and operational needs, documenting them in a requirements matrix. It also discusses developing a technical concept of operations and contract to define the problem being solved, intended changes and results, as well as operational uses and interdependencies between groups. User-driven development principles are proposed to guide developers and serve as a checklist to ensure the user perspective is considered.

1. Technical
CONOPS
and Contract
Operations
Considerations
User-Driven
Requirements
Matrix
User-Driven
Development
Principles
How Will We Build It?
User-Driven
Development Framework
26
Copyright Protected. All rights reserved by Solid Thinking Corporation, 2014.

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.