The REUSE Company. Tool Vendor Challenge (TVC) at INCOSE Symposium

Tool Vendor Challenge’13: Ontology Based System Engineering

José Fuentes

www.reusecompany.com

http://www.google.com/url?sa=i&rct=j&q=emergency+ice+delivery&source=images&cd=&cad=rja&docid=YIKETNOE3NPqmM&tbnid=jHf3NVUw_unRmM:&ved=0CAUQjRw&url=http://www.aclearalternative.com/emergency-ice.php&ei=YxiWUd_4BMTD0gH2w4GIDw&bvm=bv.46471029,d.dmQ&psig=AFQjCNEcx4sj9Pq8Juwq8wppf7t-E5qpwA&ust=1368875933450127

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




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




Stakeholder identification and information management plan




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





a semantic approach

Look for a suitable ontology

and merge





information gathering











SKB

Web pages

Planning documents

Customer documents

…




Risk management and reuse





Mitigation actions from previous projects can be reused





Valuable information is used for tradeoff analysis




Requirement managment along the “V” model




Requirement managment along the “V” model




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




Component X Customer Requirements

System Requirements


Reusing existing

elements








System Requirements


Component X


System Requirements



System Requirements


Reusing existing

elements







Reusing existing elements: “Fine-grained” reuse




Requirements Quality Checking

CCC quality approach for the reused requirements:

Correctness, Consistency and Completeness




All in one centralized Specification




Authoring new requirements

Authoring a new requirement with RAT: correctness checking




Authoring new requirements

Authoring a new requirement with RAT: writing assistant




Check for inconsistencies within the specification




Pattern based completeness




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?




Reporting




UML diagramming: reuse from umlModels.com




UML diagramming: reuse from umlModels.com




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:




UML diagramming: swREUSER












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




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


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

[email protected]

Margarita Salas, 16 2nd Floor

Innovation Center

LEGATEC Technology Park

28919 Leganés – Madrid

SPAIN – EU

Tel: (+34) 912 17 25 96

Fax: (+34) 916 80 98 26

http://www.reusecompany.com/



mailto:[email protected]


https://twitter.com/ReuseCompany

https://twitter.com/ReuseCompany


Date post:	05-Dec-2014
Category:	Education
Upload:	the-reuse-company
View:	385 times
Download:	4 times

The REUSE Company. Tool Vendor Challenge (TVC) at INCOSE Symposium

Education