Modelagem Do Projeto de Sistemas: Aula 4: MBSE and The Process of Project: Requirements

PMR 5020
Modelagem do Projeto de Sistemas

Aula 4: MBSE and the Process of Project: requirements
Prof. José Reinaldo Silva
reinaldo@poli.usp.br
Escola Politécnica da USP PMR5020

1

Recapitulando
Formal
Eliciação,
Análise de Requisitos
Modelagem de requisitos
Validação
Demanda por evolução
Ø Especi cação
Contextualização Modelagem preliminar

Encapsulamento Modelagem Formal
Prático Treinamento
Plano de eliminação
Veri cação
Teste Preliminar
Protótipo
Sistema
Deployment
Teste de Campo
Planejamento da
manutenção

2
fi
fi
Recapitulando
Methods and
Practice
Systems Design
Approach
Design Paradigms
Structured Object-Oriented
Design Design
Building System Engineering Domain


3

Recapitulando
As lições a s em aprendidas…
Paradigmas
Desenv. Estruturado Desenv. Orientado
a Objetos
Modelagem por re namentos
Modularização
Alternancia entre a abordagem
Completeza comportamental
top-down e bottom-up.

4
er
fi
Recapitulando
The “V" Model


5
Recapitulando

6

7
Martin’ s systems are:
Context System
Intervention System
Realization System
Deployed System
Collaboration System
Sustainment System
Competition System

8
Competing System
Deployment System
Sustainment System
Collaboration System
traceability Deployed System

deployment
Context System
communication
requirements Intervention System

abstraction
design
Development Process
A Service view of systems design

9

10

11
System Design is still an open problem.
A yellow brick road?

12
The f st steps: defining the system
Step 1: identifying context S and defining the problem P
(Project statement)
Step 2: Identifying objects (components) and

Its relationship (ERA model)
(Relational model)
Step 3: Meta-modeling: put everything in a more

Disciplined (semiformal) language as UML, IDEF0, KAOS, etc.
(Capture the rationales)

13
ir

Our big challenge today is to answer the question: how

could we scale the concepts discussed so far to large
and complex (automated) systems, or how could we
apply all this knowledge effectively to real-life
projects?
Model Driven Engineering

14
Principal Engineer at NASA's
Jet Propulsion Lab
Survey of Candidate Model-Based Engineering (MBSE) Methodologies, Rev. B, May 23, 2008 - INCOSE MBSE Initiative

15
Antes de discutir a metodologia, vamos
discutir alguns conceitos e terminologia.

16
Basic Definitions: process
A Process (P) is a logical sequence of tasks performed to achieve a

particular objective. A process de nes “WHAT” is to be done, without
specifying “HOW” each task is performed. The structure of a process
provides several levels of aggregation to allow analysis and de nition to
be done at various levels of detail to support different decision-making
needs.

17
fi
fi
Basic Definitions: methods
A Method (M) consists of techniques for performing a task, in
other words, it de nes the “HOW” of each task. (In this context,
the words “method,” “technique,” “practice,” and “procedure” are
often used interchangeably.) At any level, process tasks are
performed using methods. However, each method is also a
process itself, with a sequence of tasks to be performed for
that particular method. In other words, the “HOW” at one level
of abstraction becomes the “WHAT” at the next lower level.

18
fi
Basic Definitions: tools
A Tool (T) is an instrument that, when applied to a particular
method, can enhance the ef ciency of the task, provided it is
applied properly and by somebody with proper skills and training.
The purpose of a tool should be to facilitate the accomplishment of
the “HOWs.” In a broader sense, a tool enhances the “WHAT” and
the “HOW.” Most tools used to support systems engineering are
computer or software-based, known as Computer Aided Engineering
(CAE).

19
fi
Methodology is something else…
Based on these de nitions, a methodology can be de ned as a

collection of related processes, methods, and tools. A methodology is
essentially a “recipe” and can be thought of as the application of
related processes, methods, and tools to a class of problems that all
have something in common.
Bloomberg, Jason and Ronald Schmelzer, Service Orient or Be Doomed!, John Wiley & Sons: Hoboken, New Jersey, 2006.

20
fi
fi
Everything works in an environment…
An Environment (E) consists of the surroundings, the external objects,
conditions, or factors that in uence the actions of an object, individual person, or
group. These conditions can be social, cultural, personal, physical, organizational,
or functional.
The purpose of a project environment should be to integrate and support the use
of methods and the tools used in the project. An environment enables (or
disables) the “WHAT” and the “HOW.”

21
fl
Darcy Ribeiro

22
To come up with a project, we need to organize
all this… in a life cycle.

23
NASA Project Lifecycle

24
To come up with a project, we need to organize
all this… in a life cycle.
Eliciação,
Validação

Ø Especi cação
Contextualização Modelagem preliminar

Encapsulamento Modelagem Formal
Treinamento Veri cação
Plano de eliminação Teste Preliminar
Protótipo
Sistema
Deployment
Teste de Campo
Planejamento da
manutenção

25
fi
fi
It is also possible to reuse part of the design
work by using “reference models” normally
synthesized in standards.

26
Interaction
Process
Knowledge

27

28
… as
is related to
smoke re
Projects are related to documentation

29
fi
30
1. Finding the right documents
2. Version control
3. Change management
4. Scalability and flexibility
One of our customers told us about a project that involved 290 spreadsheets that
contained somewhere close to 8,000 wires. One spreadsheet alone had 1,000
instruments and 169 columns for data entry!
5. Multi-user collaboration
6. Multiple database
7. Backup and security
8. Management across the project life cycle
9. Compliance with various standards
10.Reinventing the wheel (reusability)

31

Fundamentação matemática para o MBSE

A. Wayne Wymore (T3SD)
1927-2011
Wymore, A. Wayne, A Mathematical Theory of Systems Engineering: The Elements ,

John Wiley & Sons: New York, NY, 1967.
Wymore, A. Wayne, Model-Based Systems Engineering , CRC Press, Inc.: Boca

Raton, FL, 1993.
Wymore, A. Wayne, “Contributions to the Mathematical Foundations of Systems

Science and Systems Engineering,” Systems Movement: Autobiographical
Retrospectives, The University of Arizona, Tucson, AZ, 2004.

32
Wymore proposed a tricotyledon theory of system design as he named
the speci c mathematical system theory he developed to facilitate the
process of system design. The proposed three basic spaces of system
design are described shortly.

33
fi
A T3SD (tricotyledon theory of system design)

34
And everything starts with requirements…
A key aspect that is elaborated on in the second part of the MBSE book is Wymore’s
introduction of T3SD and identi cation of the six core categories of system design
requirements (SDR), which he de nes as follows:
SDR = (IOR, TYR, PR, CR, TR, STR) where
i) IOR is the I/O requirement,

ii) TYR is the technology requirement,
iii) PR is the performance requirement,
iv) CR is the cost requirement,
v) TR is the trade-off requirement, and
vi) STR is the system test requirement.

35
fi
fi
SDR = (IOR, TYR, PR, CR, TR, STR) where
i) IOR is the I/O requirement,

ii) TYR is the technology requirement,
iii) PR is the performance requirement,
iv) CR is the cost requirement,
v) TR is the trade-off requirement, and
vi) STR is the system test requirement.

36
MBSE Methodologies
1. IBM Harmony-SE 2. OOSEM 3. RUP
6. OPM (Object-Process Methodology)
ISO/PAS 19450 (Dovi Dori)

4. Vitech 5. JPL

37
Method. Proponent Tool Reference
IBM Harmony-SE IBM not speci c IBM Rhapsody
OOSEM INCOSE not speci c INCOSE/OMG
IBM Rational IBM RUP IBM Rational
Vitech Vitech CORE www.vitech.com
JPL
JPL JPL State DB
Caltech
www.opcat.com
OPM Dov Dori (1995) OPCAT
ISO/PAS 19450

38
fi
fi

OOSEM - Object-oriented System Engineering Method
OOSEM appear in mid 1990’s in an attempt to

reinforce object-oriented method to system design.
It turns into an INCOSE chapter in 2000 and
receive later the support of OMG.
In 2012 Morgan Kauffman published a book by

Friedenthal, Moore, and Steiner with the title “A
Practical Guide to SysML”, where OOSEM is
detached as a method and SysML as the
speci cation language.

39
fi

40

41
Enterprise Architect (SparX)

42
Language, model and meta-model
“The systems engineer’s job is to language the project.”
System
“a metamodel is a model that defines the structure of a modeling language”.

43
Going down to the concrete project

44
Classifying the modeling language
There are two kinds of modeling languages
(1) General Purpose Languages
(2) Domain Specific Languages

45


46
representação
Formal
Eliciação,
Validação

Especi cação
Diagrama
Ø
Contextualização
Encapsulamento
Modelagem preliminar
Modelagem Formal
Prático
Treinamento Veri cação
Plano de eliminação Teste Preliminar
Protótipo
Sistema
Deployment
Teste de Campo
Planejamento da Prof. José Reinaldo Silva
Escola Politécnica da USP

manutenção PMR5020
47
fi
fi
Desafio (teórico e prático):
Identificar o WHAT para um projeto de sistema, e
o seu respectivo WHY (rationale), e colocar isso
em um modelo (uma representação diagramática
e/ou formal).

48


49
Design de Sistemas
O processo de projeto como disciplina
Eliciação,
Existe um processo de projeto que
Modelagem de requisitos precisa ser seguido para aumentar as
Validação chances de sucesso. Este processo
Demanda por evolução não é linear e admite superposição e
Ø Especi cação até integração de etapas.
Contextualização
Encapsulamento Modelagem preliminar
Treinamento Modelagem Formal
Plano de eliminação Veri cação
Teste Preliminar
Protótipo
Em todo processo de projeto a
Sistema documentação é essencial.
Deployment
Teste de Campo
Planejamento da
manutenção

50
fi
fi
Model-Based Requirements Engineering

51
sucssessful Challenged Canceled
60
45
30
15
0
1994 1996 1998 2000 2002 2004 2006 2008 2010 2012 2014 2015 2017

52
https://www.proofhub.com/articles/reasons-why-projects-fail#:~:text=The%20most%20prevalent%20reasons%20for,and%20changes%20in%20project%20goals.

53

54
Why projects fail according the academy

55
Projetos e mega-projetos
ISO/IEC 29100
Classi cação heurística
dos projetos:
Projetos de pequeno porte

Projetos de porte moderado
Projetos de porte médio
Projetos de grande porte
Projetos muito grandes
mega-projetos Complexidade
Impacto Ambiental
Qual é a métrica? Risco e impacto social
Escola Politécnica da USP PMR 3100

56
fi

Motivação financeira

57
Design Sprint req.
specs
design
specs
meio m
inicio
identi ca soluções implementa a

identi ca o
e escolhe uma delas solução escolhida
problema
O Design Sprint foi criado em 2010 por

Jack Knapp e re nado com o time da
Google (Chrome, etc) até se tornar o que é
hoje, que foi lançado em 2012 no Google
Ventures.
https://www.thesprintbook.com/the-design-sprint
Escola Politécnica da USP PMR 3100

58
fi
fi
fi
fi
Design de Sistemas
O processo de projeto como disciplina
Eliciação,
Existe um processo de projeto que
Modelagem de requisitos precisa ser seguido para aumentar as
Validação chances de sucesso. Este processo
Demanda por evolução não é linear e admite superposição e
Ø Especi cação até integração de etapas.
Contextualização
Encapsulamento Modelagem preliminar
Treinamento Modelagem Formal
Plano de eliminação Veri cação
Teste Preliminar
Protótipo
Em todo processo de projeto a
Sistema documentação é essencial.
Deployment
Teste de Campo
Planejamento da
manutenção

59
fi
fi
F l the yell
brick road!
Requirements
engineering
Life cycle
Model-based systems
design (MBSE)
Design Paradigms
Systems design
Systems concepts

60
ol
ow
ow

O exercício para a aula que vem será rever o

design que vocês já zeram para o sistema de
controle de acervo, agora usando o ciclo
preliminar de sistema (sem usar uma linguagem de
requisitos especí ca ainda) que vimos na aula de
hoje.

61
fi
fi
Obrigado
Reinaldo

62

Modelagem Do Projeto de Sistemas: Aula 4: MBSE and The Process of Project: Requirements

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Modelagem Do Projeto de Sistemas: Aula 4: MBSE and The Process of Project: Requirements

Enviado por

Direitos autorais:

Formatos disponíveis

PMR 5020

Modelagem do Projeto de Sistemas

Escola Politécnica da USP PMR5020

Contextualização Modelagem preliminar

Escola Politécnica da USP PMR5020

Building System Engineering Domain

Escola Politécnica da USP PMR5237

Desenv. Estruturado Desenv. Orientado

Modelagem por re namentos

Alternancia entre a abordagem

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

The “V" Model

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

traceability Deployed System

requirements Intervention System

Escola Politécnica da USP PMR5020

Escola Politécnica da USP PMR5020

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Step 2: Identifying objects (components) and

Step 3: Meta-modeling: put everything in a more

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Our big challenge today is to answer the question: how

Model Driven Engineering

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

A Process (P) is a logical sequence of tasks performed to achieve a

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Based on these de nitions, a methodology can be de ned as a

have something in common.

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5020

Demanda por evolução

Contextualização Modelagem preliminar

Escola Politécnica da USP PMR5020

Prof. José Reinaldo Silva

Escola Politécnica da USP PMR5237