work for small problems, but it introduces signi?cant accidental complexities when tackling larger problems. Notethattherealchallengehereisnothowtodesignthesystemtotakeap- ticular aspect into account: there is signi?cant design know-how in industry on this and it is often captured in the form of des
[Lecture Notes in Computer Science] Transactions on Aspect-Oriented Software Development VII Volume 6210 || Requirements Modeling with the Aspect-oriented User Requirements Notation (AoURN): A Case Study
✍ Scribed by Katz, Shmuel; Mezini, Mira; Kienzle, Jörg
- Book ID
- 119977983
- Publisher
- Springer Berlin Heidelberg
- Year
- 2010
- Tongue
- English
- Weight
- 175 KB
- Edition
- 1
- Category
- Article
- ISBN
- 3642160867
No coin nor oath required. For personal study only.
✦ Synopsis
– 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.
📜 SIMILAR VOLUMES