Visure Solutions INCOSE Tool Vendor Challenge 2013

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

3. 3
Understanding the problem
Problem Domain Model Use Case Diagrams
Context Diagrams

4. 4
The Project Structure

5. 5
Different types of Stakeholder needs

6. 6
Capturing Stakeholder needs

7. 7
Capturing Stakeholder needs
• Atomic requirements including:

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

13. 13
Risk management and FMEA
• Automatic calculation of Risk Priority Number (RPN)

14. 14
Deriving System Requirements
• System Requirements may be derived directly from the User
Requirements

15. 15
Search for inconsistencies
within the specification

16. 16
Gap Analysis: Are we missing anything?

17. 17
Reusing existing elements
Are there
existing
components
that we can
reuse?

18. 18
Semantic Search of reusable elements

19. 19
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
You already built a similar system?
Reusing existing elements

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

23. 23
Complete Impact Analysis

24. 24
Complete Impact Analysis

25. 25
Complete Impact Analysis

26. 26
Thank you
Thanks for your attention!
Fernando Valera - Alliance Manager
fvalera@visuresolutions.com
c: +1 (415) 606-5851
Skype: fvalera.visure