Abstract
[Context] The ability to address the diverse interests of different stakeholders in a software project in a coherent way is one fundamental software quality. These diverse and maybe conflicting interests are reflected by the requirements of each stakeholder. [Problem] Thus, it is likely that aggregated requirements for a software system contain interactions. To avoid unwanted interactions and improve software quality, we propose a structured method consisting of three phases to find such interactions. [Principal ideas] For our method, we use problem diagrams, which describe requirements in a structured way. The information represented in the problem diagrams is translated into a formal Z model. Then we reduce the number of combinations of requirements, which might conflict. [Contribution] The reduction of requirements interaction candidates is crucial to lower the effort of the in depth interaction analysis. For validation of our method, we use a real-life example in the domain of smart grid.
Part of this work is funded by the German Research Foundation (DFG) under grant number HE3322/4-2 and the EU project Network of Excellence on Engineering Secure Future Internet Software Services and Systems (NESSoS, ICT-2009.1.4 Trustworthy ICT, Grant No. 256980).
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
France, R., Rumpe, B.: Model-driven development of complex software: A research roadmap. In: 2007 Future of Software Engineering, FOSE 2007, pp. 37–54. IEEE Computer Society, Washington, DC (2007)
van Lamsweerde, A., Letier, E., Darimont, R.: Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Trans. Softw. Eng. 24(11), 908–926 (1998)
Sommerville, I., Sawyer, P., Viller, S.: Viewpoints for requirements elicitation: A practical approach. In: Int. Conf. on RE: Putting Requirements Engineering to Practice, pp. 74–81. IEEE Computer Society (1998)
Calder, M., Kolberg, M., Magill, E.H., Reiff-Marganiec, S.: Feature interaction: a critical review and considered forecast. Comput. Netw. 41, 115–141 (2003)
Cameron, E.J., Velthuijsen, H.: Feature interactions in telecommunications systems. Comm. Mag. 31(8), 18–23 (1993)
Robinson, W.N., Pawlowski, S.D., Volkov, V.: Requirements interaction management. ACM Comput. Surv. 35, 132–190 (2003)
Cheng, B.H.C., Atlee, J.M.: Research Directions in Requirements Engineering. In: Future of Software Engineering, FOSE 2007, pp. 285–303. IEEE Computer Society (2007)
Jackson, M.: Problem Frames. Analyzing and structuring software development problems. Addison-Wesley (2001)
Zave, P., Jackson, M.: Four dark corners of requirements engineering. ACM Trans. Softw. Eng. Methodol. 6, 1–30 (1997)
Wordsworth, J.: Software development with Z - a practical approach to formal methods in software engineering. International computer science series. Addison-Wesley (1992)
Spivey, J.M.: The Z notation: a reference manual. Prentice-Hall, Inc., Upper Saddle River (1989), http://spivey.oriel.ox.ac.uk/mike/zrm/zrm.pdf
Hatebur, D., Heisel, M.: A UML profile for requirements analysis of dependable software. In: Schoitsch, E. (ed.) SAFECOMP 2010. LNCS, vol. 6351, pp. 317–331. Springer, Heidelberg (2010)
Heisel, M., Souquières, J.: A heuristic algorithm to detect feature interactions in requirements. In: Language Constructs for Describing Features, pp. 143–162. Springer (2000)
OPEN meter project: Requirements of AMI. Technical report, OPEN meter project (2009)
Côté, I., Hatebur, D., Heisel, M., Schmidt, H.: UML4PF – a tool for problem-oriented requirements analysis. In: Proc. of the Int. Conf. on Requirements Engineering (RE), pp. 349–350. IEEE Computer Society (2011)
Egyed, A., Grunbacher, P.: Identifying requirements conflicts and cooperation: How quality attributes and automated traceability can help. IEEE Softw. 21(6), 50–58 (2004)
Alférez, M., Moreira, A., Kulesza, U., Araújo, J.A., Mateus, R., Amaral, V.: Detecting feature interactions in SPL requirements analysis models. In: Proc. of the 1st Int. Workshop on Feature-Oriented Software Development, FOSD 2009, pp. 117–123. ACM (2009)
Kim, M., Park, S., Sugumaran, V., Yang, H.: Managing requirements conflicts in software product lines: A goal and scenario based approach. Data Knowl. Eng. 61, 417–432 (2007)
Hausmann, J.H., Heckel, R., Taentzer, G.: Detection of conflicting functional requirements in a use case-driven approach: a static analysis technique based on graph transformation. In: Proc. of the 24th Int. Conf. on Software Engineering, ICSE 2002, pp. 105–115. ACM (2002)
Classen, A., Heymans, P., Schobbens, P.-Y.: What’s in a feature: A requirements engineering perspective. In: Fiadeiro, J.L., Inverardi, P. (eds.) FASE 2008. LNCS, vol. 4961, pp. 16–30. Springer, Heidelberg (2008)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Alebrahim, A., Faßbender, S., Heisel, M., Meis, R. (2014). Problem-Based Requirements Interaction Analysis. In: Salinesi, C., van de Weerd, I. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2014. Lecture Notes in Computer Science, vol 8396. Springer, Cham. https://doi.org/10.1007/978-3-319-05843-6_15
Download citation
DOI: https://doi.org/10.1007/978-3-319-05843-6_15
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-05842-9
Online ISBN: 978-3-319-05843-6
eBook Packages: Computer ScienceComputer Science (R0)