Requirements Management
A knowledge-centric approach
Dr. Jose María Alvarez-Rodríguez & Prof. Juan Llorens
Knowledge Reuse Group
Carlos III University of Madrid, Spain
CRYSTAL Final Dissemination Event
Madrid, 15-16 June, 2016
Sometimes...
Engineering fails...
Final Product
and causing...
loss of human life
A major problem and concern!
Requirements
to the rescue...
"A requirement is a need or a property that whatever human invention must be able to perform or fulfill."
How can you identify needs from humans?
Requirements Engineering
The context...
It does not matter conditions…
SAFETY is a MUST!
The need of a holistic view of a system...
The process...
To reach...
What is a requirement?
Requirements Attributes...
Types
of requirements
Representation of requirements
How can we manage requirements?
Requirement Management System
(RMS)
and the quality?
Interoperability
Quality metrics
Representation
Challenges
Interoperability
Open Services for Life-cycle Collaboration
Source: http://open-services.net/
The CRYSTAL use cases
Requirements Quality Checking
Knowledge Management
Contributions
OSLC KPIs -> OSLC EMS*
OSLC KM
Knowledge Management
Tools by TRC
OSLC Overview
Situating contributions...
OSLC Overview
Situated contributions...
KPIs
- Indicators for requirements quality
- +56
- Compile: dimensions, units of measurement, etc.
Observations
- Observations linked to a KPI
- A value under a context
- Time
- ...
OSLC KPIs
Application to requirements quality management
OSLC Defined Resources
- Based on qb:Dataset and qb:Observation
- W3C Recommendation RDF Data Cube
- Ios_kpi:KPI & Ios_kpi:Observation
Scenarios...
1-Checking the quality of a text-based requirement
2-Checking the quality of an OSLC-based requirement
3-Checking the quality of an OSLC-based requirement and a Jazz Widget
Summary
OSLC KPIs-Key Performance Indicators
- Use of the W3C RDF Data Cube Vocabulary
- KPIs and Observations are the entities to be exchanged
- Exposing as OSLC-EMS provider.
KPIs + Observation
Artifact
Context for OSLC KM
-
Multiple domains
- Different types of artifacts
- Need of intra-operability
- Intra-domain
- Need of interoperability
- Inter-domain
Real Situation
Point to point connections-> Combinatorial explosion
OSLC
Preliminary Evaluation
- Great effort on interoperability
- Community ( industry ) effort
- Different types of artifacts ( resource shapes )
- OASIS standards (Core, Change Management, etc.)
- ...
Challenges (among others)
- Increase of interoperability complexity when new domains are defined
- Provision of services to all the resource shapes
which leads to the need of a
more universal approach
KCSE
Knowledge -centric Systems Engineering
KCSE: notion of an OSLC bus
Representation
Services
COMMON
How many different types of artifacts are generated during the development life-cycle ?
tools, formats, protocols, query languages , etc.
Representation
Needs and Challenges
- A common representation model
- Interoperability
- ...
Services
- Language Uniformity
- Quality checking
- Visualization
- Traceability
- Human machine interface
- ...
Needs and Challenges
- A common representation model
- Interoperability
- Knowledge Management processes
- Natural language to express queries
- ...
OSLC-KM
New domain
New resource shape
RDF
Resource Description Framework
- Common & shared Data model
-
Triples
- (subject, object, predicate)
- Binary relationships
- Underlying Directed Graph
- W3C Recommendation (2004)
- Query languages
RDFS
RDF Schema
- Data modeling for RDF data
- Classes
- Properties (domain & ranges)
- RDF serialization
- W3C Recommendation (2004)
OWL
Ontology Web Language
- Vocabulary for defining formal ontologies
- Logic-oriented
- RDF serialization
- Flavours (2.0): EL, QL, RL
- W3C Recommendation (2012, v2.0)
RIF
Rule Interchange Format
- Exchange of business rules
- Rule-oriented
- Flavours: Core, PRD, BLD, etc.
- XML serialization
- W3C Recommendation (2013, v2.0)
RSHP
Relationship "arship"
- Property Graph
- Any kind of
relationship
- Arity and Cardinality
- Industry-oriented
- Native tool support
- Queries based on natural language
- First publication 2004
Others
- SBVR
- Semantics of Business Vocabulary and Rules
- ODM
- Ontology Definition Metamodel
- RAS
- Reusable Asset Specification
Preliminary Evaluation
-
RDF good option for exchange data on the web
- Restrictions: arity and cardinality of relationships, lack of native tools, logics, etc.
-
RDFS and OWL
- Oriented to define formal ontologies
-
RSHP
- High level of Expressivity
- Native tool support
- ...
The approach
OSLC
(Data Exchange)
RSHP*
(Internal representation: metadata+contents
and services)
The Specification
Shape for KM resources
Metadata + Contents
Resource Shape
Based on the W3C SKOS Recommendation
Simple Knowledge Organization System
OSLC Core
Provenance*
Access
(W3C HTTP Access)
Metadata
(Dublin Core, traces, etc.)
Contents
(resource shape)
Visualization (SVG)
Summary of Properties
OSLC Defined Resources
- Based on
skos:Concept
- W3C Recommendation SKOS (Simple Knowledge Organization System)
- Ios_Km:Concept
Vocabulary
& Conceptual Model
- Normalization
- Standardization
- Suggestions
- X Breakdown Structures
- ...
Patterns
- Restrictions
- Examples
- Suggestions
Knowledge Management
Application to requirements authoring and requirements quality management
Scenarios...
1- Listing the concepts of a domain vocabulary
2- Standardize a term or text-based description
3-Get synonyms for a term or a text-based description
4-Get the list of patterns to guide the writing of requirements
Real Example
SKOS Concepts through OSLC in CKEditor
Summary
OSLC KM-Knowledge management
- Use of the W3C SKOS vocabulary
- Concepts and relationships are the entities to be exchanged
- Services for: search, trace, naming, visualize, etc.
Metadata + Contents
Artifact
oslc_asset:artifact
An Example...
Process any kind of OSLC Resource or RDF data ...
E.g. Modelica
One implementation
OSLC KM
Knowledge Centric Systems Engineering to govern the development lifecyle
KCSE
Inputs
Outputs
...
Common services
Representation
OSLC KM
Not a dream!
KCSE
Inputs
Outputs
...
Common services
Representation
Advantages
- Standard exchange of data: OSLC
- Enhance expressiveness ( RSHP )
- Reuse of existing standards and vocabularies
- Native Tool support (Knowledge Manager)
- Cross-cutting services (semantic-based)
- Elastic approach
- ...
Drawbacks
- Scope of knowledge management (needs )
- Potential overlapping with other tools and specs
- Need of spread the approach
Evaluation of OSLC KM
-
Knowledge Management: a key process
-
REUSE!
-
- Need of:
- Reuse of standards and service-oriented functionalities (OSLC)
- Take the most for data exchange (OSLC) and representation (RSHP)
- Bring technology to a human-oriented environment (NLP)
- Technical issues
- Completeness of the specification?
- Implementation
Conclusions
- Two main action lines
- Requirements Quality Metrics
- Knowledge Management
- Keypoints:
- Re-use of existing RDF vocabularies
- Good experience with
OSLC4Net
- Change in the JSON Serializer
- JSON format->better performance for large responses
OSLC Domains
Technical issues
Future work
-
Merge and extend the spec with other knowledge standards
-
E.g. STEP, Industrial Internet activities
-
-
Refine of the resource shape
-
Full implementation and support to all services
-
Integration patterns governed by knowledge
-
...
Industrial Linked Data
Credits
- https://www.edx.org/course/software-architect-code-building-digital-uc3mx-inf-1x
- https://slides.com/josemariaalvarez/oslc-km-incose-2015-15
Speakers
-
Dr. Jose María Alvarez-Rodríguez
- Carlos III University of Madrid, Spain
- Member of INCOSE and the OSLC RM working group
- E-mail: josemaria.alvarez@uc3m.es
- WWW:
-
Prof. Dr. Juan Llorens
- Carlos III University of Madrid, Spain
- Member of INCOSE
- CTO of The Reuse Company Inc.
- E-mail: llorens@kr.inf.uc3m.es
- WWW:
Data modeling
- Need of logic formalism ?
- Requirements quality metrics match OSLC EMS
- Multilingual data in OSLC APIs
- On-line vs Reference vs Proxy resources
- ...
Infrastructure & Data integration
- Convergence OSLC and RDF Data Shapes , W3C LDP, etc.
- Joint efforts in OSLC specs. and new domains
- OSLC APIs in other languages
- Microservices
- ...
- Federated queries and stream processing
- Trust and Privacy
Requirements Management-CRYSTAL Final Dissemination Event
By Jose María Alvarez
Requirements Management-CRYSTAL Final Dissemination Event
Requirements Management presentation in the CRYSTAL Final Dissemination Event in conjunction with 5th European Conference on Interoperability for Embedded Systems Development Environments
