File information: | |
File name: | variability_RE_SPL0311.pdf [preview DT 1530A] |
Size: | 584 kB |
Extension: | |
Mfg: | Daytek |
Model: | DT 1530A 🔎 |
Original: | |
Descr: | plz open it |
Group: | Electronics > Automobile > Electrical diagram |
Uploaded: | 21-07-2005 |
User: | hafeezullah |
Multipart: | No multipart |
Information about the files in archive: | ||
Decompress result: | OK | |
Extracted files: | 1 | |
File name variability_RE_SPL0311.pdf FUNDP - Equipe LIEL Institut d'Informatique Rue Grandgagnage, 21 B - 5000 NAMUR (Belgique) Modelling variability requirements in Software Product Lines: a comparative survey Jean-Christophe T RIGAUX and Patrick H EYMANS Project : Financing: Product Line ENgineering of food TraceabilitY software "Région wallonne" and "Fonds Social Européen" First Europe Objectif 3 EPH3310300R0462 / 215315 15 November 2003 2 Contents 1 Introduction 5 2 An Overview of Variability 2.1 2.2 2.3 2.4 Definitions of Variability . . . . . . . . . . . . . . . . . . . . . . . . Categories of Variability . . . . . . . . . . . . . . . . . . . . . . . . Levels of Variability . . . . . . . . . . . . . . . . . . . . . . . . . . . Mechanisms of Variability . . . . . . . . . . . . . . . . . . . . . . . 5 5 6 8 9 3 Modelling Variability 3.1 3.2 Modelling variability: requirements . . . . . . . . . . . . . . . . . . Modelling Variability with Feature Diagrams . . . . . . . . . . . . . 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.3 FODA's notation . . . . . . . . . . . . . . . . . . . . . . . . FORM's notation . . . . . . . . . . . . . . . . . . . . . . . . FeatuRSEB's notation . . . . . . . . . . . . . . . . . . . . . J.Bosch's Notation . . . . . . . . . . . . . . . . . . . . . . . Riebish's Notation . . . . . . . . . . . . . . . . . . . . . . . 9 9 10 11 12 13 15 16 19 19 19 20 22 Modelling Variability with Use Cases . . . . . . . . . . . . . . . . . 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 Classical Use Cases . . . . . . . . . . . . . . . . . . . . . . . Variability and classical Use Cases . . . . . . . . . . . . . . . Extending Use Case templates . . . . . . . . . . . . . . . . . Extending Use Case diagrams . . . . . . . . . . . . . . . . . Add Decision Model and Extend Use Case diagrams & templates 26 29 31 3.4 3.5 Modelling Variability with Use Cases & Feature Diagrams . . . . . . Modelling Variability with UML Class Diagrams . . . . . . . . . . . 4 Comparison between graphical notations designed to model variation points and variants 33 5 Case Study: Engine Monitoring 38 6 Conclusion 3 49 4 1 Introduction The increase of variability leads to a situation where the complexity of managing it becomes a primary concern during software development. Variability affects the whole product line process, from requirements to code. Clearly, we need specific solutions to support variability during software product line development. However, in current practice, designers often give variability incidental treatments. They typically introduce it during late design or implementation. Even, they express it through myriad of inventive tricks. The point is that variability must be managed already during requirements engineering. Indeed, in initial project's phases, a key to success is efficient communication between the designers and the stakeholders about requirements and thus variability. Nevertheless, in the software product lines context, a major difficulty can occur because no standard |
Date | User | Rating | Comment |