1. Fernando Valera - Alliance Manager
Tool Vendor Challenge
INCOSE
25th of June, 2013
2. 2
Tool Vendor Challenge Goals
The requirements
company
• Capture Stakeholder needs
• Requirements Management
• Capture the definition and description of the system including structure and behavior
• Derive System Requirements
• Capture Assumptions
• Derive and capture external and internal Interfaces
• Decision Analysis
• Design Optimization
• Capture and portray end-to-end Traceability between Requirements, System Model elements,
and Designs including Allocations
• Conducting Impact Analysis (Ex:, requirement changes on system design, impact of delayed
design features on requirements satisfaction)
• Gap Analysis/is anything missing (i.e. are all the requirements captured)?
• Consistency/accuracy/completeness checking (i.e. is the model correct? Does it comply with
SysML/UPDM/other? Are there any errors in the model?)
• Automatically Generating Documentation such as an RFP, SPEC, ICD, Test Plan
• System Configuration Management (CM)/Change control
• Modeling (Functional and/or Object) and Simulation
8. 8
Capturing Stakeholder needs
• Atomic requirements including:
– Rich Text Format capabilities, including OLE objects and tables
9. 9
Capturing Stakeholder needs
• Atomic requirements including:
– Rich Text Format capabilities, including OLE objects and tables
– Graphical workflows capabilities
10. 10
Capturing Stakeholder needs
• Atomic requirements including:
– Rich Text Format capabilities, including OLE objects and tables
– Graphical workflows capabilities
– Quick, automated documentation
11. 11
Capturing Stakeholder needs
• Atomic requirements including:
– Rich Text Format capabilities, including OLE objects and tables
– Graphical workflows capabilities
– Quick, automated documentation
12. 12
Capturing Stakeholder needs
• Atomic requirements including:
– Rich Text Format capabilities, including OLE objects and tables
– Graphical workflows capabilities
– Quick, automated documentation
– Synchronization with IBM Rational DOORS databases
20. 20
Component X
Why not reusing a defined subset of the requirements…
Reusing existing elements
21. 21
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Component X
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
… in the new project for the disaster relief?
Reusing existing elements
22. 22
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
… in the new project for the disaster relief?
Reusing existing elements