Concurrently Engineering Requirements, Design and Knowledge
- RM, KM, ALM tools help author and manage requirements and knowledge
- Engineering tools help design a system
- But the tools exist in disjoint space, with only (marginally useful) traceability links connecting them
Business and technical decisions to define requirements and make design choices are separated from wealth of existing corporate knowledge and state-of- the-art analysis capabilities.
DRIP brings together Requirements, Design and Knowledge through an environment that promotes iterative and highly-coupled development, and mathematical analysis to discover upfront solution infeasibilities and downstream implementation deficiencies
- Requirements, Design and Knowledge represented using a common mathematical “Constraint” framework, including temporal constraints
- Explicit capture of focus areas: Decisions, Enforcements, Recommendations, Facts, ...
- Formal “Design Architecture” linked with formal Requirements and Test scenarios
- Integrated variant and configuration models
- Integration with version control systems
- Symbolic Mathematical analysis to identify “Infeasible” solution space simultaneously considering Requirements, Design and Knowledge
- Explicit “Mapping” of Design Architecture to Implementations enables test harness creation in Implementation environment (Simulink, C)
- Automated verification using test harness, tight interface to Simulink
- Analysis and Test results linked back to Decision