자동차 분야 rhapsody 활용 사례 - ibm · 2013-09-05 ·...
TRANSCRIPT
1. M사 : Rhapsody for ISO 26262 적용사례
2. L사 : Rhapsody for AUTOSAR 적용사례
Agenda
2
RHAPSODY FOR ISO 26262
M사 : ISO 26262 적용 사례
3
� SW 개발전과정에서양방향추적성을확보할수있는가?
� 회사의표준템플릿을자동생성하여개발공수를줄일수있는가?
� Rhapsody를 Customize해서사용할수있는가?
� SW 개발전과정에대한 Coverage Analysis 및 Impact Analysis를할수있는가?
� Requirement Coverage를확보할수있는가?
고객니즈 : ISO 26262, Part6 준수
4
* ISO 26262,Part 6에서요구되는 Traceability : 요구사항에대해 SW 개발전과정에서의추적성을요구
적용방안 : ISO 26262 양방향추적성
5
OEM Requirement
System Requirement
Software Use Case Model
Software Design Model
Software Implementation Model (C Code)
Matlab/Simulink Model (C Code)
Software Test Model
Trace
Trace
Trace
Trace
DOORS
Rhapsody
Gateway
� 모델기반제품개발체계구축
� 양산프로젝트적용확대
� 모델기반시스템설계�모델기반 SW 개발확대
� 양산프로젝트적용확대 (AUTOSAR 기반)
� 적용효과
� Rhapsody를통해 ISO 26262. Part 3, 4, 6에서요구되는전개발과정에서의양방향추적성을확보할수있음.
� 개발기간중요구사항의 Coverage를파악할수있어개발진척관리가가능함.
� Coverage & Impact Analysis를할수있어변경요청에대한빠른대응이가능함.
� Rhapsody Customize 및자동화를통한개발자의업무량감소.
적용결과
6
적용상세 : ISO 26262 준수한모델기반개발절차
7
OEM Requirement•OEM요구사항
•Word / Power Point / Excel 등문서기반
•OEM요구사항을정제한시스템요구사항
•요구사항관리도구 (DOORS)
•모델기반소프트웨어요구사항 (시나리오기반)
• UML 도구 (Rhapsody)
•모델기반소프트웨어설계및구현
• UML 도구 (Rhapsody)
• Manual Code (C Code)
• Simulink Model (C Code)
•모델기반소프트웨어테스트 (Testing Profile)
•요구사항 기반테스트
•모델기반테스트자동화 도구 (Test Conductor)
System Requirement
Software Use Case Model
Software Design Model
Software Implementation Model (C Code)
Matlab/Simulink Model (C Code)
Software Test Model
Trace
Trace
Trace
Trace
1. OEM Requirements
8
OEM 요구사항
Rhapsody
(Gateway)
요구사항추출Coverage : 0%
챠량 SW 표준 워크숍
2. System Requirements
9
OEM 요구사항
Rhapsody
(Gateway)
요구사항추출
DOORS
시스템요구사항분석(Derived Requirement)
Word – DOORS
Coverage Link 설정
Coverage : 100%
3. SW Usecase Model
10
소프트웨어기능정의 (Use Case) 기능별시나리오정의
Requirement – Use Case 추적성설정
Coverage : 100%
4. Software Design Model
11
소프트웨어구조설계 소프트웨어동작설계
Use Case – Class 추적성설정
* 소프트웨어모듈 = Class
Coverage : 100%
5. SW Implementation Model
12
소프트웨어코드작성
6. SW Test Model
13
테스트구조설계 테스트동작설계
Class – Test Case 추적성설정
Coverage : 100%
� Requirement Coverage Ratio 제공
• System Requirement : 10개
• Use Case : 2 개
• Design : 3개
Coverage & Impact Analysis
14
RHAPSODY FOR AUTOSAR
4.0.R3
L사 : AUTOSAR 적용사례
15
� AUTOSAR 4.0.R3 표준을준수하는시스템을개발할수있는가?
� ARXML자동생성및가져오기를지원하는가?
� AUTOSAR System 설계를지원하는가?
� AUTOSAR Application 설계를지원하는가?
� EB tresos studio를지원하는가?
고객니즈 : AUTOSAR 시스템개발
16
� System Modeling : Rhapsody
� Behavior Modeling : Simulink
� RTE Conf. & BSW :
� EB tresos Studio & AutoCore
적용방안 : Rhapsody + EB
17
(Matlab Simulink)
Embedded Coder
Rhapsody
Simulink
� AUTOSAR 4.0.R3 선행개발프로젝트적용
� AUTOSAR System & Application 설계
� AUTOSAR XML 생성
� AUTOSAR XML Import-Merge 통합
� EB tresos Studio 연동
� AUTOSAR XML 내보내기/가져오기지원
� 적용효과 :
� Rhapsody를통해 AUTOSAR System 아키텍처 (그래픽컬)설계가능
� AUTOSAR SW/C 아키텍처설계
� AUTOSAR ECU 토폴로지설계
� AUTOSAR Systems 설계
� SW/C Internal Behavior (그래픽컬) 설계가능
� SW/C와소스코드파일간매핑및소스코드생성지원
적용결과
18
적용상세 : AUTOSAR Software Component 개발영역
19
AUTOSAR Software Component는 다음과 같이 3가지 수준에서 작성
20
• SW/C 타입 정의
• SW/C 간 상호관계(Interaction) 정의
• SW/C와 RTE 간 Interface 정의
• RunnableEntity 정의
• SW/C와 소스파일 간 관계 정의
• RunnableEntity와 Function Code 매핑
Rhapsody = System Modeling Tool + Behavior Modeling
Tool
21
C Code BMT
Rhapsody BMT
Simulink BMT
Statemate BMT
Rhapsody Systems Modeling Tool
도구 구분 AUTOSAR System Modeling Tool AUTOSAR Behavior Modeling Tool
비교� SW Architecture를정의
� Algorithm을통합
� Algorithm을구현
� SW Architecture에삽입
� AUTOSAR System Modeling
� AUTOSAR Behavior Modeling
� RTE Configuration & AUTOSAR Basic Software
AUTOSAR Workflow
22
� System Modeling : Rhapsody
� Behavior Modeling : Simulink
� RTE Conf. & BSW :
� EB tresos Studio & AutoCore
AUTOSAR Workflow : Rhapsody + Simulink + EB
23
(Matlab Simulink)
Embedded Coder
Rhapsody
Simulink
� System Modeling : Rhapsody
� Behavior Modeling : Rhapsody BMT
� RTE Conf. & BSW : EB tresos Studio & AutoCore
AUTOSAR Workflow : Rhapsody + EB
24
� Software Component들이상호작용하는 Function System을정의
� VFB 상에서동작하는 Software Architecture 정의
1. AUTOSAR SW/C 아키텍처설계 [1]
25
� Software Component들이상호작용하는 Function System을정의
� VFB 상에서동작하는 Software Architecture 정의
1. AUTOSAR SW/C 아키텍처설계 [2]
26
� ECU타입과 ECU의 Communication Port를정의
� ECU 간의 Physical Communication Topology를정의
� Electrical Architecture 정의
2. ECU 토폴로지(Topology) 설계
27
� AUTOSAR System을정의
� AUTOSAR SW/C가개별 ECU에어떻게매핑되는지정의
� ECU간에 Communication Matrix를정의
3. AUTOSAR System 설계
28
� Atomic Software Component의 Internal Behavior를정의
� SW/C와 RTE간의 Interface를정의
4. AUTOSAR SW/C Internal Behavior 설계
29
� 소스코드파일과 SW/C 간매핑관계정의
5. AUTOSAR SW/C Implementation 설계
30
� AUTOSAR XML Document Import & Export
6. AUTOSAR XML Document 생성(Export)
31
© 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