Requirements abstraction model

Requirements Engineering

Volumn 11, Issue 1, 2006, Pages 79-101

  Gorschek, Tony ^a   Wohlin, Claes ^a  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

Author keywords

Market driven product centered continuous requirements engineering; Product management; Product strategy; Requirements abstraction

Indexed keywords

EID: 31044438063     PISSN: 09473602     EISSN: None     Source Type: Journal    
DOI: 10.1007/s00766-005-0020-7     Document Type: Article

References (34)

1. Ruhe G, Greer D (2003) Quantitative studies in software release planning under risk and resource constraints. In: Proceedings of international symposium on empirical software engineering (ISESE), IEEE, Los Alamitos, CA, pp 262-271
2. Butscher SA, Laker M (2000) Market-driven product development. Market Manag 9:48-53
3. I Sommerville (2001) Software engineering. Addison-Wesley, Essex
4. Carlshamre P (2002) Release planning in market-driven software product development: Provoking an understanding. Requirements Eng 7:139-151 10.1007/s007660200010
5. Yeh AC (1992) Requirements engineering support technique (request): A market driven requirements management process. In: Proceedings of the second symposium on assessment of quality software development tools, pp 211-223
6. 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 fifth IEEE international symposium on requirements engineering, IEEE, Los Alamitos, CA, pp 84-92
7. Dahlstedt A, Persson A (2003) Requirements interdependencies-moulding the state of research into a research agenda. In: Ninth international workshop on requirements engineering (REFSQ'03), Klagenfurt/Velden, Austria, pp 71-80
8. Regnell B, Host M, Natt och Dag JBP, Hjelm T (2001) An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software. Requirements Eng 6:51-62 10.1007/ s007660170015
9. Greer D, Ruhe G (2004) Software release planning: An evolutionary and iterative approach. Inf Software Technol 46:243-253 10.1016/ j.infsof.2003.07.002
10. Weber M, Weisbrod J (2003) Requirements engineering in automotive development: Experiences and challenges. IEEE Software 20:16-24 10.1109/ MS.2003.1159025
11. Higgins SA, de Laat M, Gieles PMC (2003) Managing requirements for medical IT products. IEEE Software 20:26-34
12. Potts C (1997) Requirements models in context. In: Proceedings of the third IEEE international symposium on requirements engineering, IEEE, Los Alamitos, CA, pp 102-104
13. Potts C, Hsi I (1997) Abstraction and context in requirements engineering: Toward a synthesis. Ann Software Eng 3:23-61
14. Anton AI (1996) Goal-based requirements analysis. In: Proceedings of the second international conference on requirements engineering, IEEE, Los Alamitos, CA, pp 136-144
15. Kavakli E, Loucopoulos P, Filippidou D (1996) Using scenarios to systematically support goal-directed elaboration for information system requirements. In: Proceedings of IEEE symposium and workshop on engineering of computer-based systems, IEEE, Los Alamitos, CA, pp 308-314
16. Castro J, Kolp M, Mylopoulos J (2002) Towards requirements-driven information systems engineering: The Tropos project. Inf Syst 27:365-389 10.1016/S0306-4379(02)00012-1
17. KE Wiegers, 1999 Software requirements. Microsoft Press, Redmon
18. S Lauesen (2000) Software requirements: Styles and techniques. Samfundslitteratur, Fredriksberg
19. S Robertson, J Robertson, (1999) Mastering the requirements process. Addison-Wesley, Harlow
20. Gorschek T, Wohlin C (2003) Identification of improvement issues using a lightweight triangulation approach (Eurospi'03). In: European software process improvement conference, Verlag der Technischen Universität, Graz, Austria, pp VI.1-VI.14
21. Gorschek T, Wohlin C (2004) Packaging software process improvement issues-a method and a case study. Software Pract Experience 34(14):1311-1344 10.1002/spe.615
22. Sawyer P, Sommerville I, Viller S (1999) Capturing the benefits of requirements engineering. IEEE Software 16:78-85 10.1109/52.754057
23. I Sommerville, P Sawyer, 1999 Requirements engineering: A good practice guide. Wiley, Chichester
24. SL Pfleeger (1998) Software engineering: Theory and practice. Prentice-Hall, London
25. Martin S, Aurum A, Jeffery R, Barbara P (2002) Requirements engineering process models in practice. In: Seventh Australian workshop on requirements engineering (AWRE'02), Melbourne, Australia, pp 141-155
26. Juristo N, Moreno AM, Silva A (2002) Is the European industry moving toward solving requirements engineering problems? IEEE Software 19:70-78 10.1109/MS.2002.1032864
27. Gorschek T, Svahnberg M, Tejle K (2003) Introduction and application of a lightweight requirements engineering process evaluation method. In: Requirements engineering: Foundation for software quality (REFSQ'03), Velden, Austria, pp 101-112
28. Kivisto K (1999) Roles of developers as part of a software process model. In: Proceedings of the 32nd annual Hawaii international conference on systems sciences, IEEE Computer Society, pp 1-19
29. WS Humphrey 2000 Introduction to the team software process. Addison-Wesley, Reading
30. Fritzhanns T, Kudorfer F (2002) Product management assessment-a new approach to optimize the early phases. In: Proceedings of IEEE joint international conference on requirements engineering, IEEE, Los Alamitos, CA, pp 124-134
31. SR Rakitin (2001) Software verification and validation forractitioners and managers. Artech House, Boston
32. DR Lehmann, RS Winer, (2002) Product management. McGraw-Hill, Boston
33. G Kotonya, I Sommerville, (1998) Requirements engineering:pRocesses and techniques. Wiley, New York
34. C Robson (2002) Real world research: A resource for social scientists and practitioner-researchers. Blackwell, Oxford