D-Case – Collaboration with Modeling environment
Demonstration
D-Case – Collaboration with Modeling environment
2
Abstract
Association Association of of Requirements Requirements and and Functions Functions by by D-Case D-Case
D -Case D-Case
Goal
Requirements Identification / Product Planning
Context
Requirements Definition • •
req [パッ ケ ージ ] AnalysisPkg [REQ_CCS] req [パッ ケ ージ ] AnalysisPkg [REQ_CCS] <
>
CCS <>
CCS
車両は運転者を支援する走行制御機能を搭載する 車両は運転者を支援する走行制御機能を搭載する
<> <> <>
車速 の 設定 （ Set） ID 目標 = FY_CCS_03
ID = FY_CCS_02 CCS起動中に運転者 が「Cruise」ボタン CCS起動中に運転者 を押すと、CCSを停 が「Cruise」ボタン 止する を押すと、CCSを停 止する
ID = FY_CCS_03 CCS起動中に運転者 が「Set」ボタンを CCS起動中に運転者 押すと、現在の速 が「Set」ボタンを 度を設定値として 押すと、現在の速 保持する 度を設定値として 保持する
<>
<>
<>
<>
<>
<>
操作 性
<>
が「Decel」ボタン CCS起動中に運転者 を押すと、設定値の が「Decel」ボタン 速度が下がる を押すと、設定値の 速度が下がる
<>
<>
<>
応答性 ID = RY_CCS_23
加速 度 の測 定 頻度 ID = RY_CCS_33
ID = RY_CCS_23 運転者が操作盤で操 作をすると、CCSは 運転者が操作盤で操 1ms以内に動作モード 作をすると、CCSは を切り替える 1ms以内に動作モード を切り替える
ID = RY_CCS_33 加速度を毎秒10回測定 する 加速度を毎秒10回測定 する
<> <>
に運転者が「 CCS一時休止中 Resume」ボタン に運転者が「 を押すと、一時 Resume」ボタン 休止前の設定で を押すと、一時 CCSを再開する 休止前の設定で CCSを再開する
ID = 加 減速 性 能 RY_CCS_32 ID = RY_CCS_32 最低0.080gの 加速度で加減 最低0.080gの 速する 加速度で加減 速する
<>
車両 の 限界 加 速性 能
0.5g未満の加 速度で加減速 する0.5g未満の加 速度で加減速 する
Requirement Requirement Diagram Diagram
Model Simulation
Association Association of of D-Case D-Case and and Model Model Elements Elements
Context
Architecture Design • •
Context Evidence
Checking Safety Requirements Checking Reliability requirements
CCS再 開（ Resume）
者がブレーキを踏 CCS起動中に運転 むと、CCSを一時 者がブレーキを踏 休止する むと、CCSを一時 休止する
<> <> <> <> <> <> <> <> <> <> <> 車両 の 限界 加 速性 能 加 減速 性能 <>
<>
応答性
<>
ID = RY_CCS_21 運転者は直感的 に操作できる 運転者は直感的 に操作できる
• •
<>
<>
者が「Accel」ボ CCS起動中に運転 タンを押すと、設 者が「Accel」ボ 定値の速度が上が る タンを押すと、設 定値の速度が上が る
<>
加速 度 の測 定 頻度
<>
操作 性 ID = RY_CCS_21
<>
Requirements Validation
車 速の 減 速（ Decel） ID 目 車速 の 加速 （ Accel） ID 目標 = FY_CCS_04 = 標FY_CCS_05 時休 止（ Break） ID CCS再 開（ Resume） ID CCS一 = FY_CCS_06 = FY_CCS_07 ID = FY_CCS_04 ID = FY_CCS_05 ID = FY_CCS_06 ID = FY_CCS_07 CCS一時休止中 CCS起動中に運転 CCS起動中に運転者 CCS起動中に運転
<> <> <>
<>
<>
ID = RY_CCS_24 CCSは現在速度が 50km/h以上かつ CCSは現在速度が 100km/h以下の場 50km/h以上かつ 合のみ起動する 100km/h以下の場 合のみ起動する
<>
Safety Requirements Reliability Requirements
<> <> <> <> <> 目 標 車速 の 加速 （ Accel） CCS一 時休 止（ Break）
<>
<>
止（ Cruise） ID = CCS停 FY_CCS_02
ID = FY_CCS_01 CCS停止中に運転者 が「Cruise」ボタ CCS停止中に運転者 ンを押すと、CCSが が「Cruise」ボタ 起動する ンを押すと、CCSが 起動する
CCS起 動 条件 ID = RY_CCS_24
<>
<>
<> <> <> <> <> 目標 車 速の 減 速（ Decel） 目標 車速 の 設定 （ Set）
<>
（ Cruise） ID = CCS起動 FY_CCS_01
CCS起 動 条件
Sub-Goal
<>
<>
<> <> CCS停 止（ Cruise）
CCS起動 （ Cruise）
Strategy
Sub-Goal
MBD MBD (SysML) (SysML)
Implementing Requirements Verification Spec
System Verification •
Checking Functions
Evidence bdd [パッ ケ ー ジ] AnalysisPkg [BDD_car] bdd [パッ ケ ー ジ] AnalysisPkg [BDD_car]
Parametric Parametric Diagram Diagram
<>
車両 <>
Values 車両
車重 Values 投 射面積 車重 Cd値 投 射面積 空 気抵抗 Cd値 ト ルク 空 気抵抗 トOperations ルク Operations
1
1 <>
1 1
ブレーキ <>
Values ブレーキ
< >
C CS コ ン ト ロ ー ラ
1 1
Values
<>
Values 電子制御スロットル
<>
Values 加速度センサー Values
Values
<>
PI制御 <>
Values PI制御 1 1 Values 1 1Operations
1 1
<>
車両力学制御
Operations
<>
1 1
Values 車 両 力 学 制 1御 Values 1 1 1 Operation
Operation
Operations Operations
1
1 1
< >
1 1
1
1 ユ ー ザ ー I /F <>
Values ユ ー ザ ー I /F
Values スロットル アクチュエータ
1 1
1
<>
1 < >
1 エータ スロットル アクチュ
Values Operations
1
Operations
Operations
1
Values Operations
Operations
Operations Operations
1 1
1 加速度センサー
<>
Values 車速センサー
1 <>
電 子 1制 御 ス ロ ッ ト ル
<>
<>
車速センサー 1
Operations
Operations
1
1
< >
Values C CS コ ン ト ロ ー ラ
Values Operations
1
1
Values Operatio Operatio 1
1 1
1
Block Block Definition Definition Diagram Diagram
Software Design / Equivalence Checking Implementation and Verification Spec (=D-Case)
Verification Verification Using Using Model Model Simulation Simulation at at Early Early Development Development Phase Phase 3
Table of Contents
1. Abstract 2. Apply D-Case to Development Process 3. Effectiveness of D-Case – MBD Collaboration 4. System Configuration 5. Use case of D-Case – SysML Development Environment
4
Apply D-Case to Development Process
Achieve Consensus Building
Achieve Accountability
Making Making Stakeholders’ Stakeholders’ Agreement Agreement about about System System Dependability Dependability
Accomplishing Accomplishing Accountability Accountability at at System System Development Development and and Maintenance Maintenance
•Requirements Validation at Early Development Phase •Continuous Traceability of Requirements and Functions Functions Verification Using Model Simulation at Early Development Phase Association of Association of Requirements D-Case and Model Elements and Functions by DD-Case D -Case D-Case
MBD MBD (SysML) (SysML) Goal
Requirements Identification / Product Planning
Context
Requirements Definition req
[パ ッケ ー ジ ] AnalysisPkg req
Requirements Validation
[REQ_CCS]
[パ ッケ ー ジ ] AnalysisPkg
[REQ_CCS]
<>
CCS <>
CCS
車両は運転者を支援する走行制御機能を搭載する 車両は運転者を支援する走行制御機能を搭載する <> <>
Strategy
<>
<> <> <> CCS起 動条 件
<>
ID = <> 加減 RY _ CC S_ 32速 性 能
応答 性
運転 者= が RY 操 _C 作 CS 盤 _2 で3 操 ID 作 を す る と 、 C CS は
ID = R Y_ CC S_ 33 加 速 度 を 毎 秒 10 回 測 定 する
運転者は直感的 に操作できる
<>
<> I D = RY _C CS _2 3
ID = 80 gの 最低 0 .0 RY _ CC 加速 度 で S_ 加 32 減 速する 最 低 0 .0 80 gの 加速度で加減 速する
1 ms 以 内 に 動 作 モ ー ド 運 転 者 が 操作盤で操 を切 り 替 え る 作 を す る と 、 C CS は 1 ms 以 内 に 動 作 モ ー ド を切り替える
加 速 度 を 毎 秒 10 回 測 定 する
ID = F<> Y_ CC S_ 07
CCS一時 休 止 （Break）
<> <> <> <> 加減 速 性 <> 能 <>
応答 性
<>
<>
CCS再開 （ Resume）
ID = F Y_ <> CC S_ 06 ID 動 =中 F Y_ CC S起 に CC 運 S_ 転 06 者がブレーキを踏 む と 、 CC Sを 一 時 CC S起 休止 す る動 中 に 運 転 者がブレーキを踏 む と 、 CC Sを 一 時 休止する
<> <> <> <> <> <>
加速 度 の 測定 頻 度
運転 者= は RY 直 _C 感 CS 的 _2 1 ID に操作できる
<> <>
目 標 車 速の 加 速 （Accel
ID 動 =中 F Y_ CC S起 に CC 運 S_ 転 05 者 が 「 Ac ce l」 ボ タンを押すと、設 CC S起 定値 の 速動 度中 がに 上運 が転 る 者 が 「 Ac ce l」 ボ タンを押すと、設 定値の速度が上が る
<>
<> ID = R Y_ CC S_ 33
操 作性
CC Sは 速 CC 度 S_ が 24 ID 現 =在 R Y_ 50 km /h 以 上 か つ 10 0k m/ h以 下 の 場 CC Sは 合の み 起現 動在 す速 る度 が 50 km /h 以 上 か つ 10 0k m/ h以 下 の 場 合のみ起動する
<>
CCS一時 休 止<> （Break） <>
ID = F Y_ <> CC S_ 05
D動 =中 FY _C CS _0 4 C CSI 起 に 運 転 者 が 「 D ec el 」 ボ タ ン を押すと、設定値の C CS 速度 が起 下動 が中 るに 運 転 者 が 「 D ec el 」 ボ タ ン を押すと、設定値の 速度が下がる
<> <> <> 加速 度 の 測定 頻 度
<>
<> 操 作性
<> I D = RY _C CS _2 1
CCS起 動条 件
目標 車 速の 加 速 （Accel <>
目 標 車速 の 減速 （ Decel）
目 標車 速 の 設定 （ Set）
CC S起 にC 運 転 者 ID 動 =中 F Y_ CS _0 3 が 「 Se t」 ボ タ ン を 押すと、現在の速 CC S起 度を 設 定動 値中 とに し運 て転 者 が 「 Se t」 ボ タ ン を 保持 す る 押すと、現在の速 度を設定値として 保持する
<>
<>
I D = FY _C <> CS _0 4
ID = F Y_ <> C CS _0 3
CCS停止 （ Cruise）
ID 動 =中 FY _C CS _0 2 CC S起 に 運 転 者 が 「 Cr ui s e」 ボ タ ン を 押 す と 、 C CS を 停 CC S起 動 中 に 運 転 者 止す る が 「 Cr ui s e」 ボ タ ン を 押 す と 、 C CS を 停 止する
<>
<> ID = R Y_ CC S_ 24
<>
<> <>
<>
目 標 車速 の 減速 （ Decel） 目 標車 速 の 設定 （ Set） <> <> <>
CCS停止 （ <> Cruise）
ID = F Y _C <> CS _0 2
CCS起動 （ Cruise）
<>
<>
<>
CCS起動 （ Cruise）
ID = F Y_ <> CC S_ 01 ID 止 =中 F Y_ CC S停 に CC 運 S_ 転 01 者 が 「 Cr ui se 」 ボ タ ン を 押 す と 、 CC Sが CC S停 起動 す る止 中 に 運 転 者 が 「 Cr ui se 」 ボ タ ン を 押 す と 、 CC Sが 起動する
CCS再開 （ Resume）
ID 時 =休 F Y_ CC S一 止 CC 中 S_ 07 に運転者が「 Re su me 」 ボ タ ン CC S一 を押 す と時 、休 一止 時中 に 運 転 者 が 「 休止 前 の 設 定 で Re su CC Sを 再 me 開」 すボ るタ ン を押すと、一時 休止前の設定で CC Sを 再 開 す る
<>
車両 の 限 界加 速 性 能 <>
車両 の 限 界加 速 性 能
0. 5g 未 満 の 加 速度で加減速 す 0. 5g 未 満 の 加 速度で加減速 す
Requirement Requirement Diagram Diagram
Architecture Design Sub-Goal
Sub-Goal
bdd [パ ッケ ージ ] AnalysisPkg [BDD_car]
<< bl oc k> >
車両 Values
bdd [パ ッケ ージ ] AnalysisPkg [BDD_car]
車重 投射面積
<< bl oc k> >
車両 Values
Cd値 車重 空気抵抗 投射面積 トルク Cd値 空 抵 O気 pera tio抗 ns トルク 1
< >
ブレーキ
Ope 1 rations
1
1
< >
1
Values
加速 度 セ ン サ ー
OperatioValue ns s
Values Operations
Values Operations
<< bl oc k> >
1 << bl oc k >>
スロットル
アク チ ュ エ ー タ 1 Values
<< bl oc k >>
スロットル
アク チ ュ エ ー タ
O 1perations
Operations
Operations
1 1
< >
PI制 御 1 1
Values
< >
1
PI制 御 1
Va slues 1Operation 1 Operations
1
< >
1
車両 力 学 制 御 Values
< > 1 車両 力 学 制 御 1
1 1
Values Ope ration
1 1
Ope ration
Value s
<< bl oc k> >
ユ ー ザ ー I/F
Value tio s Opera 1Opera 1 tio
Operations 1
1
ユ ー ザ ー I/F 1
Operation s es Valu
1 1
1 1
5
<< bl oc k> >
電 子 制御 ス ロ ッ ト ル
< >
< >
車 速 セ ン サー
1 << bl oc k> >
加速 度 セ ン サ ー 1 Values
車 速 セ ン サー
Values
CCS コン ト ロ ー ラ OperatioVa nslues
電 子 制御 ス ロ ッ ト ル 1 Values
< >
< >
CCS コン ト ロ ー ラ
Operations
1
1 1
1
< >
1 Values
Operation slues Va
1
Operations
1
< >
ブレーキ
Evidence
System Verification
Context Context
Evidence
Model Simulation
1
Parametric Parametric Diagram Diagram
Block Software Design / Equivalence Checking Block Definition Definition Diagram Diagram Implementation and Verification Spec (=D-Case) 1
1
Requirements Validation at Early Development Phase •Front Loading of Requirements Validation using Model Simulation •Front Loading of Clarification about Development Activity Requirements Identification / Product Planning Goal
Context
Requirements Definition + Requirements Verification
• •
Safety Reliability
Architecture Design
• Implementation • Verification spec Sub-Goal
6
Evidence
System Verification • Functional Verification
Context
Context Evidence
• Safety • Reliability
Model Simulation
Strategy
Sub-Goal
Requirements Validation
Development Activity Software Design / Equivalence Checking Implementation and Verification Spec (=D-Case)
Continuous Traceability of Requirements and Functions •Clarification of Requirements in the Life Cycle •Effect Analysis of Changes and Validation of Implementation Requirement
Design
Requirement
Implementation
Test Link
D-Case
Design
par bdd
Test Plan Test case Test Result
…
ibd
req Development Activity 7
Operation
System Configuration of D-Case – SysML Collaboration •OSLC Add-on for D-Case Editor •D-Case Data Translation for SW Development Environment OSLC (Open Services for Lifecycle Collaboration)
OSLC I/F OSLC OSLC Add-on Add-on
D-Case Editor
Import
Export
D-Case D-Case Date Date Translation Translation
SysML SysML ＳＷ ＳＷ Development Development Environment Environment 8
Requirements Management Quality Management Task & Configuration Management SysML Model Management
Collaboration
Demonstration D-Case – Modeling Environment Cruise Control System Development
9
Demonstration : Cruise Control System Development Application of D-Case to Cruise Control System Development 1. Dependability Consensus Building Tool D-Case
2. D-Case Environment D-Case Editor
3. Modeling Language SysML
4. Modeling & Simulation Environment IBM Rational Rhapsody
10
Development Process SysML model and D-Case are made and simulated in V-model.
D-Case
MBD Requirements Identification / Product Planning
Requirements Definition
Requirements Validation
Use Case Diagram Requirement Diagram
Architecture Design Block Definition Diagram Parametric Diagram Statemachine Diagram
System Verification Simulation Scenario Test Data Simulation Results
Equivalence Checking Software Design Implementation and Verification Spec (=D-Case) 11
Demonstration Flow
Legend Current Dev. Process D-Case Task
Requirements Extraction
Analysis & Consent of Dependability Requirements & Validity Using D-Case
Requirement Process Design Using SysML & Specify Requirements
Design of Architecture & Behavior Using SysML Model
Design Process
Registration of Test case Test Process
12
Verification of D-Case
Association of SysML Models & D-Case
Association of Test case & D-Case
Test & Requirements Validation
Registration of Test Result
Association of Test Result & D-Case
Demonstration Flow
Legend Current Dev. Process D-Case Task
Requirements Extraction Requirement Process
#1
•• Extraction Extraction of of User User Requirements Requirements Using Using Requirements Requirements Analysis & Consent Management Management Tool Tool of Dependability Requirements •• Analysis Analysis & & Consent Consent of of Dependability Dependability Requirements Requirements & Validity Using D-Case Using D-Case Editor Using D-Case Editor
Design Using SysML & Specify Requirements
Design Process
#3
Verification of D-Case •• Development Development of of D-Case D-Case by by Architecture Architecture Specification Specification Using Using SysML SysML Environment Environment
Design of Architecture & Behavior Using SysML Model
Registration of Test case Test Process •• Test Test on on SysML SysML Environment Environment •• Registration Registration of of Test Test Result Result on on Test Management Tool Test Management Tool •• Development Development of of D-Case D-Case by by Adding Adding 13 Test Result Using D-Case Editor Test Result Using D-Case Editor
Association of Test case & D-Case
#4
Test & Requirements Validation
Association of SysML Models & D-Case
#2
•• Clarification Clarification of of Test Test Specification Specification Using Using Test Test Management Management Tool Tool •• Development Development of of D-Case D-Case by by Adding Adding Test Test Specification Specification
Registration of Test Result
Association of Test Result & D-Case
Demonstration Flow
Legend Current Dev. Process D-Case Task
Requirements Extraction Requirement Process
#1
User Requirements Using Requirements •• Extraction Extraction User Requirements Extraction of ofof User Requirements UsingUsing Requirements Extraction of User Requirements Using Analysis & Consent Management Tool Management Tool Requirements Management Tool of Dependability RequirementsRequirements Management Tool •• Analysis of Requirements Analysis & &&Consent of Dependability Dependability Requirements Consent of & Validity Using D-Case•• Analysis Analysis &Consent Consent of Dependability Dependability Using D-Case Editor Using D-Case Editor
Requirements Requirements Using Using D-Case D-Case Editor Editor
Design Using SysML & Specify Requirements
Verification of D-Case
1. 1. Extraction Extraction of of User User Requirements Requirements
2. 2. Framework Framework Determination Determination of of D-Case D-Case Design Process
#3
Design of Architecture 3. 3. & Behavior Using SysML Model
4. 4. Association Association of of Requirements Requirements to to Satisfy Satisfy Association of the the Goal Goal with with Context Context of of D-Case D-Case Test case & D-Case
Registration of Test case
#2
Test Process
#4 14
Import Requirements from Import User User Requirements from Association of SysML Models & D-Case Requirements Management Tool Requirements Management Tool to to DDCase Case Editor Editor Using Using OSLC OSLC Collaboration Collaboration
Test & Requirements Validation
Registration of Test Result
Association of Test Result & D-Case
Development Process SysML model and D-Case are made and simulated in V-model.
D-Case
MBD Requirements Identification / Product Planning
Requirements Definition
Requirements Validation
Use Case Diagram Requirement Diagram
Architecture Design Block Definition Diagram Parametric Diagram Statemachine Diagram
System Verification Simulation Scenario Test Data Simulation Results
Equivalence Checking Software Design Implementation and Verification Spec (=D-Case) 15
Preparation of D-Case Rough structure of D-Case is considered.
16
Preparation of D-Case Rough structure of D-Case is considered. Top Top goal goal :: ACC ACC is is safe. safe.
ACC ACC is is safe safe because because itit doesn't doesn't cause cause the the past past accidents. accidents.
Suppress Suppress damage damage of of the threat which the threat which has has not not occurred occurred
17
Association of Requirements with D-Case Goal (1/3)
18
Association of Requirements with D-Case Goal (2/3)
19
Association of Requirements with D-Case Goal (3/3)
20
Demonstration Flow
Legend Current Dev. Process D-Case Task
Requirements Extraction Requirement Process
Analysis & Consent of Dependability Requirements & Validity Using D-Case
#1 1. 1. Import Import Test Test Specification Specification from from Test Tool to Test Management Management Tool to DDVerification of D-Case Case Case Editor Editor Using Using OSLC OSLC Collaboration Collaboration
Design Using SysML & Specify Requirements
Design Process
#3
Registration of Test case
Association of Test case & D-Case
Test Process
#4 21
2. 2. Association Association of of Test Test case case to to Satisfy Requirement Association Satisfy of Requirement with with SysML Models & D-Case Context of Context of D-Case D-Case
Design of Architecture & Behavior Using SysML Model
Test & Requirements Validation
#2
•• Clarification Clarification of of Test Test Specification Specification Using Using Test Test Management Management Tool Tool •• Development Development of of D-Case D-Case by by Adding Adding Test Test Specification Specification
Registration of Test Result
Association of Test Result & D-Case
Describing Test Cases associated with D-Case (1/3)
Create Create New New Test Test Case Case
22
Describing Test Cases associated with D-Case (2/3)
Fill Fill in in title title and and details details of the test case of the test case
23
Describing Test Cases associated with D-Case (3/3)
Fill Fill in in title title and and details details of the test case of the test case
24
Association of Test Specifications with D-Case (1/3) The The test test case case is is created created
Drag Drag the the test test case case to Goal to Goal
25
Association of Test Specifications with D-Case (2/3)
Select Select “Create “Create Association Association through through Context” Context”
26
Association of Test Specifications with D-Case (3/3)
Context Context describing describing the the test test case case is is added added
27
Demonstration Flow
Legend Current Dev. Process D-Case Task
Requirements Extraction Requirement Process
Analysis & Consent of Dependability Requirements & Validity Using D-Case
#1 Design Using SysML & Specify Requirements
Design Process
#3
Verification of D-Case •• Development Development of of D-Case D-Case by by Architecture Architecture Specification Specification Using Using SysML SysML Environment Environment
Design of Architecture & Behavior Using SysML Model
Association of SysML Models & D-Case
1. 1. Open Open D-Case D-Case on on SysML SysML Environment Environment Using Using D-Case D-Case Data Data Collaboration Collaboration Registration of Test case Test Process
Association of Test case & D-Case Association of Design
#2 Information 2. 2. Association of Design Information to to Satisfy Satisfy the the Goal Goal with with Context Context of of D-Case D-Case #4 3. 3.
28
Test & Registration of Association of Requirements Testto Export Updated D-Case Export Updated D-Case D-Case toResult D-Case Editor EditorTest Result & D-Case Validation
Development Process SysML model and D-Case are made and simulated in V-model.
D-Case
MBD Requirements Identification / Product Planning
Requirements Definition
Requirements Validation
Use Case Diagram Requirement Diagram
Architecture Design Block Definition Diagram Parametric Diagram Statemachine Diagram
System Verification Simulation Scenario Test Data Simulation Results
Equivalence Checking Software Design Implementation and Verification Spec (=D-Case) 29
Requirements Definition – Use Case Diagram Relation of User and Operation of the System is defined in Use Case Diagram.
User User
30
Operation Operation
Requirements Definition – Requirement Diagram Functional requirements and Non-functional requirements are defined in Requirement Diagram.
Functional Functional requirements requirements Non-functional Non-functional requirements requirements
31
Requirements Definition – Requirement Diagram Functional requirements and Non-functional requirements are defined.
Functional Functional requirements requirements Non-functional Non-functional requirements requirements
32
D-Case Update Association of requirements in Requirement Diagram with D-Case. Req. Diagram
D-Case
1. Add and associate SysML requirements with D-Case Context. Requirements
Context 33
D-Case Update Association of requirements in Requirement Diagram with D-Case.
34
D-Case Update Association of requirements in Requirement Diagram with D-Case.
Import Import D-Case D-Case in in modeling modeling environment environment 35
D-Case Update Association of requirements in Requirement Diagram with D-Case.
Import Import D-Case D-Case in in modeling modeling environment environment 36
D-Case Update Association of requirements in Requirement Diagram with D-Case.
Import Import D-Case D-Case in in modeling modeling environment environment 37
D-Case Update Association of requirements in Requirement Diagram with D-Case.
Associate Associate requirement requirement with with D-Case D-Case
38
D-Case Update Association of requirements in Requirement Diagram with D-Case.
Associate Associate requirement requirement with with D-Case D-Case
39
D-Case Update Association of requirements in Requirement Diagram with D-Case.
Associate Associate requirement requirement with with D-Case D-Case
40
D-Case Update - Feedback to Requirements Definition Lack of requirements will be found through discussion about D-Case Goal or Strategy.
Lack Lack of of requirements requirements is is found found
41
D-Case Update - Feedback to Requirements Definition Lack of requirements will be found through discussion about D-Case Goal or Strategy.
Select Select Context Context
42
D-Case Update - Feedback to Requirements Definition Lack of requirements will be found through discussion about D-Case Goal or Strategy.
Add Add aa requirement requirement
43
D-Case Update - Feedback to Requirements Definition Lack of requirements will be found through discussion about D-Case Goal or Strategy.
Add Add aa requirement requirement
44
D-Case Update - Feedback to Requirements Definition Lack of requirements will be found through discussion about D-Case Goal or Strategy.
Add Add aa requirement requirement
45
D-Case Update - Feedback to Requirements Definition Update Requirement Diagram by adding suitable requirements.
D-Case
Lack of requirements was found through discussion about Goal or Strategy Req. Diagram
Add a requirement to Requirement Diagram
46
D-Case Update - Feedback to Requirements Definition Update Requirement Diagram by adding suitable requirements.
Open Open Requirement Requirement Diagram Diagram
47
D-Case Update - Feedback to Requirements Definition Update Requirement Diagram by adding suitable requirements.
Select Select Requirement Requirement
48
D-Case Update - Feedback to Requirements Definition Update Requirement Diagram by adding suitable requirements.
Add Add aa requirement requirement
49
D-Case Update - Feedback to Requirements Definition Update Requirement Diagram by adding suitable requirements.
Add Add aa requirement requirement
50
Development Process SysML model and D-Case are made and simulated in V-model.
D-Case
MBD Requirements Identification / Product Planning
Requirements Definition
Requirements Validation
Use Case Diagram Requirement Diagram
Architecture Design Block Definition Diagram Parametric Diagram Statemachine Diagram
System Verification Simulation Scenario Test Data Simulation Results
Equivalence Checking Software Design Implementation and Verification Spec (=D-Case) 51
System Design – Block Definition Diagram System architecture is defined in Block Definition Diagram.
System System composition composition with with Control Control flow flow
52
System Design – Parametric Diagram Restriction, Condition, Value involved, and Mathematical expression are defined in Parametric Diagram.
Restriction, Restriction, Condition, Condition, Value, Value, Mathematical Mathematical expression, expression, Design intent Design intent
53
System Design – Parametric Diagram Restriction, Condition, Value involved, and Mathematical expression are defined in Parametric Diagram.
Restriction, Restriction, Condition, Condition, Value, Value, Mathematical Mathematical expression, expression, Design intent Design intent
54
System Design – State Machine Diagram Dynamical behavior is defined in State Machine Diagram, and generate Source code.
Dynamical Dynamical behavior behavior
55
D-Case Update Add D-Case Context based on Design Specification described in Parametric Diagram. Parametric Diagram 1
<>
vd actualSpeed drag thrust
1
D-Case
<>
s actualSpeed
<> <> <> <>
a= (thrust + drag) / mass
<>
加速の加速度制限： a < 0.35G
Context Context Design Design Spec. Spec.
*Association is performed like the above-mentioned. 56
D-Case Update Export the D-Case described in the modeling environment to D-Case Editor.
Export Export D-Case D-Case 57
D-Case Update Export the D-Case described in the modeling environment to D-Case Editor.
Export Export D-Case D-Case 58
D-Case Update Export the D-Case described in the modeling environment to D-Case Editor.
Export Export D-Case D-Case 59
Demonstration Flow
Legend Current Dev. Process D-Case Task
Requirements Extraction Requirement Process
Analysis & Consent of Dependability Requirements & Validity Using D-Case
#1
1. 1. Execution Execution of of Model Model Simulation Simulation on on SysML SysML Environment Environment Verification of D-Case
Design Using SysML & Specify Requirements
2. 2. Registration Registration of of Simulation Simulation Result Result in in Test Test Management Management Tool Tool Design Process
#3
Design of Architecture 3. Result Association 3. Import Import Simulation Simulation Resultoffrom from Test Test & Behavior SysML Models & D-CaseEditor Management Tool to Management Tool to D-case D-case Editor Using SysML Model
Using Using OSLC OSLC Collaboration Collaboration 4. 4. Association Association of of Simulation Simulation Result Result to to Association of Satisfy Satisfy the the Requirement Requirement with with Evidence Evidence Test case & D-Case #2 of of D-Case D-Case
Registration of Test case Test Process •• Test Test on on SysML SysML Environment Environment •• Registration Registration of of Test Test Result Result on on Test Management Tool Test Management Tool •• Development Development of of D-Case D-Case by by Adding Adding 60 Test Result Using D-Case Editor Test Result Using D-Case Editor
#4
Test & Requirements Validation
Registration of Test Result
Association of Test Result & D-Case
Development Process SysML model and D-Case are made and simulated in V-model.
D-Case
MBD Requirements Identification / Product Planning
Requirements Definition
Requirements Validation
Use Case Diagram Requirement Diagram
Architecture Design Block Definition Diagram Parametric Diagram Statemachine Diagram
System Verification Simulation Scenario Test Data Simulation Results
Equivalence Checking Software Design Implementation and Verification Spec (=D-Case) 61
System Verification – Test Data Verification of requirement for Acceleration against Body type : Wagon and Sedan Test Data
62
Body type
Wagon
Sedan
Mass (kg)
2,500
1,700
Air Resistance Cd value
0.50
0.44
Projected Area (m2)
2.0
1.8
Requirement for Acceleration
< 0.35G
< 0.35G
System Verification – Simulation Scenario Scenario is defined for Model Simulation.
Verification Verification of of requirement requirement for for Acceleration Acceleration “accel “accel << 0.35G” 0.35G” with with this this Driving Driving Pattern Pattern
Start Start an an Engine Engine Power Power ON ON ACC ACC
63
Target Target speed speed of of ACC ACC is is changed changed at at 100km/h 100km/h ifif speed speed exceeds exceeds 50km/h. 50km/h.
System Verification – Model Simulation Check verification of D-Case Goal through Model Simulation.
Start Start Simulation Simulation
64
System Verification – Model Simulation Check verification of D-Case Goal through Model Simulation. D-Case
Goal Goal Max Max Accel Accel G G << 0.35G 0.35G
Speed (km/h)
Simulation Results
Wagon 120
0.28G MAX
100 80
Max Accel G : 0.28G OK!
60 40 20 0
Speed (km/h)
0
5000
10000
15000
Time (ms)
20000
Sedan 120
0.42G MAX
100 80
Max Accel G : 0.42G NG!
60 40 20 0 0
65
2000
4000
6000
8000
10000
12000
14000
16000
Time (ms)
18000
Association of Test Results with D-Case Goal (1/3)
Drag Drag the the Test Test Case Case to to aa Goal Goal
66
Association of Test Results with D-Case Goal (2/3)
Select Select “Create “Create Association Association through through Evidence” Evidence”
67
Association of Test Results with D-Case Goal (3/3)
Evidence Evidence is is added added
68
Conclusion
Advantage of D-Case - SysML Collaboration •Requirements Validation at Early Development Phase •Continuous Traceability of Requirements and Functions
Development of Collaboration Functions •OSLC Collaboration Add-on of D-Case Editor •D-Case Data Collaboration of SW Development Environment
69
