model based systems engineering을 통한 요구사항 기반 시스템 … · 시스템 분석 및...

Model Based Systems

Engineering을 통한 요구사항

기반 시스템 개발 방안

김대승부장

[email protected]

Rational Software, 한국IBM

1

Agenda

� Systems Engineering

� What is Model Based Systems Engineering

� MBSE Solution

� 사례

2

IBM, An Systems Engineering Solution Provider

Systems Engineering

3

Systems Engineering for Dummies

시스템공학이란?

� Systems Engineering Definition

– Systems Engineering is an interdisciplinary

approach and means to enable the

realization of successful systems. It focuses

on defining customer needs and required

functionality early in the development cycle,

documenting requirements, then proceeding

with design synthesis and system validation

while considering the complete problem.

(International Council on Systems

Engineering)

4

Systems Engineering의효과?

� 요구사항과인터페이스를잘이해하기위해프로젝트초기단계에서좀더노력을기울일수록프로젝트의기간은더단축된다.

5

� 시스템엔지니어링에대한적절한투자(10~15%)는궁극적으로프로젝트의성공(품질/비용/납기)확률을높힘.

INCOSE, Understanding the Value of Systems Engineering (June 2004)

시스템 엔지니어링에 대한 적절한 투자??

6

시스템엔지니어링프로세스

Requirement Analysis

- Mission analysis

- Operations analysis

- Functional req.

- Performance req.

- Physical configuration

Functional Analysis

And Allocation

- Top down decomposition

- Performance allocation

- Functional flow diagram

- Timeline analysis

- Functional architecture

Design Synthesis

- Physical architecture

- Alternate design analysis

- Optimization

- Effectiveness analysis

- Preferred design selection

- Documentation

System Analysis

& Control- Trade anaysis

- Utility analysis

- Risk analysis

- Ops. effectiveness

- Configuration mgmt.

- Technical reviews

Requirements

Analysis시스템 분석

및 통제

과정입력- 고객 요구

- 기술 기반- 출력 요구

- 의사결정요구

- 사양과 표준과정출력개발단계 의존

-의사결정사항-형상

-사양과 대안

Design Synthesis

Functional Analysis

And Allocation

Verification

Requirements

Loop

Design Loop

Verification

Source : Systems Engineering Guidebook written by James N. Martin

7

Requirements

Analysis시스템 분석

및 통제

Design

Synthesis

Functional Analysis

And Allocation

Verification

Requirement

s Loop

Design Loop

Verification

시스템엔지니어링프로세스(계속)

과정 입력- 고객 요구

- 기술 기반- 출력 요구

- 의사결정요구- 사양과 표준

과정 출력개발단계 의존

- 의사결정사항-형상

-사양과 대안

사양서 도출 작업

ORD

SSS

8

StakeholderRequirements

Perception of need Operational use

ComponentRequirements

Component

test

Subsystem

test

SubsystemRequirements

System

test

SystemRequirements

Acceptance

test

satisfies

satisfies

satisfies

validates

validates

validates

validates

Customer

Suppliers

Customer

Suppliers

Customer

Suppliers

Requirements

Analysis시스템분석

및통제

Design Synthesis

Functional Analysis

And Allocation

Verif

ication

Requir

ements Loop

Desig

n Loop

Verif

ication

과정입력

-고객요구

-기술기반

-출력요구-의사결정요구

-사양과표준과정출력

개발단계의존

-의사결정사항

-형상

-사양과대안

사양서도출작업

O

RD

SSS

Requirements

Analysis시스템분석

및통제

Design Synthesis

Functional Analysis

And Allocation

Verif

ication

Requir

ements Loop

Desig

n Loop

Verif

ication

과정입력

-고객요구

-기술기반-출력요구

-의사결정요구


개발단계의존

-의사결정사항

-형상-사양과대안


O

RD

S

SS

Requirements Analysis

시스템분석

및통제

Design Synthesis

Functional Analysis

And Allocation

Verif

ication

Requir

ements Loop

Desig

n Loop

Verif

ication

과정입력

-고객요구

-기술기반

-출력요구-의사결정요구


개발단계의존

-의사결정사항

-형상

-사양과대안


O

RD

SSS

시스템개발수명주기 – End-to-End Traceability

9

Agenda



� MBSE Solution

� 사례

10

� Model Based Systems Engineering (MDSE) 은

복잡성을효과적으로다루기위해모델링을

활용하여시스템엔지니어링을체계적인접근

방법

– 모든요구사항이만족하는지, 비기능적

제약조건을만족하면서기능적거동이잘

동작하는지를식별하는데도움

– 모델은시스템개발과연관된 stakeholders 간의

의사소통을향상

– 모델은복잡성을관리할수있는효과적인도구

– 시스템개발시모델을주요산출물

� SysML은시스템엔지니어들이시스템모델링을

할수있도록지원하는표준모델링언어

What is Model Based Systems Engineering?

11

Parametric Diagram

Requirements Diagram

Block Definition Diagram

Internal Block Diagram

Use Case Diagram

Sequence Diagram

Activity Diagram

Statechart Diagram

SysML Diagram

Structural Diagrams Behavioral Diagrams

Parametric Diagram


Block Definition Diagram

Internal Block Diagram

Use Case Diagram

Sequence Diagram

Activity Diagram

Statechart Diagram

SysML Diagram

Structural Diagrams Behavioral Diagrams

UML 2.1 SysML 1.0

UML4SysML

UML 2.1 SysML 1.0UML 2.1 SysML 1.0

UML4SysMLUML4SysML

필수 SysML다이어그램

12

Parametric Diagram

Parametric relationship between system properties

itsNewtonLaw:NewtonLaw

1 «ConstraintProperty,ConstraintBlock »

force = mass * acceleration

force:Newtons

mass:Kg

acceletation:MetersPerSec^2

force

«Attribute »mass

«Attribute »

acceleration

«Attribute »

mass

«Attribute »

acceleration

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »




force:Newtons

mass:Kg

acceleration:MetersPerSec^2

force

«Attribute »mass

«Attribute »

acceleration

«Attribute »

mass

«Attribute »

acceleration

«Attribute »


• Taxonomy of requirements

• Relationship between model

elements and requirements

SRS_Req_1.1

SRS_Req_1.1.1

« Requirement»

SRS_Req_1.1.1.x« derive »

« trace » « satisfy »

SS_B

Uc2Scenario5

« verify »

Uc2

SRS_Req_1.1

« »

SRS_Req_1.1.1.x

SS_B

« block »

Uc2Scenario5

« testCase »

Uc2Uc2

SRS_Req_1.1.1

« Requirement »« Requirement »

« Requirement »

A1 A2

SuD

«block»

SS_A

«block»

11 1

SS_B

«block»

1

1 1 1 1

A1A1 A2

SuD

«block»

SS_A

«block»

11 1

SS_B

«block»

1

1 11 11 1 1 11 11 1

Block Definition Diagram:

Structural elements (Blocks) and

their relationship

itsSuD1 «block»

itsSS_A

1 «block»

pSS_BpA1

itsSS_B

1 «block»

pSS_ApA2pA2

pA1

itsA11 «Actor»

pSuD

itsA2

1 «Actor»

pSuD

itsSuD1 «block»

itsSS_A

1 «block»

pSS_BpA1

itsSS_B

1 «block»

pSS_ApA2pA2

pA1

itsA11 «Actor»

pSuD

itsA2

1 «Actor»

pSuD

Internal Block Diagram:

Realization of system structure

Structure Diagrams

Parametric Diagram

Parametric relationship between system properties




force:Newtons

mass:Kg


force

«Attribute »mass

«Attribute »

acceleration

«Attribute »

mass

«Attribute »

acceleration

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »mass

«Attribute »

acceleration

«Attribute »

mass

«Attribute »

acceleration

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »mass

«Attribute »

acceleration

«Attribute »

mass

«Attribute »

acceleration

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »




force:Newtons

mass:Kg


force

«Attribute »mass

«Attribute »

acceleration

«Attribute »

mass

«Attribute »

acceleration

«Attribute »


• Taxonomy of requirements

• Relationship between model

elements and requirements

SRS_Req_1.1

SRS_Req_1.1.1

« Requirement»



SS_B

Uc2Scenario5

« verify »

Uc2

SRS_Req_1.1

« »

SRS_Req_1.1.1.x

SS_B

« block »

Uc2Scenario5

« testCase »

Uc2Uc2

SRS_Req_1.1.1


« Requirement »

SRS_Req_1.1

SRS_Req_1.1.1

« Requirement»



SS_B

Uc2Scenario5

« verify »

Uc2

SRS_Req_1.1

« »

SRS_Req_1.1.1.x

SS_B

« block »

Uc2Scenario5

« testCase »

Uc2Uc2

SRS_Req_1.1.1


« Requirement »

A1 A2

SuD

«block»

SS_A

«block»

11 1

SS_B

«block»

1

1 1 1 1

A1A1 A2

SuD

«block»

SS_A

«block»

11 1

SS_B

«block»

1

1 11 11 1 1 11 11 1

Block Definition Diagram:

Structural elements (Blocks) and

their relationship

itsSuD1 «block»

itsSS_A

1 «block»

pSS_BpA1

itsSS_B

1 «block»

pSS_ApA2pA2

pA1

itsA11 «Actor»

pSuD

itsA2

1 «Actor»

pSuD

itsSuD1 «block»

itsSS_A

1 «block»

pSS_BpA1

itsSS_B

1 «block»

pSS_ApA2pA2

pA1

itsA11 «Actor»

pSuD

itsA2

1 «Actor»

pSuD

Internal Block Diagram:

Realization of system structure

Structure Diagrams

정적 SysML뷰 : SysML artifactsRequirements diagram, Structure diagrams, Parametric diagram

13

SuD use case diagram

1. 시스템범위정의하고요구사항을 use cases로그룹핑

UC1 Black-box activity diagram

2. Use case의기능흐름(storyboard)을정의

Note: Interaction with the environment is

described with SysML action pins

stereotyped <<ActorPin>>

Received/sent messages not associated

with a system operation are described as

an action node stereotyped

<<MessageAction>>

1

2

동적 SysML뷰 : 시스템의동적거동분석(1)

14

3. Black-box activity

diagram으로부터주변환경(사용자, 외부시스템등)과의상호관계를표현하는시나리오도출

UC1 black-box scenarios 3

UC1 block statechart4

4. Activity/Sequence

diagram의정보를종합해서상태기반의거동을표현

동적 SysML뷰 : 시스템의동적거동분석(2)

15

Model Based Systems Engineering

16

MBSE의목표

� 개발하고자하는시스템의기능

식별및도출

� 식별된기능을시스템아키텍쳐에

할당

� 모델실행을통한시스템의검증및

시스템아키텍쳐의 Tradeoff

– 모델실행은초기에시스템을

검증할수있는효과적인방법

– 모델을실행할수없다면

모델에대한테스트를할수

없음.

System FunctionalAnalysis

RequirementsAnalysis

DesignSynthesis

17

Model Based Systems Engineering Process

18


1. Requirements Analysis

� Stakeholder요구사항분석을통해시스템요구사항초안작성

– 시스템이가져야할기능식별

– 비기능적요구사항

– 시스템수준의 Use Cases 식별

� 시스템수준 Use Cases 개수 : 10 ~

15개 (Rule of Thumb)

19


2. System Functional Analysis

� 시스템기능분석단계에서는기능요구사항들을일관된시스템operations으로변환

� Use Case는실행가능한모델로변환되고모델실행으로시스템요구사항을검증

20

System Functional Analysis 수행절차(3가지방법)

21

UC Black box diagram으로부터 Sequence diagram 자동생성

22


3. Design Synthesis

� 식별된기능요구사항을물리적아키텍쳐에할당

� 시스템수준의필요한기능을수행하고,

성능제약조건을만족하는물리적아키텍쳐개발

23

서브시스템으로기능할당(UC white box diagram)

24

UC white box diagram으로부터 Sequence diagram

자동생성

25

MBSE의이득

� 모델실행을통한요구사항의완전성및정확성검증

� 요구사항의가시화로효과적인의사소통

� Trade-off study를통한최적의아키텍쳐도출

26

Systems engineering handoff

� Model-Based Systems Engineering에서시스템엔지니어링팀이서브시스템

개발팀에게전달하는가장중요한핵심산출물은실행가능한시스템아키텍쳐

모델임.

� HW/SW 요구사항스펙문서는공통저장소에서자동생성

� 프로젝트조직의구조및특성에따라 handoff의범위및내용이달라짐

27

Agenda



� MBSE Solution

� 사례

28

IBM Rational solution

for systems and software engineering

Open Lifecycle Integration

Planning, Change/ Configuration Management

Quality Visualize, Analyze and, Organize

Best Practices and Services

IBM Rational Solution

for Systems and Software Engineering

Requirements

Architecture, Design and Development

29

Rational DOORS

Systems requirements management and traceability

� 고객과시장의필요를수집하고문서화

� 고객의요구사항의누락방지

� 프로젝트범위및변경통제

� Compliance를증명하기위한추적성확보

Requirements Management

Search, filter on attributes

Traceability between related

artifacts

Impact & Coverage analysis

Review & Collaboration

Security & Auditing

DOORS

Test PlansSoftware

Requirements

Design

System ReqsStakeholder Reqs

30

Rational Rhapsody

시스템모델링및요구사항검증

ModelExecution

Model-Driven Testing

Software-Centric

Workflow

Standards-Based MDD

Strategic Reuse

Requirements Visualization

� 시각적인모델링을통한요구사항분석및의사소통향상

� 실행가능한모델을통한조기설계검정

� SW, HW와기구부문으로기능요구사항할당및관리

� 변경요청에대한영향도분석

31

IBM Collaborative

Design Management

Rational Rhapsody Design Manager

Design Reviewer

Architect

SystemsEngineer

SoftwareDeveloper

RequirementsAnalyst

QualityEngineer

Rational Rhapsody Design Manager

시스템및 SW 설계팀간의협업향상

� 설계산출물의허브

– 설계요소들의중앙저장소 –검색, 리뷰,

분석및재사용

– 설계요소들과다른산출물(요구사항,

테스트케이스등)과의추적성

– 가시적추적성관계

32

Agenda



� MBSE Solution

� 사례

33

Jaguar Land Rover – SW검증시간을 90% 감소

� 영국에본사를두고있으며, 3개의브랜드,

Jaguar, Land Rover, Range Rover를관리

� 2008년인도 Tata Motor가인수

� 분산개발환경하에서복잡한요구사항을잘

관리해서성공적으로신속히시장에

출시하기위함.

� 솔루션

– IBM Rational DOORS

– IBM Rational Rhapsody

– IBM Rational ClearCase/ClearQuest

� 효과

– SW검증시간과버그원인검출시간을

90% 감소

34

Boeing

� Corporate Standard for UML development per

System and Software HILT May, 2006.

� Example projects where Rhapsody is being used

or is specified.

– BMD (Ballistic Missile Defense)

– JUCAS

– Airborne Laser

35

Cassidian (EADS Defense & Security Systems)

� Talerion

– UAV, Harmony SE based development

process

� Eurocopter

– Heavy use of MDSE

– Process based upon Harmony SE

� Defense Electronics

– A400M:

Mission Management System,

Defensive Aids Subsystem,

– Obstacle Warning System for

helicopters

� Military Aircraft

– A400M:

Terrain Masking Low Level Flight

System

에어버스 A380

유로파이터

유로콥터 타이거

37

© Copyright IBM Corporation 2013. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.IBM, the IBM logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

www.ibm.com/software/rational

Senior Rational Technical Specialist

[email protected]

김 대 승 부장

model based systems engineering을 통한 요구사항 기반 시스템 … · 시스템 분석 및...

Documents