LEADER 04278nam  2200745 a 450 
001 996465981403316
005 20200520144314.0
010   $a1-280-38943-5
010   $a9786613567352
010   $a3-642-16086-7
024 7 $a10.1007/978-3-642-16086-8
035   $a(CKB)2670000000045138
035   $a(SSID)ssj0000446837
035   $a(PQKBManifestationID)11308429
035   $a(PQKBTitleCode)TC0000446837
035   $a(PQKBWorkID)10504528
035   $a(PQKB)10674718
035   $a(DE-He213)978-3-642-16086-8
035   $a(MiAaPQ)EBC3065870
035   $a(Au-PeEL)EBL3065870
035   $a(CaPaEBR)ebr10419671
035   $a(CaONFJC)MIL356735
035   $a(OCoLC)676698660
035   $a(BIP)032334106
035   $a(PPN)149024592
035   $a(EXLCZ)992670000000045138
100   $a20100816d2010      uy             0
101 0 $aeng
135   $aurnn|008mamaa
181   $ctxt
182   $cc
183   $acr
200 02$aA common case study for aspect-oriented modeling$b[electronic resource] /$fShmuel Katz, Mira Mezini, Joerg Kienzle (eds.)
205   $a1st ed. 2010.
210   $aBerlin ;$aNew York $cSpringer$d2010
215   $a1 online resource (XV, 423 p. 234 illus.) 
225 1 $aLecture notes in computer science,$x0302-9743 ;$v6210
225 0 $aTransactions on aspect-oriented software development,$x1864-3027 ;$v7
300   $aBibliographic Level Mode of Issuance: Monograph
311   $a3-642-16085-9 
320   $aIncludes bibliographical references and index.
327   $aCrisis Management Systems: A Case Study for Aspect-Oriented Modeling -- Requirements Modeling with the Aspect-oriented User Requirements Notation (AoURN): A Case Study -- Relating Feature Models to Other Models of a Software Product Line -- Aspect-Oriented Development Using Protocol Modeling -- Using VCL as an Aspect-Oriented Approach to Requirements Modelling -- Workflow Design Using Fragment Composition -- Modeling the Car Crash Crisis Management System Using HiLA -- Aspect-Oriented Design with Reusable Aspect Models -- A Graph-Based Aspect Interference Detection Approach for UML-Based Aspect-Oriented Models -- Discovery of Stable Abstractions for Aspect-Oriented Composition in the Car Crash Management Domain.
330   $a? Those who want to learn about AOM ?nd in this special issue a concise collection of descriptions of solid and mature AOM approaches. They only have to take the time to understand one case study in order to appreciate the sample models shown in all papers. ? Those who want to apply AOM for a particular purpose and are looking for the most appropriate AOM technique can use the papers presented in this specialissue to identify the mostpromisingapproach(es).By identifying similarities between their problem and the case study they should be able to determine candidate AOM approaches easily. ? Those working on their own AOM approach can readily identify approaches that were able to handle concerns that their own approach is not able to handle elegantly. This stimulates cross-fertilization between approaches and collaborative research. ? Thoseengineering researchersthat areworkingon enhancing softwaredev- opment processes can use the example models presented in this special issue to understand the potential bene?ts of using AOM techniques at di?erent phases of the software development life-cycle.
410  0$aLecture notes in computer science ;$v6210.
606   $aComputer software$xDevelopment
606   $aObject-oriented programming (Computer science)
606   $aAspect-oriented programming
610   $aObject-Oriented Programming (Computer Science)
610   $aComputer Software
610   $aAspect-Oriented Programming
610   $aComputers
615  0$aComputer software$xDevelopment.
615  0$aObject-oriented programming (Computer science)
615  0$aAspect-oriented programming.
676   $a005.1
702   $aKatz$b Shmuel$4oth
702   $aMezini$b Mira$4oth
702   $aKienzle$b Jo?rg$4oth
801  0$bMiAaPQ
801  1$bMiAaPQ
801  2$bMiAaPQ
906   $aBOOK
912   $a996465981403316
996   $aA common case study for aspect-oriented modeling$93422161
997   $aUNISA