Variability and Aspect Orientation

Chapter
First Online:

Abstract

Variability is an inherent property of software product lines. In software product line engineering, variability must be systematically described and managed throughout all development activities. Variability in a software product line is often analyzed and modeled in terms of features. Optional or alternative features in a feature diagram [1, 2] represent units of variations in requirements. However, realizing a feature may affect several parts of core assets (e.g., architectures or implementation components) instead of being localized.

Keywords

Product Line Software Product Line Feature Dependency Modular Unit Feature Diagram 
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.
This is a preview of subscription content, log in to check access.

References

  1. 1.
    Kang, K.C., Cohen, S.G., Hess, J.A., Novak, W.E., Peterson, A.S.: Feature-oriented domain analysis (FODA) feasibility study. Technical report, SEI, Carnegie Mellon University, Pittsburgh, PA (1990)Google Scholar
  2. 2.
    Czarnecki, K., Helsen, S., Eisenecker, U.: Staged configuration using feature models. In: Proc. SPLC 2004, pp. 266–283 (2004)Google Scholar
  3. 3.
    Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C. Lopes, C., Loingtier, J.-M., Irwin, J.: Aspect-oriented programming. In: Proc. ECOOP 1997, pp. 220–242 (1997)Google Scholar
  4. 4.
    Lee, K., Kang, K.C.: Feature dependency analysis for product line component design. In: Proc. ICSR 2004, Madrid, Spain, pp. 69–85. Springer (2004)Google Scholar
  5. 5.
    Kästner, C., Apel, S., ur Rahman, S., Rosenmüller, M., Batory, D., Saake, G.: On the impact of the optional feature problem: analysis and case studies. In: Proc. SPLC 2009, pp. 181–190 (2009)Google Scholar
  6. 6.
    Alves, V., Matos, Jr., P., Cole, L., Borba, P., Ramalho, G.: Extracting and evolving mobile games product lines. In: Proc. SPLC 2005, pp. 70–81 (2005)Google Scholar
  7. 7.
    Kästner, C., Apel, S., Batory, D.: A case study implementing features using AspectJ. In: Proc. SPLC 2007, pp. 223–232 (2007)Google Scholar
  8. 8.
    Zhang, C., Jacobsen, H.-A.: Refactoring middleware with aspects. IEEE Trans. Parallel Distr. Syst. 14(11), 1–16 (2003)CrossRefGoogle Scholar
  9. 9.
    Viega, J., Bloch, J.T., Chandra, P.: Applying aspect-oriented programming to security. Cutter IT Journal 14(2):31–39, February 2001Google Scholar
  10. 10.
    Szentiványi, D., Nadjm-Tehrani, S.: Aspects for improvement of performance in fault-tolerant software. In: Proc. PRDC 2004, pp. 283–291 (2004)Google Scholar
  11. 11.
    Liu, J., Batory, D., Lengauer, C.: Feature-oriented refactoring of legacy applications. In: Proc. ICSE 2006, pp. 112–121 (2006)Google Scholar
  12. 12.
    Lee, K., Botterweck, G., Thiel, S.: Aspectual separation of feature dependencies for flexible feature composition. In: Proc. COMPSAC 2009, pp. 45–52 (2009)Google Scholar
  13. 13.
    Calder, M., Kolberg, M., Magill, E.H., Reiff-Marganiec, S.: Feature interaction – a critical review and considered forecast. Comput. Netw. 41(1), 115–141 (2003)MATHCrossRefGoogle Scholar
  14. 14.
    William, G., Shonie, M., Sullivan, K., Song, Y., Tewari, N., Cai, Y., Rajan, H.: Modular software design with crosscutting interfaces. IEEE Softw. 23(1), 51–60 (2006)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  1. 1.Department of Information Systems EngineeringHansung UniversitySeoulRepublic of Korea

Personalised recommendations