Essence for Systems Engineering
(Systems Engineering Essence)
INCOSE
Russian
Chapter
Berlin
20 June 2013
Context
Roadmap (http://semat.org/?p=863):
• 1st of August 2013 – define model and architecture ontological status in
the Essence
• 1st of September 2013 – publish first draft of the Essence kernel
extension for Systems Engineering
• 1st of December 2013 – map Essence Systems Engineering kernel
elements to ISO 15926
• End of December 2013 – publish first version of the “Essence systems
engineering kernel elements (mapped to the ISO 15926)”
Achievements:
• Proposal discussed at the INCOSE Russian Chapter on 22nd of May 2013
(http://incose-ru.livejournal.com/42524.html).
• Proposal disussed at MESI conference on 6-7th of June 2013
(http://www.mesi.ru/our/events/detail/121699/) with Ivar Jacobson
and wider audience.
2
Language, kernel, practice
Language
Kernel
(abstract)
Requirements
Practices
(specific for situation)
ConOp
Stakeholders
...
Explore
possibilities
Budget
Perform interview
...
Brainstorm
3
Alpha: states = checklists : checkpoints
ALPHA -- Abstract-Level Progress Health Attribute.
4
Engineering project alphas: as is
Customer
< fulfils
scopes and
constrains
System of
Interest
^ produces
^
Work
supports >
Requirements
Endeavor
Stakeholders
Stakeholders
Opportunity
use and
consume >
Solution
< provide
focuses >
Set up to
address >
Opportunity
Opportunity
< plans and performs
Team
Way of
Essence Tutorial May 25, 2013. San Francisco CA USA
Working
5
5
Systems engineering
• Intuition: V-model
• Focus on system definition (more resources to
define the system, i.e. more work with bits
rather than atoms)
• Agile in the work with bits, cascade in the
work with atoms.
• Architecture and design are of the same
importance as requirements (constraints to
design solutions, focusing in Essence terms).
6
2D representation of Life Cycle:
practices executed in time
validation
define needs
acceptance
verification
integration
architecturing
verification
design
System
definition
parts manufacturing
System
realization
[System
operation]
7
Requirements, Architecture, Design and
System: state redistribution is needed
System
definition
(bit)
*Requirements defined
*design
System
implementation
(atoms)
8
Essence and Architecture
• Not present in current standard as alpha:
«architecture wasn’t addressed explicitly in many
software projects»
• Required by systems engineering methodology
(design should be architectural)
• Current Essence kernel choices for architecture
modeling:
– Architecture is an independent alpha
– Architecture is a sub-alpha of alpha “System”
– Architecture is a pattern
9
Trade-off options
• System definition (result of system definition activities
in V-diagram) alpha with requirements, architecture
and design as sub-alphas (with system descriptions as
work products): with redistribution of states from
System realization alpha
• Architecture and design as first class kernel alphas
• Architecture and design as sub-alpha of system
• Architecture as Patterns (according to Ian Dietz – link
between requirements and system like GORE patterns
is link between Opportunities/Goals and
Requirements)
10
Proposal: kernel modification
Customer
< fulfils
scopes and
constrains
Work
System
Realization
^ produces
^
Endeavor
supports >
System
Definition
Stakeholders
Stakeholders
Opportunity
use and
consume >
Solution
< provide
focuses >
Set up to
address >
Opportunity
Opportunity
< plans and performs
Team
Way of
Essence Tutorial May 25, 2013. San Francisco CA USA
Working
11
11
System Definition
vs System Realization
• System Definition = Requirements, Architecture,
Design
• Composed from models that grouped by views –
generalized from ISO 42010
• System definition frameworks are sub-alphas of
way-of-working (generalized from ISO 42010
architectural framework)
• System definition languages are sub-alphas of
way-of-working too («language» is a practice in a
method aka «resource» - «language» in ISO
24744)
12
ISO 42010
Map to Essence
Solution area of
concern alphas
Work products (i.e. in practices)
Way-of-working
sub-alphas
13
System definition and realization
(ISO 42010 generalization)
Way-of-working
sub-alphas
(specified by
standards)
Solution area of concern alphas & V-model
verification
System
Definition
Sub-alphas
verification
Solution Area of Concern Alpha States
System
Definition
System
Definition
Conceived
It is clear how the system will be
defined.

It is clear what success is for
the new system.

Viewpoints are agreed upon.

The approach to concord
descriptions among the
stakeholders has been agreed.

The description change
management mechanisms have
been agreed.
Consistent
Used for Production
Used for Verification
System definition is used for system
production.
System definition is used for testing.

Descriptions are documented
and available for the team and
stakeholders.

The origin of the description is
clear.

Descriptions are examined.

Contradictory descriptions have
been identified and are dealt
with.

The team understands
descriptions and agrees to
implement them.

The system implementing the
descriptions is accepted be the
stakeholders as worth realizing.


System
Realization
Raw materials
Parts


Facilities for manufacturing
parts from the raw materials are
available.
Enough of the descriptions are
ready for starting system
realization.

Realization technologies have
been defined.


Part of the team responsible for
system realization
acknowledges available
descriptions sufficient to realize
the system.

Tests, success criteria and test
methods have been defined.

Parts of the system have been
produced and/or purchased and
checked.

Some functions of the system can
be exercised and key
characteristics can be measured.

Key system characteristics have
be demonstrated.

Integration schedule has been
agreed.

Critical interfaces have been
demonstrated.

Integration works are ready to
start.

The integration with other existing
systems has been demonstrated.
System definition is used for
gathering information about
state of the operational system
realization.

System definition within
information about the state of
the operational system is used
for making decisions about
maintenance, repair, and
modernization.
4/6

System definition is used for
making decision about system
disposal or operation extension.

System definition shows
absence of undesirable
consequences (e.g. environment
pollution) through system
disposal.

System definition is used for
planning and performing
disposal or recycling of the
system realization.
5/6
3/6
6/6
System
Realization
Ready
System
Realization
Operational
The systemема (as a whole) has been
accepted for deployment in a live
environment.

The functionality of the system has
been tested.

Level of defects is acceptable for the
stakeholders.

Retired
The system is in use in a live
environment.
The realized system is no longer
supported and disposed and/or recycled.

The system has been made
available to the stakeholders
intended to use it.
Setup and other user documentation
is available.

At least one example of the
system is fully operational.

The stakeholder representatives
accept the system as fit-for-purpose.


Configuration of the system to be
handed over to the stakeholders is
known.
The system is fully supported to
the agreed service levels.

The stakeholder representatives want
to make the system operational.

The system is fully supported to the
agreed service levels.
The relevant stakeholders agree
that system has to be tested.
Parts manufacturing works are
ready to start.
2/6
System definition is used for system
disposal.

System
Realization
The system has been assembled from
the parts and is ready for testing.

System definitions is used by
stakeholders for operation.
Stakeholders agree with test
scope.
3/6
Demonstrable
Parts production and logistic
schedule has been agreed.
1/6
There are no missed parts of
the system definition that make
testing impossible.
System
Realization
Parts have been produced and are ready
for integration.


Used for Disposal
Used for Operation
Issues occurring during system
realization lead to the re-work
and actualization of the system
definition.
2/6
System
Realization
Raw materials for system
realization are available and
allow manufacturing of the
parts with required properties.

System
Definition
System
Definition
Consistent System definition has been
created.
1/6
Raw materials for system realization
are available and ready parts
manufacturing.
System
Definition
System
Definition
4/6
5/6

The system realization has been
replaced or discontinued.

The system is no longer
supported.

There are no “official”
stakeholders who still use the
system.

Updates/ modifications to the
system will no longer be produced.

All material components of the
system are re-used or have been
properly disposed.
16
6/6
Thank you!
Anatoly Levenchuk (Lead scientist)
http://ailev.ru
ailev@asmp.msk.su
(President of INCOSE Russian Chapter)
Victor Agroskin (ISO 15926 liaison)
vic5784@gmail.com
Andrey Bayda (SEMAT liaison)
andrey.a.bayda@gmail.com
17