The REUSE Company. Tool Vendor Challenge (TVC) at the 23rd INCOSE Symposium held in Philadelphia June 2013. Check our Ontology Based System Engineering (OBSE) approach addressed the challenge proposed by INCOSE. Knowledge Management, knwoledge quality and quality reuse as the core of our solution for complex System Engineering projects.

1. ToolVendor Challenge’13: Ontology Based System Engineering
José Fuentes
www.reusecompany.com

2. 2 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Case study summary
Disaster relief challenge… provide ice:
A natural disaster has devastated a huge area of land
3,000 people have lost their homes
Shelter must be provided for them
No electricity and impassible roads
Ice must be provided !!!
Option1: making
Option2: procuring

3. 3 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Global architecture of the challenge
VR DB
Repository
Role
Tool
Data flow Or
Data Relation
VR
RQs
(Functional)
System
Engineer
RAT
RQs
(Functional)
with quality
on the fly
Analyst
SKB
KM
Terms
PBS
RQs Patterns
Compliance
rules
Domain
Expert
swREUSER
-Requirements
-Risks
-UML/SysML
-Semantic I&R
System
Engineer
Interoperability bus
- RAT : Requirements Authoring Tool
- RQA: Requirements Quality Analyzer
- KM: Knowledge Manager
VR: Visure Requirements RMT
RQA
RQs quality
Metrics
Quality
Manager
REUSE
Studio
Asset
management
All
SKB
UMLModels
-UML models
(Use Cases,
Components)
-Risks
-Requirements
System
Engineer
RQS RQS: Requirements Quality Suite
SKB: System Knowledge Base

4. 6 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Stakeholder identification and information management plan

5. 7 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Information management:
a semantic approach
Every asset will be managed into a
centralized semantic repository
Services of the repository:
Assets indexing
Assets retrieval and reuse
Semantic search engine for
external sources
E.g. this plan will be stored into
the repository as an asset for
further reuse

6. 8 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Information management:
a semantic approach
Look for a suitable ontology
and merge

7. 9 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Information management:
information gathering

8. 10 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Information management:
information gathering

9. 11 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Information management:
information gathering
SKB
Web pages
Planning documents
Customer documents
…

10. 13 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Risk management and reuse

11. 14 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Risk management and reuse
Mitigation actions from previous projects can be reused

12. 15 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Risk management and reuse
Valuable information is used for tradeoff analysis

13. 16 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Requirement managment along the “V” model

14. 17 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Requirement managment along the “V” model

15. 18 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Reusing existing
elements
Reusing existing elements: “Coarse-grained” reuse
Are there existing components that we can reuse?
Provide your organization with a catalog of reusable components

16. 19 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Component X
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Reusing existing
elements
Reusing existing elements: “Coarse-grained” reuse
Are there existing components that we can reuse?
Provide your organization with a catalog of reusable components

17. 20 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Component X
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Customer Requirements
System Requirements
Hardware Requirements Software Requirements
Reusing existing
elements
Reusing existing elements: “Coarse-grained” reuse
Are there existing components that we can reuse?
Provide your organization with a catalog of reusable components

18. 21 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Reusing existing elements: “Fine-grained” reuse

19. 22 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Requirements Quality Checking
CCC quality approach for the reused requirements:
Correctness, Consistency and Completeness

20. 23 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
All in one centralized Specification

21. 24 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Authoring new requirements
Authoring a new requirement with RAT: correctness checking

22. 25 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Authoring new requirements
Authoring a new requirement with RAT: writing assistant

23. 28 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Check for inconsistencies within the specification

24. 29 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Pattern based completeness

25. 30 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Ontology based completeness
Ontology represented as a taxonomy of concepts
After a semantic index of the requirements: which branches of the
ontology are really covered by the specification?

26. 31 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Reporting

27. 32 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
UML diagramming: reuse from umlModels.com

28. 33 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
UML diagramming: reuse from umlModels.com

29. 34 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
1. Information coming from the requirements specification:
SthReq_Cust_00010:The health personnel must be able to maneuver the equipment within the hospital
NF/Std_0105:The freezing device shall support temperatures ranging between 70 and 100 degrees Fahrenheit.
UML Diagramming: elicitation of elements from requirements
The <STAKEHOLDER> shall be able to <ACTION> <OBJECT><COMPLEMENT>*
The <SUBSYSTEM> shall <SUPPORT_VERB> <ATTRIBUTE> <RANGE><UNIT>
2.Application of boilerplates:

30. 35 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
UML diagramming: swREUSER

31. 36 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
UML diagramming: swREUSER

32. 37 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
UML diagramming: swREUSER

33. 38 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Debriefing
Once the problem is over, the
project is closed
Debriefing activities:
Costs
Risk related activities
Generation of KPIs
All assets must be stored back
to the common repository for
further reuse in other projects

34. 39 July 12, 2013© The REUSE Company – http://www.reusecompany.com
Tool Vendor Challenge 2013
Debriefing
Once the problem is over, the
project is closed
Debriefing activities:
Costs
Risk related activities
Generation of KPIs
All assets must be stored back
to the common repository for
further reuse in other projects
Reminder: keep updated the ontology

35. Thank you!
 Thank you for your attention
 Visit us at booth C2 for a extended and live version of the
challenge
http://www.reusecompany.com
@ReuseCompany
contact@reusecompany.com
Margarita Salas, 16 2nd Floor
Innovation Center
LEGATECTechnology Park
28919 Leganés – Madrid
SPAIN – EU
Tel: (+34) 912 17 25 96
Fax: (+34) 916 80 98 26