Aspect-oriented Requirements Engineering with Problem Frames

Stephan Faßbender, Maritta Heisel, Rene Meis

2014

Abstract

Nowadays, the requirements of various stakeholders for a system do not only increase the complexity of the system-to-be, but also contain different cross-cutting concerns. In such a situation, requirements engineers are really challenged to master the complexity and to deliver a coherent and complete description of the system-to-be. Hence, they are in need for methods which reduce the complexity, handle functional and quality requirements, check completeness and reveal interactions, and are tool supported to lower the effort. One possible option to handle the complexity of a system-to-be is the separation of concerns. Both, aspect-oriented requirements engineering and the problem frames approach implement this principle. Therefore, we propose a combination of both, the AORE4PF (Aspect-Oriented Requirements Engineering for Problem Frames) method. AORE4PF provides guidance for classifying requirements, separating the different concerns, modeling requirements for documentation and application of completeness and interaction analyses, and weaving the reusable parts to a complete and coherent system. AORE4PF provides tool support for most activities. We exemplify our method using a smart grid case obtained from the NESSoS project. For validation, the results of a small experiment in the field of crisis management systems are presented.

References

  1. Alebrahim, A., Choppy, C., Faßbender, S., and Heisel, M. (2014a). Optimizing functional and quality requirements according to stakeholders' goals. In System Quality and Software Architecture. Elsevier. to appear.
  2. Alebrahim, A., Faßbender, S., Heisel, M., and Meis, R. (2014b). Problem-based requirements interaction analysis. In Requirements Engineering: Foundation for Software Quality, volume 8396 of LNCS, pages 200-215. Springer.
  3. Alrajeh, D., Kramer, J., Russo, A., and Uchitel, S. (2009). Learning operational requirements from goal models. In IEEE 31st International Conference on Software Engineering, pages 265-275. IEEE Computer Society.
  4. Baniassad, E. and Clarke, S. (2004). Finding aspects in requirements with Theme/Doc. In Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design, pages 15-22. http://trese.cs.utwente.nl/workshops/early-aspects2004/workshop papers.htm.
  5. Beckers, K., Faßbender, S., Heisel, M., and Meis, R. (2014). A problem-based approach for computer aided privacy threat identification. In Privacy Technologies and Policy, volume 8319 of LNCS, pages 1- 16. Springer.
  6. Beckers, K., Faßbender, S., Heisel, M., and Paci, F. (2013). Combining goal-oriented and problem-oriented requirements engineering methods. In Availability, Reliability, and Security in Information Systems and HCI, volume 8127 of LNCS, pages 178-194. Springer.
  7. Boehm, B. W. and Papaccio, P. N. (1988). Understanding and controlling software costs. IEEE Transactions on Software Engineering, 14(10):1462-1477.
  8. Cavusoglu, H., Mishra, B., and Raghunathan, S. (2004). The effect of internet security breach announcements on market value: Capital market reactions for breached firms and internet security developers. International Journal of Electronic Commerce, 9(1):70- 104.
  9. Conejero, J. M., Hernandez, J., Jurado, E., and van den Berg, K. (2010). Mining early aspects based on syntactical and dependency analyses. Science of Computer Programming, 75(11).
  10. Coˆté, I., Hatebur, D., Heisel, M., and Schmidt, H. (2011). UML4PF - a tool for problem-oriented requirements analysis. In Proceedings of the 19th IEEE International Requirements Engineering Conference, pages 349-350. IEEE Computer Society.
  11. Faßbender, S. and Heisel, M. (2013). From problems to laws in requirements engineering using modeltransformation. In ICSOFT 7813, pages 447-458. SciTePress.
  12. Faßbender, S., Heisel, M., and Meis, R. (2014). Functional requirements under security pressure. In ICSOFT 7814. SciTePress. to appear.
  13. Firesmith, D. (2003). Specifying good requirements. Journal of Object Technology, 2(4):77-87. http://www.jot.fm/issues/issue 2003 07/column7.
  14. Grundy, J. C. (1999). Aspect-oriented requirements engineering for component-based software systems. In Proceedings of the IEEE International Symposium on Requirements Engineering, pages 84-91, Washington, DC, USA. IEEE Computer Society.
  15. Hatebur, D. and Heisel, M. (2010). A UML profile for requirements analysis of dependable software. In Computer Safety, Reliability, and Security, volume 6351 of LNCS, pages 317-331. Springer.
  16. Hofmann, H. and Lehner, F. (2001). Requirements engineering as a success factor in software projects. IEEE Software, 18(4):58-66.
  17. Jackson, M. (2001). Problem Frames. Analyzing and structuring software development problems. AddisonWesley.
  18. Jackson, M. and Zave, P. (1995). Deriving specifications from requirements: an example. In ICSE, USA, pages 15-24. ACM Press.
  19. Jacobson, I. and Ng, P.-W. (2004). Aspect-Oriented Software Development with Use Cases. Addison-Wesley Professional.
  20. Khansa, L., Cook, D. F., James, T., and Bruyaka, O. (2012). Impact of HIPAA provisions on the stock market value of healthcare institutions, and information security and other information technology firms. Computers & Security, 31(6):750 - 770.
  21. Kienzle, J., Guelfi, N., and Mustafiz, S. (2010). Crisis management systems: A case study for aspect-oriented modeling. In Katz, S., Mezini, M., and Kienzle, J., editors, Transactions on Aspect-Oriented Software Development VII, volume 6210 of LNCS, pages 1-22. Springer.
  22. Kreutzmann, H., Vollmer, S., Tekampe, N., and Abromeit, A. (2011). Protection profile for the gateway of a smart metering system. Technical report, BSI.
  23. Landuyt, D., Truyen, E., and Joosen, W. (2010). Discovery of stable abstractions for aspect-oriented composition in the car crash management domain. In Transactions on Aspect-Oriented Software Development VII, volume 6210 of LNCS, pages 375-422. Springer.
  24. Lencastre, M., Moreira, A., Araújo, J., and Castro, J. (2008). Aspects composition in problem frames. In Proceedings of the 16th IEEE International Requirements Engineering Conference, pages 343-344. IEEE Computer Society.
  25. Mohammadi, N. G., Alebrahim, A., Weyer, T., Heisel, M., and Pohl, K. (2013). A framework for combining problem frames and goal models to support context analysis during requirements engineering. In Availability, Reliability, and Security in Information Systems and HCI, volume 8127 of LNCS, pages 272-288. Springer.
  26. Moreira, A., Arajo, J., and Rashid, A. (2005). A concernoriented requirements engineering model. In Pastor, O. and Falco e Cunha, J., editors, Advanced Information Systems Engineering, volume 3520 of LNCS, pages 293-308. Springer.
  27. Moser, T., Winkler, D., Heindl, M., and Biffl, S. (2011). Requirements management with semantic technology: An empirical study on automated requirements categorization and conflict analysis. In Advanced Information Systems Engineering, volume 6741 of LNCS, pages 3-17. Springer.
  28. Mussbacher, G., Amyot, D., Araújo, J., and Moreira, A. (2010). Requirements modeling with the aspectoriented user requirements notation (AoURN): A case study. In Transactions on Aspect-Oriented Software Development VII, volume 6210 of LNCS, pages 23- 68. Springer.
  29. OPEN meter project (2009). Requirements of AMI. Technical report, OPEN meter project.
  30. Parnas, D. L. (1972). On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15(12):1053-1058.
  31. Rago, A., Marcos, C., and Diaz-Pace, J. A. (2013). Uncovering quality-attribute concerns in use case specifications via early aspect mining. Requirements Engineering, 18(1):67-84.
  32. Rashid, A. (2008). Aspect-oriented requirements engineering: An introduction. In Proceedings of the 16th IEEE International Requirements Engineering Conference, pages 306-309. IEEE Computer Society.
  33. Sampaio, A., Rashid, A., Chitchyan, R., and Rayson, P. (2007). Ea-miner: Towards automation in aspectoriented requirements engineering. In Transactions on Aspect-Oriented Software Development III, volume 4620 of LNCS, pages 4-39. Springer.
  34. Sutton, Jr., S. M. and Rouvellou, I. (2002). Modeling of software concerns in cosmos. In Proceedings of the 1st International Conference on Aspect-oriented Software Development, AOSD 7802, pages 127-133, New York, NY, USA. ACM.
  35. Whittle, J. and Araujo, J. (2004). Scenario Modelling with Aspects. IEE Proceedings Software, 151(4):157-171.
  36. Willis, R. (1998). Hughes Aircraft's Widespread Deployment of a Continuously Improving Software Process. AD-a358 993. Carnegie-Mellon University.
  37. Yu, Y., Cesar, J., Leite, S. P., and Mylopoulos, J. (2004). From goals to aspects: Discovering aspects from requirements goal models. In Proceedings of the 12th IEEE International Requirements Engineering Conference, pages 38-47. IEEE Computer Society.
Download


Paper Citation


in Harvard Style

Faßbender S., Heisel M. and Meis R. (2014). Aspect-oriented Requirements Engineering with Problem Frames . In Proceedings of the 9th International Conference on Software Paradigm Trends - Volume 1: ICSOFT-PT, (ICSOFT 2014) ISBN 978-989-758-037-6, pages 145-156. DOI: 10.5220/0005001801450156


in Bibtex Style

@conference{icsoft-pt14,
author={Stephan Faßbender and Maritta Heisel and Rene Meis},
title={Aspect-oriented Requirements Engineering with Problem Frames},
booktitle={Proceedings of the 9th International Conference on Software Paradigm Trends - Volume 1: ICSOFT-PT, (ICSOFT 2014)},
year={2014},
pages={145-156},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0005001801450156},
isbn={978-989-758-037-6},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 9th International Conference on Software Paradigm Trends - Volume 1: ICSOFT-PT, (ICSOFT 2014)
TI - Aspect-oriented Requirements Engineering with Problem Frames
SN - 978-989-758-037-6
AU - Faßbender S.
AU - Heisel M.
AU - Meis R.
PY - 2014
SP - 145
EP - 156
DO - 10.5220/0005001801450156