Harmony/SE: A SysML Based Systems Engineering Process

Transcription

1 Hrmony/SE: A SysML Bsed Systems Engineering Process Hns-Peter Hoffmnn, Ph.D Chief Systems Methodologist hoffmpe@us.ibm.com

2 Model-Bsed Systems Engineering Integrted System / Embedded Softwre Development Process Hrmony Fundmentls of Model-Bsed Systems Engineering ( Hrmony/SE ) - Essentil SysML Artifcts - Service Request-Driven Modeling Approch Tsk Flow nd Work Products in Hrmony/SE Systems Engineering Hndoff to Hrdwre nd Softwre Development 2

3 Integrted System / Softwre Development Process Model-Driven Development of Embedded Systems System Chnges Stkeholder Requirements Systems Engineering Hrmony/SE Requirements Models, Requirements Requirements & System Use Cses Anlysis Test Scenrios Executble System Functionl Use Cse Models Anlysis Architecturl Anlysis Model(s), Design Synthesis System Architecture Model System Architecture Bseline SW Anlysis & Design Model / Requirements Repository * System Acceptnce Embedded SW Engineering Hrmony/ESW (Sub-)System Integrtion & Test Module Integrtion & Test Softwre Implementtion Model SW Implementtion & Unit Test * Configurtion Controlled Knowledge of the System Under Development: Requirements Documenttion Requirements Trcebility Design Documenttion Test Definitions 3

4 Model-Bsed Systems Engineering Integrted System / Embedded Softwre Development Process Hrmony Fundmentls of Model-Bsed Systems Engineering ( Hrmony/SE ) - Essentil SysML Artifcts - Service Request-Driven Modeling Approch Tsk Flow nd Work Products in Hrmony/SE Systems Engineering Hndoff to Hrdwre nd Softwre Development 4

5 Essentil SysML Artifcts for Model-Bsed Systems Engineering SysML Digrm Structurl Digrms Behviorl Digrms Requirements Digrm Block Definition Digrm Use Cse Digrm Internl Block Digrm Sequence Digrm Prmetric Digrm Activity Digrm Sttechrt Digrm UML4SysML UML 2. SysML.0 5

6 Requirements Digrm Use Cse Digrm Activity Digrm «Requirement» SRS_Req_. «decompose» «Requirement» SRS_Req_.. «derive» «trce» Uc2 «testcse» Uc2Scenrio5 «verify» «Requirement» SRS_Req_...x «stisfy» «block» SS_B A SuD Uc Uc2 A2 op2 [c2==true] Uc op [c==true] [else] op5 op3 op4 Txonomy of Requirements Reltionship between Model Elements nd Requirements Definition of System Scope Grouping of Requirements into Use Cses Structure Digrms Functionl Flow in Use Cse / Block(s) Sequence Digrm SysML Artifcts in Hrmony/SE «block» SuD A A2 «block» «block» SS_A SS_B itsa reqop() lt reqop4() [C==true] itsuc op() op3() op4() [C2==true] op2() reqopx() op5() Prmetric Digrm Block Definition Digrm: Structurl Elements (Blocks) nd their Reltionship Messge Interctions between Nodes Sttechrt Digrm «Attribute» mss «Attribute» ccelertion «ConstrintProperty,ConstrintBlock» itsnewtonlw:newtonlw force = mss * ccelertion mss:kg force:newtons ccelettion:meterspersec^2 «Attribute» force «Actor» itsa psud «Actor» itsa2 psud pa pa2 «block» itssud «block» itsss_a pa pss_b «block» itsss_b pa2 pss_a S reqs2tos reqstos2 S2 S2 reqop/op [c==true]/op3 S22 [c2==true]/op2 [else] reqopx S23 op5 reqop4/op4 Prmetric Reltionship between System Properties Internl Block Digrm: Reliztion of System Structure Stte-bsed Behvior of Block 6

7 Model-Bsed Systems Engineering (Hrmony/SE ) Artifct Reltionships in Requirements Anlysis / System Functionl Anlysis Requirements Digrm * Use Cse Digrm Structure Digrm Block Definition Digrm Internl Block Digrm..* Use Cse 5..* Sequence Digrm 2..* Block Activity Digrm Stkeholder Requirements Systems Engineering Hrmony/SE Sttechrt Digrm Requirements Anlysis Requirements & Test Scenrios System Functionl Anlysis Design Synthesis Requirements Anlysis System Functionl Anlysis 7

8 Model-Bsed Systems Engineering Integrted System / Embedded Softwre Development Process Hrmony Fundmentls of Model-Bsed Systems Engineering ( Hrmony/SE ) - Essentil SysML Artifcts - Service Request-Driven Modeling Approch Tsk Flow nd Work Products in Hrmony/SE Systems Engineering Hndoff to Hrdwre nd Softwre Development 8

9 Service Request-Driven Modeling Approch Step : Define Communiction Nodes IBD_SuD Step 3: Allocte Service Requests nd Opertions IBD_SuD itsb:b itsb2:b2 itsb:b itsb2:b2 Step 2: Describe Inter-Nodl Communiction in Sequence Digrm reqopertion2 reqopertion4 opertion2 opertion4 pb reqsetmode reqopertion reqopertion3 opertion opertion3 itsb itsb2 reqopertion() opertion() reqsetmode(modex) ModeX reqopertion2() opertion2() Step 4: Define Ports nd Interfces IBD_SuD itsb:b pb2 reqopertion2 reqopertion4 opertion2 opertion4 ib_to_b2 ib2_to_b ib_to_b2 ib2_to_b pb itsb2:b2 reqsetmode reqopertion reqopertion3 opertion opertion3 reqopertion3() opertion4() reqopertion4() opertion3() «Interfce» ib_to_b2 reqopertion2 reqopertion4 «Interfce» ib2_to_b reqsetmode reqopertion reqopertion3 Communiction described through Opertionl Contrcts (OpCon), i.e. - synchronous Service Requests vi SysML Service Ports followed by - provided services t the receiving prt (stte/mode chnges or opertions) 9

10 Model-Bsed Systems Engineering Integrted System / Embedded Softwre Development Process Hrmony Fundmentls of Model-Bsed Systems Engineering ( Hrmony/SE ) - Essentil SysML Artifcts - Service Request-Driven Modeling Approch Tsk Flow nd Work Products in Hrmony/SE Systems Engineering Hndoff to Hrdwre nd Softwre Development 0

11 Key Objectives of the Model-Bsed Systems Engineering Process Hrmony/SE Stkeholder Requirements Systems Engineering Hrmony/SE Requirements Anlysis Requirements & Test Scenrios Identify / derive required system functionlity System Functionl Anlysis Design Synthesis Identify ssocited system modes nd sttes Allocte system functionlity / modes to physicl rchitecture

12 Model-Bsed Systems Engineering (Hrmony/SE ) Requirements Anlysis Stkeholder Requirements Model / Requirements Repository Stkeholder Requirements System Requirements System Use Cses Requirements Anlysis System Use Cses In the Requirements Anlysis phse, the focus is on the nlysis of the process inputs. Stkeholder requirements re trnslted into system requirements tht define - wht the system must do (functionl requirements) nd - how well it must perform (qulity of service requirements). Once the requirements re sufficiently understood they re grouped into Use Cses. SRS (Drft) Anlyze/Refine Stkeholder Reqs Stkeholder Requirements Specifiction Generte Link System Reqs Stkeholder Reqs to System Reqs System Requirements Specifiction (Drft) Define System Level Use Cse Link Functionl / Performnce Requirements to Use Cse [Next Use Cse] [else] Links providing trcebility to originl requirements 2

13 Model-Bsed Systems Engineering (Hrmony/SE ) System Functionl Anlysis Stkeholder Requirements Stkeholder Requirements Define Use Cse Model Context Model / Requirements Repository System Requirements Use Cse Model System Requirements Executble Use Cse Model(s) Use Cse Scenrios (Blck-Box) Requirements Anlysis System Use Cses System Functionl Anlysis (Use Cse-Bsed) System Opertions In the System Functionl Anlysis phse, the focus is on the trnsltion of the functionl requirements into coherent description of system functions (Opertions). Ech use cse is trnslted into model nd the underlying requirements verified nd vlidted through model execution. SRS (Drft) SRS (Bseline) Document New / Derived Reqs Define UC Functionl Flow Derive UC Scenrios from UC Functionl Flow Define Ports nd Interfces Derive UC Stte-Bsed Behvior from UC BB-AD nd BB-SDs Verify / Vlidte UC Model trough Model Execution [else] [Riny Dy Anlysis] Extend UC Model w.r.t. Error/Fil Behvior Links providing trcebility to originl requirements Link UC Block Properties to Reqs Updte Drft System ReqSpec 3

14 System Functionl Anlysis Derivtion of Use Cse Scenrios from UC Blck-Box Activity Digrm SD_Uc_HomingAndMnulMode_Sc AD_Uc_HomingAndMnulMode 4

15 Use Cse Model Verifiction nd Vlidtion Through Model Execution Exmple: Security System Use Cse ControlEntry (ref. Rhpsody Deskbook Rel. 3.0) Security System Cmer Uc_ ControlEntry Door User Admin itsuser Uc_ControlEntry itsaccesspoint itscmer reqredsecuritycrd() redsecuritycrd() reqtkesnpshot() vlidtesecuritycrd(crdsttus = Vlid) displycrdsttus(crdsttus = Vlid) reqscnbiometricdt() scnbiometricdt() uthentictebiometricdt(authentictionsttus = Authenticted) Uc_Cmer itsuc_controlentry Uc_Door displyauthentictionsttus(authentictionsttus = Authenticted) puc_controlentry pcmer pdoor puc_controlentry requnlockaccesspoint() Uc_User Uc_Admin tm(000) puc_controlentry puser padmin puc_controlentry evaccesspointunlocked() 5

16 Model-Bsed Systems Engineering (Hrmony/SE ) Design Synthesis Model / Requirements Repository System Requirements Executble Use Cse Model(s) Use Cse Scenrios (Blck-Box) System Requirements Architecturl Anlysis Model(s) UC Activity Digrm(s) (Blck-Box) Use Cse Scenrios (Blck-Box) System Architecture Model (Bseline) Scenrios (White-Box) Links providing trcebility to originl requirements System Functionl Anlysis (Use Cse-Bsed) System Opertions Design Synthesis Repeted for ech Level of System Architecture Decomposition Architecturl Anlysis (Trde Study) Architecturl Concept Architecturl Design Allocted System Opertions Detiled Architecturl Design HW/SW Development SRS (Bseline) Architecturl Anlysis Architecturl Design Detiled Architecturl Design Elborte Architecturl Concept (Trde Study) Allocte Non-Functionl Req s to Prts [Next Use Cse] [Next Level of Decomposition] Decompose UC Blck-Box Sequence Digrms [Next Use Cse] Define Prts of Decomposition Hierrchy Allocte System-Level Opertions to Prts [else] [else] [else] Define Ports nd Interfces The focus of the Design Synthesis phse is on the development of system rchitecture cpble of performing the required functions within the limits of the prescribed performnce constrints. Define Lef Blocks Stte-Bsed Behvior Verify System Architecture Model 6

17 Architecturl Design Alloction of System-Level Opertions to Subsystems (Decomposition Level ) Subsystem Subsystem 2 Subsystem 3 Use Cse Blck-Box Activity Digrm Use Cse White-Box Activity Digrm 7

18 Detiled Architecturl Design Decomposition of UC Blck-Box Scenrios nd Definition of Ports / Interfces Use Cse Scenrio SuD Internl Block Digrm itsa itssud itssud Blck Box itsa reqopertion4 psud pa reqopertion opertion opertion2 opertion3 itssud itsa itsss itsss2 itsss White Box itsa reqopertion4 psud pa reqopertion2 opertion2 itsss2 reqopertion reqopertion3 opertion opertion3 pa pss2 pss 8

19 Architecture Model Verifiction nd Vlidtion Through Model Execution Exmple: Security System (ref. Rhpsody Deskbook Rel. 3.0) itsuser SecuritySystem. CrdReder_Entry SecuritySystem. CrdReder_Exit SecuritySystem. itsfingerprintscnner SecuritySystem. itssecsyscontroller itsaccesspoint itscmer itsadmin reqredsecuritycrd() redsecuritycrd() reqvlidtesecuritycrd() reqtkesnpshot() vlidtesecuritycrd(crdsttus = Vlid) displycrdsttus(crdsttus = Vlid) reqdisplycrdsttus(crdsttus = Vlid) reqenblebiometricscn() reqscnbiometricdt() scnbiometricdt() uthentictebiometricdt(authentictionsttus = Authenticted) displyauthentictionsttus(authentictionsttus = Authenticted) reqsetauthentictionsttus(authentictionsttus = Authenticted) reqdisblebiometricscn() requnlockaccesspoint() IBD_SecuritySystem itssecuritysystem evaccesspointunlocked() tm(000) itsuser pcrdreder_entry pcrdreder_exit puser_entry puser_exit CrdReder_Entry puser psecsyscontroller CrdR eder_exit puser psecsyscontroller itssecsyscontroller pcrdreder_entry paccesspoint pcrdreder_exit pcmer paccesspoint pcmer itsaccesspoint psecsyscontroller itscmer psecsyscontroller tm(5000) reqlockaccesspoint() evaccesspointlocked() tm(000) pfingerprintscnner itsfingerprintscnner puser_fpscn puser psecsyscontroller pfingerprintscnner padmin padmin itsadmin psecsyscontroller 9

20 Model-Bsed Systems Engineering (Hrmony/SE ) Stkeholder Requirements Stkeholder Requirements Model / Requirements Repository System Requirements System Use Cses System Requirements Executble Use Cse Model(s) Use Cse Scenrios (Blck-Box) System Requirements Architecturl Anlysis Model(s) UC Activity Digrm(s) (Blck-Box) Requirements Anlysis System Use Cses System Functionl Anlysis (Use Cse-Bsed) System Opertions Design Synthesis Repeted for ech Level of System Architecture Decomposition Architecturl Anlysis (Trde Study) Architecturl Concept Architecturl Design SRS (Drft) SRS (Bseline) Use Cse Scenrios (Blck-Box) System Architecture Model (Bseline) Scenrios (White-Box) Links providing trcebility to originl requirements Allocted System Opertions Detiled Architecturl Design HW/SW Development 20

21 Model-Bsed Systems Engineering Integrted System / Embedded Softwre Development Process Hrmony Fundmentls of Model-Bsed Systems Engineering ( Hrmony/SE ) - Essentil SysML Artifcts - Service Request-Driven Modeling Approch Tsk Flow nd Work Products in Hrmony/SE Systems Engineering Hndoff to Hrdwre nd Softwre Development 2

22 Systems Engineering Hndoff to Hrdwre nd Softwre Development In model-driven development the key rtifct of the hndoff from systems engineering to the subsequent system development is the bselined executble model. This model is the repository from which specifiction documents (e.g. HW/SW Requirements Specifictions, ICDs, ) re generted. Scope nd content of the hnd-off is dependent on the chrcteristics of the project nd the orgniztionl structure systems engineering is embedded. 22

23 Systems Engineering Hndoff to Hrdwre nd Softwre Development If the System under Development (SuD) is ll softwre, systems engineering my stop t the functionl nlysis level. In this cse, the hnd-off will be executble use cse models. From the orgniztionl point of view, if there is seprtion between systems engineering nd subsystems engineering, then systems engineering my stop t the first level of system rchitecture decomposition. In this cse the hnd-off will be composed of relevnt executble subsystem models. If systems engineers hnd-off their specifictions directly to HW/SW development, then the hnd-off will be the respective executble HW nd/or SW component models. 23

24 Systems Engineering Hndoff to Hrdwre nd Softwre Development The hnd-off pckges typiclly re composed of: Bselined executble configurtion item (CI) model(s) Definition of CI-llocted opertions including links to the ssocited system functionl nd performnce requirements Definition of CI ports nd logicl interfces Definition of CI behvior, cptured in sttechrt digrm Test scenrios, derived from system-level use cse scenrios CI-llocted non-functionl requirements 24

25 Model-Bsed Systems Engineering System Chnges Stkeholder Requirements Systems Engineering Hrmony/SE Integrted Systems / Embedded Softwre Development Process Hrmony Model / Requirements Repository Stkeholder Requirements Stkeholder Requirements System Requirements Use Cse Model System Requirements Executble Use Cse Model(s) Use Cse Scenrios (Blck-Box) System Requirements Architecturl Anlysis Model(s) UC Activity Digrm(s) (Blck-Box) Requirements Anlysis System Use Cses System Functionl Anlysis (Use Cse-Bsed) System Opertions Design Synthesis Repeted for ech Level of System Architecture Decomposition Architecturl Anlysis (Trde Study) Architecturl Concept Architecturl Design SRS (Drft) SRS (Bseline) Requirements Requirements & Anlysis Test Scenrios System Functionl Anlysis Design Synthesis SE / ESW Hnd-off SW Anlysis & Design Model / Requirements Repository SW Implementtion & Unit Test System Acceptnce Embedded SW Engineering Hrmony/ESW (Sub-)System Integrtion & Test Module Integrtion & Test Use Cse Scenrios (Blck-Box) System Architecture Model (Bseline) Scenrios (White-Box) Allocted System Opertions Detiled Architecturl Design Links providing trcebility to originl requirements HW/SW Design Logicl ICDs HW/SW Req Specs incl. Test Scenrios 25