Harmony/ESW An Agile Real-time Development Process. Jeff Vodov

Transcription

1 Hrmony/ESW An Agile Rel-time Development Process Jeff Vodov

2 Objectives Provide high-level overview of Hrmony Chllenges of SE nd SW Development Hrmony Best Prctices Rtionl / Telelogic Process Rodmp Provide n overview of Hrmony/ESW Understnd the core principles, roles, work products, tsks, best prctices nd lifecycle of Hrmony/ESW Deployment of Hrmony/ESW Process Trining Interctive Process Hndbook 2

3 The Importnce of Process & Best Prctices The qulity of product is lrgely determined by the qulity of the process tht is used to develop nd mintin it " bsed on: Shewhrt, Jurn, Deming nd Humphrey 3

4 Combintion of Technology nd Process Results in 10x Business Vlue 10x Business Vlue 4x 1x Technology Only Process Only Technology nd Process Source: London School of Economics McKinsey Survey 4

5 Chllenge of Leverging Best Prctices Different sources in different formts Difficult to customize nd mintin Lrge volumes of informtion Difficult for prctitioners to find relevnt informtion 5

6 Telelogic Hrmony Librry of re-useble Best Prctices - Stndrd met-model (OMG SPEM 2.0) - Stndrd tool (EPF Composer/RMC) Pre-configured processes include: - Hrmony/ITSW IT Softwre - Hrmony/ESW Embedded Softwre - Hrmony/SE Systems Engineering 6

7 Rtionl / Telelogic Process Rodmp 2Q08 3Q08 4Q08 1Q09 4Q09 1Q09 2Q09 2Q09 3Q09 1Q10 4Q09 1Q10 APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR Rtionl RMC 7.5 Prctices nd Mesurements RMC APARs RMC APARs RMC APARs RMC 8.0 Jzz Bsed ( Tenttive ) Telelogic Hrmony ITSW Process Guidnce for Telelogic Tools ESW Content SE Content Chnge Control Prctice Requirements Definition Requirements Mngement Continuous Integrtion Prctices 2Q08 3Q08 4Q09 1Q09 4Q09 1Q09 2Q09 2Q09 3Q09 1Q10 4Q09 1Q10 7

8 The Telelogic Process nd Product Portfolio Telelogic System Architect EA nd Business Process Telelogic Hrmony Telelogic DOORS Telelogic Tu & Rhpsody Anlysis & Design Telelogic Focl Point Product Portfolio Mngement Requirements Telelogic Chnge & Synergy Telelogic Tu, Rhpsody & Eclipse &.Net Integrtions Telelogic Dshbord Mesurement Telelogic Integrtions Telelogic Synergy Relese Mgmt Configurtion & Chnge Mgmt Telelogic Tester, Test Conductor nd Test Genertor Implementtion Production Test 8

9 Hrmony/ESW Introduction 9

10 Wht is Hrmony/ESW? The Hrmony/ESW Process is generlly pplicble to softwre nd systems development, but is optimized for the development of softwre-intensive rel-time nd embedded systems. Hrmony/ESW is directly derived from the Rpid Objectoriented Process for Embedded Systems (ROPES), uthored by Dr. Bruce Powel Douglss. 10

11 Wht is Hrmony/ESW? Hrmony/ESW is: Agile: embodies the use of key concepts nd guiding principles of gile development Efficient: emphsis is on tsks nd work products tht dd significnt to the development High qulity: stresses on continul vlidtion of correctness nd completeness throughout development Requirements-driven: development tsks concentrte on identifying nd meeting stkeholders needs Architecture-centric: strong concepts of key rchitecturl views Sclble: process is defined so tht spects re included only when needed 11

12 Core Principles The core principles of Hrmony/ESW cpture the overll intent nd philosophy behind the Hrmony Process Your Primry Gol is to Develop Softwre or Systems Principle of Continul Feedbck Key Views of Architecture Pln, Trck, Adpt Leding Cuse of Project Filure is... Ignoring Risk Modeling is next to godliness 12

13 Primry Gol: Some key prctices 80% of developer s time should be spent on ctivities supporting the development of high-qulity softwre Even if you re signing off documents fster thn plnned, you re not mking rel progress if the softwre doesn t work Dily ctivities should focus on: The nnocycle of development performs rpid model-compiledebug-unit test workflow every few minutes Source code is generted nd tested every few minutes Continuous integrtion builds the system t lest dily to ensure comptibility of components nd subsystems This is not to sy writing documents nd other tsks re inpproprite, just tht they re not your primry gol 13

14 Continuous Feedbck: Some key prctices It in t right if it don t run Lw of Douglss Optimism is the enemy of relism Lw of Douglss Optimism is disese feedbck is the cure Kent Beck As we develop softwre over dys, weeks, nd months, we need ssurnce tht we re doing the right thing: Constnt debug nd unit test every few minutes with the Hrmony/ESW nnocycle Test-driven development produces unit tests simultneously with models nd code Constnt elbortion nd execution of the unit test suite Continuous integrtion of components nd subsystems removes integrtion problems erly Schedules re trcked frequently for devitions from pln with Bruce s Evlution nd Review Technique (BERT) workflow Softwre estimtion ccurcy is improved with the Effect Review for Nnocycle Itertion Estimtion (ERNIE) workflow Project issues nd rodblocks re identified frequently nd ddressed t lest every microcycle itertion (4-6 weeks) 14

15 Key Views of Architecture: Some key prctices Hrmony/ESW identifies 5 key views of Architecture (t right) Architecture focuses on overll design optimiztion concerns in ech of the rchitecturl views In ech view, n optimiztion workflow is followed: Identify the relevnt design optimiztion criteri Rnk criteri in order of criticlity Identify design ptterns nd/or technologies tht provide the importnt criteri t the expense of the lesser Apply design ptterns Test 15

16 Pln, Trck, nd Adpt: Some key prctices Dynmic plnning ensures tht plns lwys reflect truth on the ground Trcking is performed ginst gols (e.g. working functionlity relized/vlidted) not ginst implementtion (e.g. lines of code written) Plns re reviewed nd updted t lest once per microcycle in the Increment Review (Prty) phse of the microcycle Scheduling is done vi the BERT workflow 3 schedules re produced Working schedule (bsed on weighted e 20, e 50, nd e 80 ) Customer schedule (bsed on weighted e 80 ) Gol schedule (bsed on weighted e 20 ) 16

17 Risk Mngement: Some key prctices Risks re ctively identified, rnked, nd ddressed with scheduled risk mitigtion ctivities Risks re trcked in the Risk Mngement Pln (Excel templte is provided) Risks re trcked dily Risks re reevluted t lest once per microcycle in the Increment Review (Prty) phse 17

18 Modeling: Some key prctices High-qulity semntic rich models re emphsized Models re continuously (nd utomticlly) synchronized with the source code ( dynmic model-code ssocitivity ) Model orgniztion optimizes tem collbortion while minimizing coupling between tems Constructed models Anlysis models (k Pltform Independent Models) produce correctly-executing models nd source code of the necessry functionlity Design models (k Pltform Specific Models) products optimized models nd source code, optimizing the weighted set of design criteri Ech digrm is hs singulr concept (mission) nd includes ll elements relevnt to tht mission nd no elements not so relevnt 18

19 Hrmony/ESW is Agile nd Model-Driven Hrmony/ESW incorportes number of gile prctices Test-First Design Continuous Integrtion Agile Estimtion Microcycle plnning nd ssessment within the context of n itertive, incrementl lifecycle (microcycle). 19

20 Governnce Model Blncing Agility nd Discipline Hrmony/ESW incorportes three-tiered governnce model to pln, execute, nd monitor progress. These tiers correspond to personl, tem nd stkeholder concerns nd ech opertes t different time scle nd level of detil. 20

21 Hrmony/ESW Project Lifecycle Hrmony/ESW uses n itertive, incrementl lifecycle. 21

22 Prespirl Plnning Prespirl Plnning is ment to set up the informtion nd tems for the project 22

23 Develop Stkeholder Requirements This ctivity is ment to define the vision nd scope of the project nd provide set of customer-level requirements 23

24 Microcycle Lifecycle The softwre development tkes plce with series of itertions, known s microcycles Ech microcycle produces fully vlidted version of the model, source code nd constructed system ( prototype ) tht incorportes subset of the use cses Ech prototype dds on to the functionlity delivered in previous microcycle prototypes 24

25 Prototype Definition Defines the mission nd scope for the next microcycle including Use cses relized Architecturl intent relized Risk mitigtion ctivities performed Defects repired Trget pltforms supported 25

26 Hrmony/ESW Lifecycle WBS 26

27 Hrmony Disciplines A discipline is collection of tsks tht re relted to mjor "re of concern" within the overll project. Within the lifecycle, tsks re performed concurrently cross severl disciplines. Seprting tsks into distinct disciplines is simply n effective wy to orgnize content tht mkes comprehension esier. Hrmony/ESW defines the following Disciplines: 27

28 Project Mngement Discipline 28

29 Hrmony/ESW Roles 29

30 Softwre Modeler Role 30

31 A Typicl Tsk Description Tsks typiclly hve n ssocited concept, guideline nd checklist. If one needs to perform tsk one reds the concept to understnd the context, reds the steps to determine wht needs to be done, reds the guideline to determine how to do it, then reds the checklist to vlidte completion. 31

32 A Typicl Artifct Description Typiclly rtifcts hve ssocited templtes nd checklists. The templte provides dditionl guidnce on completing the rtifct nd The checklist helps check the qulity of the resulting rtifct. 32

33 Deployment of Hrmony/ESW services Interctive EPF-bsed Hndbook Project templte tht guides workers from concept to delivered system Flexibility of hving electronic Process Hndbook vs. trditionl document-bsed Hndbook in Rhpsody Rpid Deployment Process Trining The Hrmony/ESW Process 3-dy hnds-on course developed by Dr. Bruce Douglss Introduction to EPF for Hrmony/ESW 1-dy Introduction to Hrmony nd EPF Concentrtes on how Hrmony/ESW cn be customized Introduction to EPF Custom trining bsed on client needs during project deployment 33

34 Hrmony/ESW Website 34

35 Summry Hrmony/ESW is coherent set of best prctices ment to effectively relize set of core principles Hrmony/ESW is Requirements-driven Architecture-centric Optimized for Systems nd Softwre Engineering projects Rel-time Embedded Hrdwre-softwre co-design Sclbility from smll to lrge systems projects 35

36 Thnks for your ttention & ny questions? 36