Requirements interdependencies: State of the art and future challenges

Engineering and Managing Software Requirements

Volumn , Issue , 2005, Pages 95-116

  Dahlstedt, Åsa G ^a   Persson, Anne ^a  

^a UNIVERSITY OF SKÖVDE   (Sweden)

Author keywords

Requirement coupling; Requirements dependencies; Requirements interdependencies; Requirements traceability

Indexed keywords

EID: 33846570705     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28244-0_5     Document Type: Chapter

References (39)

1. Briand LC, Labiche Y, O'Sullivan L (2003) Impact analysis and change management of UML models. In: Proceedings of the International Conference on Software Maintenance, Amsterdam, The Netherlands, pp.256-265.
2. Bubenko jr., JA (1993) Extending the scope of information modeling. In: Proceedins of 4th International Workshop on the Deductive Approach to Information Systems and Databases, Department de Llenguatges i Sistemes Informatics, Universitat Politecnica de Catalunya, Report de Recerca LSI/93-25, Barcelona.
3. Bubenko jr JA, Persson A, Stirna J (2001) User guide of the knowledge management approach using enterprise knowledge patterns. Deliverable D3, IST Programme project HyperKnowledge - Hypermedia and Pattern Based Knowledge Management for Smart Organisations, Project no. IST-2000-28401, Dept. of Computer and Systems Sciences, Royal Institute of Technology, Stockholm, Sweden available on http://www.dsv.su.se/~js/ekd-user-guide.html.
4. Carlshamre P, Regnell B (2000) Requirements lifecycle management and release planning in market-driven requirements engineering processes. In: Proceedings of 2nd Inter- national Workshop on the Requirements Engineering Process, Greenwich, London, pp.961-966.
5. Carlshamre P, Sandahl K, Lindvall M, Regnell B, Natt och Dag J (2001) An industrial survey of requirements interdependencies in software product release planning. In: Proceedings of the 5th International Symposium on Requirements Engineering, 27-31 August, Toronto, Canada, pp. 84-91.
6. Curtis B, Krasner H, Iscoe N (1988) A field study of the software design process for large systems. Communications of the ACM, 31(11): 1268-1286.
7. Dahlstedt ÅG (2004) Requirements interdependencies - Towards an understanding of their nature and context of use. Licentiate thesis, Department of Computer and Systems Science, Stockholm University/Royal Institute of Technology, Sweden.
8. Dahlstedt ÅG, Persson A (2003a) Requirements interdependencies - Molding the state of research into a research agenda. In: Proceedings of the 9th International Workshop on Requirements Engineering: Foundation for Software Quality, Klagenfurt/Velden, Austria, pp. 71-80.
9. Dahlstedt ÅG, Persson A (2003b) An overview of requirements interdependency types. http://www.ida.his.se/ida/~asa/ReqInterdependencies.pdf.
10. Davis AM (1990) The analysis and specification of systems and software requirements. Systems and Software Requirements Engineering, IEEE Computer Society Press, pp.119-144.
11. Dömges R, Pohl K (1998) Adapting traceability environment to project-specific needs. Communication of the ACM, 41(12): 54-62.
12. Gotel O (1995) Contribution structures for requirements traceability. PhD Thesis, Department of Computing Imperial College of Science, Technology and Medicine, University of London.
13. Gotel O, Finkelstein A (1994) An analysis of the requirements traceability problem. In: Proceedings of the 1st international Conference on Requirements Engineering, Colorado Springs, Colorado, USA, pp. 94-102.
14. Gotel O, Finkelstein A (1997) Extended requirements traceability: Results of an industrial case study. In: Proceedings of the 3rd International Symposium on Requirements Engineering, Annapolis, MD, IEEE Computer Society Press, pp. 169-178.
15. Grehag Å (2001) Requirements management in a life-cycle perspective - A position paper. In: Proceedings of the 7th International Workshop on Requirements Engineering: Foundation for Software Quality, Interlaken, Switzerland, pp.183-188.
16. IEEE Standard 830 (1984): IEEE guide to software requirements specifications. Institute of Electrical and Electronics Engineers, New York, USA.
17. Jarke M (1998) Requirements tracing. Communication of the ACM, 41(12): 32-36.
18. Johnson WL, Feather MS, Harris DR (1991) Integrating domain knowledge, requirements and specifications. Journal of Systems Integration, 1: 283-320.
19. Kaindl H (1993) The missing link in requirements engineering. ACM SIGSOFT Software Engineering Notes, 18(2): 30-39.
20. Karlsson J, Olsson S, Ryan K (1997) Improved practical support for large-scale requirements prioritization. Requirements Engineering, 2(1): 51-60.
21. Kirkman DP (1998) Requirements decomposition and traceability. Requirements Engineering, 3(2): 107-114.
22. Kotonya G, Sommerville I (1998) Requirements engineering - Processes and techniques, John Wiley & Sons.
23. Maciaszek LA (2001) Requirements analysis and system design - Developing information systems with UML, Addison Wesley.
24. Moran TP, Carroll JM (1996) Design rationale concepts, techniques, and use. Lawrence Erlbaum Associates, Publisher, Mahwah, New Jersey.
25. Natt och Dag J, Regnell B, Carlshamre P, Andersson M, Karlsson J (2002) A feasibility study of automated natural language requirements analysis in market-driven development, Requirements Engineering, 7(1): 20-33.
26. Pohl K (1996) Process-centered requirements engineering, John Wiley & Sons Inc.
27. Ramesh B (1998) Factors influencing requirements traceability practice. Communications of the ACM, 41(12): 37-44.
28. Ramesh B, Dhar V (1992) Supporting systems development by capturing deliberations during requirements engineering, IEEE Transactions on Software Engineering, 18(6): 498-510.
29. Ramesh B, Edwards M (1993) Issues in the development of a requirements traceability model. In: Proceedings of the IEEE International Symposium on Requirements Engineering, San Diego, California, USA, pp. 256-259.
30. Ramesh B, Jarke M (2001) Toward reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(1): 58-93.
31. Ramesh B, Powers T, Stubbs C, Edwards M (1995) Implementing requirements traceability: A case study. In: Proceedings of the 2nd International Symposium on Requirements Engineering, York, England, pp. 89-93.
32. Ramesh B, Stubbs C, Powers T, Edwards M (1997) Requirements traceability: Theory and Practice. Annals of Software Engineering, 3: 397-415.
33. Regnell B, Paech B, Aurum A, Wohlin C, Dutoit A, Natt och Dag J. (2001) Requirements mean decisions! - Research issues for understanding and supporting decisionmaking in requirements engineering. In: Proceedings of 1st Swedish Conference on Software Engineering Research and Practice (SERP'01), October 25-26, Ronneby, Sweden.
34. Robertson S, Robertson J. (1999) Mastering the requirements process, Addison-Wesley.
35. Robinson WN, Pawlowski SD, Volkov V (2003) Requirements interaction management. ACM Computing Surveys, 35(2): 132-190.
36. Sommerville I (1996) Software engineering, Addison-Wesley, UK.
37. von Knethen A, Grund M (2003) QuaTrace: A tool environment for (semi-) automatic impact analysis based on traces. In: Proceedings of the International Conference on Software Maintenance, Amsterdam, The Netherlands, pp. 246-255.
38. von Knethen A, Peach B, Kiedaisch F, Houdek F (2002) Systematic requirements recycling through abstraction and traceability. In: Proceedings of IEEE Joint International Conference on Requirements Engineering, 9-13 September, Essen, Germany, pp.273-281.
39. Yu E (1995) Modeling strategic relationships for process reengineering. Ph.D thesis, Department of Computer Science, University of Toronto, Canada.