Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

INCOSE - TVC'14

No description
by

José M. Fuentes

on 14 August 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of INCOSE - TVC'14

INCOSE - TVC'14
Case Study Summary
Disaster relief challenge… provide ice:
A natural disaster has devastated a huge area of land
15 000 people have lost power
No electricity and impassible roads
Shelter must be provided in less than 24 hours
Power, water, food and ice must be provided !!!

The backbone of the system - Interoperability
Our solution
Conclusions
Knowledge as the leading actor of the System Engineering Processes

Mainly three enhanced factors:
Traceability
Reuse
Quality: CCC approach for requirements quality

Ontologies as the core element: SKB
Thank you
Thank you for your attention

Visit us at booth C4 for a extended and live version of the challenge

The REUSE Company
Option #1: Making
Option #2: Procuring
UML diagramming: swREUSER

UML diagramming: swREUSER

UML diagramming: swREUSER

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?

Ontology based completeness

Requirement management along the “V” model

Risk management and reuse

Semantic search

Pattern based completeness

Complete Impact Analysis

Authoring a new requirement with RAT: correctness checking

Authoring new requirements

Requirement managment along the “V” model

Mitigation actions from previous projects can be reused

Risk management and reuse

Improve the ontology all along the project

Ontology management and Knowledge management

Stakeholder identification and information management plan

Once the problem is over, the project is closed
Debriefing activities:
Costs
Risk related activities
Generation of KPIs and lessons learned

All assets must be stored back to the common repository for further reuse in other projects

And the ontology must be maintained

Debriefing

Check for inconsistencies within the specification

Authoring a new requirement with RAT: writing assistant

Authoring new requirements

CCC quality approach for the reused requirements:
Correctness, Consistency and Completeness
All along the supply chain

Requirements Quality Checking

Are there existing components that we can reuse?
Provide your organization with a catalog of reusable components

Reusing existing elements: “Coarse-grained” reuse

Valuable information is used for tradeoff analysis

Risk management and reuse

Connection to a requirements management tool

Reusing existing elements: “Fine-grained” reuse

Information management:
a semantic approach

OBSE relies on ontologies
Look for suitable ontologies to serve as baseline for this project


Every asset will be managed into a centralized semantic repository

Services of the repository:
Assets semantic indexing
Assets semantic retrieval&reuse
Semantic search engine for external sources

Ergo, this plan will be stored into the repository as an asset for further reuse

Information management:
a semantic approach

UML diagramming: reuse from umlModels.com

Reporting

Web pages
Planning documents
Customer documents


SKB

Semantic search

The <SUBSYSTEM> shall <SUPPORT_VERB> <ATTRIBUTE> <RANGE><UNIT>

SysML Diagramming: elicitation of elements from requirements
2. Application of boilerplates:


The <STAKEHOLDER> shall be able to <ACTION> <OBJECT><COMPLEMENT>*

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.



Communication Management Plan
Stakeholders identified as:
Requirement <<agents>>
Actors in a UML/SysML diagram
Instances into an ontology
...

Anyway, this document must identify/formalize stake-holders, while addresses the proper communication strategy for them
Procurement management:

What is The REUSE Company
The REUSE Company...
a.k.a.
T R C
r
a
c
e
a
b
i
l
i
t
y
e
u
s
e
u
a
l
i
t
y
Q
50+ different metrics
Assessment based on quality functions
Metrics for both:
Individual requirements
Whole documents/projects
Quality Reports mailed to the Quality Team in a batch mode

Quality Reports mailed to requirements authors
Ontology based approach
Tool manufacturer: RQS
Integrated to different RM tools
IBM DOORS
Visure Requirements
CATIA Reqtify
MS Excel
Available in:
SKR - System Knowledge Repository
SKB - System Knowledge Base
SAS - System Asset Store
All the indexed assets are stored here
Only their formal representation is indexed, in a form of a semantic graph, not the asset itself
Different types of assets require different formalization methods. Some available formalization methods so far:
Requirements
Tests
UML/SysML models
OO source code
Risks
Formalization for textual assets
Re-use of existing product scheme classifications for public contracts such as:
CPV-Common Procurement Vocabulary 2008 (EU)
NAICS-North American Industry Classification System (USA)
UNSPSC
NACE
...
Different schemas in different countries
UK, USA, etc.
Full transcript