LEADER 05461nam 2200685 a 450 001 9910139054703321 005 20230802012933.0 010 $a1-118-56137-6 010 $a1-118-56973-3 010 $a1-299-31489-9 010 $a1-118-56979-2 035 $a(CKB)2560000000100583 035 $a(EBL)1144073 035 $a(OCoLC)830161156 035 $a(SSID)ssj0000833674 035 $a(PQKBManifestationID)11418312 035 $a(PQKBTitleCode)TC0000833674 035 $a(PQKBWorkID)10936261 035 $a(PQKB)11132561 035 $a(OCoLC)839304736 035 $a(MiAaPQ)EBC1144073 035 $a(Au-PeEL)EBL1144073 035 $a(CaPaEBR)ebr10674776 035 $a(CaONFJC)MIL462739 035 $a(EXLCZ)992560000000100583 100 $a20130419d2012 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aModel-driven and software product line engineering$b[electronic resource] /$fHugo Arboleda, Jean-Claude Royer 210 $aLondon $cISTE ;$aHoboken, N.J. $cJohn Wiley & Sons$dc2012 215 $a1 online resource (290 p.) 225 1 $aISTE 300 $aDescription based upon print version of record. 311 $a1-84821-427-8 320 $aIncludes bibliographical references and index. 327 $aCover; Title Page; Copyright Page; Table of Contents; Chapter 1. Introduction; 1.1. Software product line engineering; 1.2. Model-driven engineering; 1.3. Merging model-driven and software product line engineering; 1.4. The FieSta framework; 1.5. Book structure; Chapter 2. Software Product Line Engineering Basics; 2.1. Introduction to product line engineering; 2.2. Brief history; 2.3. Application example: Smart-Home systems; 2.3.1. Smart-Home system's domain; 2.3.2. Requirements of the application example; 2.4. Software product line engineering; 2.5. Domain engineering 327 $a2.5.1. Component-based software engineering2.6. Variability management; 2.6.1. Feature modeling; 2.7. Application engineering; 2.7.1. Product configuration; 2.7.2. Product derivation; 2.8. Benefits and drawbacks; 2.9. Issues in product line; 2.9.1. Variability management; 2.9.2. Product derivation; 2.9.3. Testing; 2.9.4. Traceability; 2.9.5. Product line evolution; 2.9.6. Tool support; 2.10. Summary; Chapter 3. Model-Driven Engineering; 3.1. Introduction; 3.2. Models and metamodels; 3.2.1. The 4-level metamodeling framework; 3.2.2. The nature of models; 3.3. UML class diagrams and OCL 327 $a3.4. Model transformations3.4.1. Scheduling of transformation rules; 3.4.2. Model transformation patterns; 3.4.3. Classification of model transformations; 3.4.4. Vertical model transformations; 3.4.5. Horizontal model transformations; 3.4.6. Model composition or model weaving; 3.5. Modeling framework; 3.5.1. The eclipse modeling framework; 3.5.2. The topcased toolkit; 3.6. Model transformation languages; 3.6.1. QVT; 3.6.2. ATL; 3.6.3. The open Architecture Ware framework; 3.6.4. The Xtend language; 3.7. Benefits and challenges for SPLE; 3.8. Summary 327 $aChapter 4. Model-Driven and Software Product Line Engineering4.1. Introduction; 4.2. Problem space issues; 4.2.1. Separating points of views; 4.2.2. Capturing variability and configuring products; 4.2.3. Relating several points of view; 4.2.4. Configuring products in a multi-staged process; 4.3. Solution space issues; 4.4. Developing core assets; 4.4.1. Developing decision models and deriving products; 4.5. Variability expression and product configuration; 4.5.1. Metamodels; 4.5.2. Feature models; 4.6. Core asset development and product derivation 327 $a4.6.1. Transformation rules in the Smart-Home systems SPL4.6.2. Creating and using decision models; 4.7. Summary; Chapter 5. The FieSta Framework: Fine-Grained Derivation and Configuration; 5.1. Introduction; 5.1.1. Coarse-grained and fine-grained variations; 5.2. Binding models and constraint models; 5.2.1. Binding models; 5.2.2. Constraint models; 5.2.3. The cardinality property; 5.2.4. The structural dependency property; 5.2.5. The constraint metamodel and the binding metamodel; 5.2.6. Validating binding models against constraint models 327 $a5.3. Deriving products based on constraint models and binding models 330 $a Many approaches to creating Software Product Lines have emerged that are based on Model-Driven Engineering. This book introduces both Software Product Lines and Model-Driven Engineering, which have separate success stories in industry, and focuses on the practical combination of them. It describes the challenges and benefits of merging these two software development trends and provides the reader with a novel approach and practical mechanisms to improve software development productivity.The book is aimed at engineers and students who wish to understand and apply software product lines 410 0$aISTE publications. 606 $aSoftware product line engineering 606 $aModel-driven software architecture 615 0$aSoftware product line engineering. 615 0$aModel-driven software architecture. 676 $a005.1 700 $aArboleda$b Hugo$0934062 701 $aRoyer$b Jean-Claude$0934063 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910139054703321 996 $aModel-driven and software product line engineering$92103022 997 $aUNINA