1. Introduction1.1. Foreword1.2. Outline1.3. Who’s who1.4. Getting more information about the KAOS approach2. Key ideas underlying KAOS2.1. Build a requirements model2.2. Justify your requirements by linking them to higher-level goals2.3. Build a model of the whole system, not just the software part of it2.4. Build a responsibility model2.5. Build a consistent and complete glossary of all the problem-related terms you use to write the requirements2.6. Describe how the agents need to behave in order to satisfy the requirements they are responsible for2.7. Base the requirements document on the requirements model2.8. Validate your requirements by first reviewing the model2.9. Use a defensive approach to the building of a requirements model3. The Elevator case study3.1. Problem statement3.2. Goal model3.2.1. Requirements patterns3.2.2. Application to the elevator problem3.3. Responsibility model3.4. Object model3.5. Operation model3.6. Dealing with obstacles3.7. Requirements document generation3.7.1. Requirements document structure3.7.2. How to fill in the template from a KAOS model4. Discussion4.1. Is it worth paying attention to a Kaos analysis?4.2. Traceability4.3. Completeness4.4. No ambiguity4.5. For which project size is it worth thinking of using Kaos ?5. Conclusion6. Methodology summary6.1. KAOS meta-model6.2. KAOS glossary!!Tutorial!V1.0!!Oct.!18,!2007!!!!!!©!Respect"IT,!2007!!"#!$%"&'()*+,-!"#!$%"&'()*+,-" © ./01/2(34&"0,"" 5,6/"7" Revision Table Version Date Modified pages Modified sections Comments!"#!$%"&'()*+,-" © ./01/2(34&"0,"" 5,6/"8" Table of Contents TABLE!OF!CONTENTS!......................................................................................................................!3!1.! INTRODUCTION!...............................................................................................................!5!1.1.! FOREWORD! 5!1.2.! OUTLINE! 5!1.3.! WHO’S!WHO! 5!1.4.! GETTING!MORE!INFORMATION!ABOUT!THE!KAOS!APPROACH! 5!2.! KEY!IDEAS!UNDERLYING!KAOS!.........................................................................................!6!2.1.! BUILD!A!REQUIREMENTS!MODEL! 6!2.2.! JUSTIFY!YOUR!REQUIREMENTS!BY!LINKING!THEM!TO!HIGHER"LEVEL!GOALS! 6!2.3.! BUILD!A!MODEL!OF!THE!WHOLE!SYSTEM,!NOT!JUST!THE!SOFTWARE!PART!OF!IT! 7!2.4.! BUILD!A!RESPONSIBILITY!MODEL! 7!2.5.! BUILD!A!CONSISTENT!AND!COMPLETE!GLOSSARY!OF!ALL!THE!PROBLEM"RELATED!TERMS!YOU!USE!TO!WRITE!THE!REQUIREMENTS! 8!2.6.! DESCRIBE!HOW!THE!AGENTS!NEED!TO!BEHAVE!IN!ORDER!TO!SATISFY!THE!REQUIREMENTS!THEY!ARE!RESPONSIBLE!FOR! 8!2.7.! BASE!THE!REQUIREMENTS!DOCUMENT!ON!THE!REQUIREMENTS!MODEL! 9!2.8.! VALIDATE!YOUR!REQUIREMENTS!BY!FIRST!REVIEWING!THE!MODEL! 9!2.9.! USE!A!DEFENSIVE!APPROACH!TO!THE!BUILDING!OF!A!REQUIREMENTS!MODEL! 9!3.! THE!ELEVATOR!CASE!STUDY!...........................................................................................!11!3.1.! PROBLEM!STATEMENT! 11!3.2.! GOAL!MODEL! 11!3.2.1.! REQUIREMENTS!PATTERNS!...........................................................................................................!11!3.2.2.! APPLICATION!TO!THE!ELEVATOR!PROBLEM!......................................................................................!13!3.3.! RESPONSIBILITY!MODEL! 23!3.4.! OBJECT!MODEL! 26!3.5.! OPERATION!MODEL! 30!3.6.! DEALING!WITH!OBSTACLES! 34!3.7.! REQUIREMENTS!DOCUMENT!GENERATION! 37!3.7.1.! REQUIREMENTS!DOCUMENT!STRUCTURE!........................................................................................!37!3.7.2.! HOW!TO!FILL!IN!THE!TEMPLATE!FROM!A!KAOS!MODEL!.....................................................................!39!4.! DISCUSSION!..................................................................................................................!41!4.1.! IS!IT!WORTH!PAYING!ATTENTION!TO!A!KAOS!ANALYSIS?! 41!4.2.! TRACEABILITY! 41!4.3.! COMPLETENESS! 41!!"#!$%"&'()*+,-" © ./01/2(34&"0,"" 5,6/"9" 4.4.! NO!AMBIGUITY! 42!4.5.! FOR!WHICH!PROJECT!SIZE!IS!IT!WORTH!THINKING!OF!USING!KAOS!?! 42!5.! CONCLUSION!.................................................................................................................!44!6.! METHODOLOGY!SUMMARY!..........................................................................................!45!6.1.! KAOS!META"MODEL! 45!6.2.! KAOS!GLOSSARY! 45!!"#!$%"&'()*+,-" © ./01/2(34&"0,"" 5,6/":" 1. Introduction 1.1. Foreword KAOS is a methodology for requirements engineering enabling analysts to build requirements models and to derive requirements documents from KAOS models. In this tutorial, you will learn how to build a KAOS model step by step and how to generate a requirements document based on this model. Objectiver is a tool designed to support KAOS. All diagrams in this tutorial have been generated by this tool. 1.2. Outline The tutorial is structured as follows: ! Key ideas underlying KAOS. The section introduces KAOS; it gives the main ideas and processes you have to keep in mind to build a successful requirements document with KAOS. ! Analysis of a case study, where the requirements will be gathered for the design of a new elevator system. The case study will let us show you how the KAOS approach favors the identification of interesting properties and alternative unexpected designs. But you should keep in mind that KAOS can be used for any type of information system. We have been using it for many years in different industries such as steel, mechanics, telecommunication, health care. We also used the KAOS approach for public administrations, ... 1.3. Who’s who KAOS originates from a cooperation between the University of Oregon and the University of Louvain (Belgium) in 1990. Research, extensions and improvements are still being made to the methodology on a regular basis at the University of Louvain. Respect-IT is a spin-out company of the University of Louvain. Respect-IT has put the method to practice on dozens of industrial cases in different sectors. Respect-IT has built and is now distributing Objectiver, a tool that supports KAOS. 1.4. Getting more information about the KAOS approach Scientific papers and slide presentations shown during conference keynotes can be found on the following Web site: http://www.info.ucl.ac.be/research/projects/AVL/ReqEng.html Return on experience and reports on the KAOS approach can be found on Objectiver’s web site : http://www.objectiver.com/!"#!$%"&'()*+,-" © ./01/2(34&"0,"" 5,6/";" 2. Key
View Full Document
Unlocking...