Modeling Volatile Concerns as Aspects

  • Ana Moreira
  • João Araújo
  • Jon Whittle
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4001)


A rapidly changing market leads to software systems with highly volatile requirements. These must be managed in a way that reduces the time and costs associated with updating a system to meet these new requirements. By externalizing volatile concerns, we can build a stepping-stone for future management of unanticipated requirements change. In this paper, we present a method for handling volatile concerns during early lifecycle software modeling. The key insight is that aspect-oriented techniques can be applied to modularize volatility and to weave volatile concerns into the base software artifacts.


Unify Modeling Language Activity Diagram Role Element Composition Rule Subway Station 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Baniassad, E., Clarke, S.: Theme: An approach for aspect-oriented analysis and design. In: ICSE 2004, Scotland (2004)Google Scholar
  2. 2.
    Chung, L., Nixon, B., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, Dordrecht (2000)MATHGoogle Scholar
  3. 3.
    Clarke, S., Walker, R.J.: Composition Patterns: An Approach to Designing Reusable Aspects. In: ICSE 2001 (2001)Google Scholar
  4. 4.
    Clements, P., Northrop, L.: Software Product Lines: Practices and Patterns. Addison Wesley, Reading (2002)Google Scholar
  5. 5.
    Czarnecki, K., Eisenecker, U.: Generative Programming. Addison Wesley, Reading (2000)MATHGoogle Scholar
  6. 6.
    Dahlstedt, Å., Persson, A.: Requirements Interdependencies - Moulding the State of Research into a Research Agenda. In: REFSQ 2003, Austria, pp. 71–80 (2003)Google Scholar
  7. 7.
    Firesmith, D.G.: Creating a Project-Specific Requirements Engineering Process. Journal of Object Technology 3(5), 31–44 (2004)CrossRefGoogle Scholar
  8. 8.
    France, R., Kim, D., Ghosh, S., Song, E.: A UML-Based Pattern Specification Technique. IEEE Transactions on Software Engineering 30(3) (2004)Google Scholar
  9. 9.
    Jacobson, I., Ng, P.: Aspect-Oriented Software Development with Use Cases. Addison-Wesley, Reading (2005)Google Scholar
  10. 10.
    Kiczales, G., Hilsdale, E., Hugunin, J., Kersten, M., Palm, J., Griswold, W.: An overview of AspectJ. In: Knudsen, J.L. (ed.) ECOOP 2001. LNCS, vol. 2072, pp. 327–353. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  11. 11.
    Sampaio, A., Chitchyan, R., Rashid, A., Rayson, P.: EA-Miner: A Tool for Automating Aspect-Oriented Requirements Identification. In: ASE 2005. IEEE Computer Society, Los Alamitos (2005)Google Scholar
  12. 12.
    Sommerville, I.: Software Engineering, 7th edn. Addison-Wesley, Reading (2004)Google Scholar
  13. 13.
    UML Specification, version 2.0, in OMG (August 2005) ,
  14. 14.
    Whittle, J., Araújo, J.: Scenario Modeling with Aspects. IEE Proceedings Software 151(04), 157–172 (2004)CrossRefGoogle Scholar
  15. 15.
    Survey on Aspect-Oriented Analysis & Design Approaches,

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Ana Moreira
    • 1
  • João Araújo
    • 1
  • Jon Whittle
    • 2
  1. 1.CITI/Dept. Informática, FCTUniversidade Nova de LisboaCaparicaPortugal
  2. 2.ISE Dept.George Mason UniversityFairfaxUSA

Personalised recommendations