with KAOS/Objectiver Robert Darimont E mail: it.be JDEV /9/2013

Transcription

1 GORE: from Theory to Practice with KAOS/Objectiver Robert Darimont E mail: Robert.Darimont@respect it.be JDEV /9/2013 / 1

2 Outline sa RESPECT IT Introduction Objectiver in action Process overview Short example & demo Synthesis pj Examples of Objectiver artefacts Requirements Documents Supportto to tenderassessment Regulation Modelling Conclusion 2

3 Position in the life cycle Bridging the gap Business <> IT Define objectives & requirements Design sa RESPECT IT Business Manage Approve Accept Implement Develop Deliver IT Define future evolutions Maintain Objectiver 3

4 Addressing the problem space Problem space Solution space Initial Request Initial Requirements Change Requirements Requirements document Test case information Design Implementation Verification Change Request Validation Result Requirements Engineering i Verification: build the system right Validation: build the right ihtsystem 4

5 Position in the life cycle RE versus RM Engineering Management Requirements Engineering Tool (RE) Objectiver Requirements Management Tool (RM) Doors (IBM/Telelogic) RequisitePro (IBM Rational) CaliberPro (Borland) Reqtify Objectiver focuses on engineering gthe requirements. Tool complementary of market leaders in RM. Design Tool (UML, ) Enterprise Architect (Sparx) Topcased Open source) Tau (IBM/Telelogic) ll i) Rose (IBM Rational) Together (Borland) 5

6 No philosopher s p stone Movie industry Software Industry Requirements Engineering Method/Tool Bad Script Bad /Good Actors Bad Requirements Better Requirements Video Editing Software Rubbishy Movie Requirements Management Tool Bad Software Requirements Management Tool Better Software Bad requirements eventually put the project into jeopardy pull out all the stops for RE

7 RE & the Software Life Cycle RESPECT IT sa RE whatever SLC you use

8 Objectiver: key points sa RESPECT IT A GORE methodology focusing on the objectives to be satisfied strategical business technical + relationships the commitment of agents in the system in the environment Responsibilities, Scope, Interfaces the risks (obstacles, threats, ) to build consistent and complete sets ofrequirements to think & communicate about requirements

9 Outline sa RESPECT IT Introduction Objectiver in action Process overview Short example & demo Synthesis pj Examples of Objectiver artefacts Requirements Documents Supportto to tenderassessment Regulation Modelling Conclusion 9

10 KAOS/Objectiver: key process Interviews Existing systems Documents RESPECT IT sa Modeling Validation KAOS model Web doc Generating Requirements document 10

11 Requirements Elicitation

12 Requirements modelling

13 Requirements Documentation

14 RESPECT IT sa

15 Requ irements Do cument Generation

16 Outline sa RESPECT IT Introduction Objectiver in action Process overview Short example & demo Synthesis pj Examples of Objectiver artefacts Requirements Documents Supportto to tenderassessment Regulation Modelling Conclusion 16

17 Mini case study Context: SAFEE project EEC 6th FP 17

18 31 partners, 11 countries, 36 M budget, 4 years ( ) 18

19 Project organization TARMS: Threat Assessment & Response Management System SUB-PROJECT 1: ON-BOARD THREAT DETECTION Detection of abnormal events SUB-PROJECT 2: THREAT ASSESSMENT AND RESPONSE MANAGEMENT SYSTEM Consolidation and fusion of threat signals Proposition of courses of actions SUB-PROJECT 3: FLIGHT PROTECTION against hostile attempts ACTIONS SUB-PROJECT 4: DATA, deals with this complete process for data only 19

20 Mini case study: context sa RESPECT IT Interview: A350 pilot... It is essential that the cockpit door be kept closed dduring the whole flight. It prevents any offender from penetrating into the cockpit and from taking control of the A/C.... To be continued in the Objectiver tool

21 Outline sa RESPECT IT Introduction ti Objectiver in action Process overview Short example & demo Synthesis Examples of Objectiver artefacts Requirements Documents Support to tender assessment Regulation Modelling Conclusion NB: PM Case study: Car Park Management System 21

22 Synthesis RESPECT IT sa

23 Objectiver meta modelmodel Goal lmodel Responsibility Model sa RESPECT IT Object Model Operation Model

24 Objectiver meta modelmodel Goal Model Responsibility Model sa RESPECT IT Object Model Operation Model

25 Synthesis: KAOS/Objectiver in one slide 25

26 Outline sa RESPECT IT Introduction ti Objectiver in action Process overview Short example & demo Synthesis Examples of Objectiver artefacts Requirements Documents Support to tender assessment Regulation Modelling Conclusion NB: PM Case study: Car Park Management System 26

27 sa RESPECT IT Requirements Documents Typical structure: t Introduction Objective of the document Scope Main Use cases User typology Domain overview: domain taxonomy, main processes Definitions, Abbreviations & acronyms ( Object Model) Reference Overview Goals, requirements & expectations Responsibilities See example

28 Outline sa RESPECT IT Introduction ti Objectiver in action Process overview Short example & demo Synthesis Examples of Objectiver artefacts Requirements Documents Support to tender assessment Regulation Modelling Conclusion NB: PM Case study: Car Park Management System 28

29 Support to tender assessment sa RESPECT IT Assessment form based on the list of requirements Tenders required to evaluate the level of coverage of each requirement Metrics used to assess the compliance of a tender to a requirements document Tender s evaluation part of the contract See example

30 Outline sa RESPECT IT Introduction ti Objectiver in action Process overview Short example & demo Synthesis Examples of Objectiver artefacts Requirements Documents Support to tender assessment Regulation Modelling Conclusion NB: PM Case study: Car Park Management System 30

31 Regulation analysis Regulation Text: Step 1 Annotations: traceability from the regulation text to the model Regulation Model: Step 2 Respect IT sa

32 Columns: System Requirement System involvement Step 4 Blue rectangle: system contributes to the regulation requirement (derived from the requirements model) Lines: Requirementsfromthe regulation Traceability from regulation to system System Contribution & Impact Refinement Operationalization Step 3 Respect IT sa

33 Step 5 System compliance assessment Empty column: system requirement not involved in the regulation commitment Columns: System Requirement Blue rectangle: system contributes tib t to the regulation requirement Empty line: no evidence that the system complies with the regulation requirement Lines: Requirements from the regulation Respect IT sa

34 Outline sa RESPECT IT Introduction ti Objectiver in action Process overview Short example & demo Synthesis Examples of Objectiver artefacts Requirements Documents Support to tender assessment Regulation Modelling Conclusion NB: PM Case study: Car Park Management System 34

35 Conclusion RESPECT IT sa