Goal-Oriented Requirements Communication in New Product Development

2008 2nd International Workshop on Software Product Management, ISWPM'08

Volumn , Issue , 2008, Pages 27-34

  Fricker, Samuel ^a   Gorschek, Tony ^b   Glinz, Martin ^a  

^a UNIVERSITY OF ZURICH   (Switzerland)

^b BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

Author keywords

[No Author keywords available]

Indexed keywords

PRODUCT DEVELOPMENT; REQUIREMENTS ENGINEERING;

DEVELOPMENT TEAMS; NEW PRODUCT DEVELOPMENT; NOVEL CONCEPT; PRODUCT DEVELOPMENT ORGANIZATIONS; PRODUCT MANAGEMENT; SHARED RESPONSIBILITY; SPECIFIC KNOWLEDGE; TECHNOLOGICAL ASPECTS;

HUMAN RESOURCE MANAGEMENT;

EID: 64949122330     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/IWSPM.2008.2     Document Type: Conference Paper

References (37)

1. D. Berry, "Formal Methods: The Very Idea. Some Thoughts About Why They Work When They Work", Science of Computer Programming 42 (2002), 11-27.
2. B. Boehm, and R. Turner, Balancing Agility and Discipline: A Guide for the Perplexed, Addison-Wesley, 2004.
3. M. Ciolkowski, O. Laitenberger, and S. Biffl, "Software Reviews: The State of the Practice", IEEE Software 20 (2003), 46-51.
4. P. Clements, R. Kazman, and M. Klein, Evaluating Software Architectures: Methods and Case Studies, Addison-Wesley Professional, 2001.
5. A. Cockburn, Writing Effective Use Cases, Addison-Wesley Professional, 2000.
6. D. Damian, and D. Zowghi, "RE Challenges in Multi-Site Software Development Organisations", Requirements Engineering 8 (2003), pp.149-160.
7. A. Dardenne, S. Fickas, and A. van Lamsweerde, "Goal-Directed Requirements Acquisition", Science of Computer Programming 20 (1991), pp.3-50.
8. A. Davis, "Operational Prototyping: A New Development Approach", IEEE Software 9 (1992), pp.70-78.
9. A. Davis, Software Requirements: Objects, Functions, and States, Prentice Hall PTR, 1993.
10. S. Easterbrook, J. Singer, M.-A. Storey, and D. Damian, "Selecting Empirical Methods for Software Engineering". in: F. Shull, J. Singer, and D. Sjøberg, (Eds.), Guide to Advanced Empirical Software Engineering, Springer, 2008.
11. S. Fricker, M. Glinz, and P. Kolb, "A Case Study on Overcoming the Requirements Tar Pit", Journal of Universal Knowledge Management (J.UKM) 1 (2006), pp.85-98.
12. S. Fricker, T. Gorschek, and P. Myllyperkiö, "Handshaking between Software Projects and Stakeholders Using Implementation Proposals", Intl. Working Conference on Requirements Engineering: Foundation for Software Quality (RefsQ'07), 2007.
13. S. Fricker, and P. Grünbacher, "Negotiation Constellations - Method Selection Framework for Requirements Negotiation", Intl. Working Conference on Requirements Engineering: Foundation for Software Quality (RefsQ'08), 2008.
14. T. Gilb, "Advanced Requirements Specification: Quantifying the Quantitative", PSQT Conference, 1999.
15. M. Glinz, S. Berner, and S. Joos, "Object-Oriented Modeling with ADORA", Information Systems 27 (2002), pp.425-444.
16. J. Goguen, and C. Linde, "Techniques for Requirements Elicitation", IEEE Intl. Symposium on Requirements Engineering (RE'93), 1993.
17. S. Gordon, and J. Bieman, "Rapid Prototyping: Lessons Learned", IEEE Software 12 (1995), pp.85-95.
18. A. Griffin, and J. Hauser, "The Voice of the Customer", Marketing Science 12 (1993), 1-27.
19. A. Griffin, and J. Hauser, "Integrating R&D and Marketing: A Review and Analysis of the Literature", Journal of Product Innovation Management 13 (1996), 191-215.
20. P. Grünbacher, and N. Seyff, "Requirements Negotiation". in: A. Aurum, and C. Wohlin, (Eds.), Engineering and Managing Software Requirements, Springer, 2005, pp.143-162.
21. A. Hickey, and A. Davis, "Elicitation Technique Selection: How Do Experts Do It?" 11th IEEE Intl. Requirements Engineering Conference (RE'03), 2003.
22. IEEE, "IEEE Recommended Practice for Software Requirements Specifications", IEEE Standard 830-1998, 1998.
23. ISO/IEC, "Software Engineering - Product Quality - Part 1: Quality Model", ISO/IEC Standard 9126-1, 2001.
24. G. Klir, Facets of Systems Science, Kluwer Academic / Plenum Publishers, 2001.
25. C. Larman, and V. Basili, "Iterative and Incremental Development: A Brief History", Computer 36 (2003), pp.47-56.
26. S. Lauesen, Software Requirements: Styles & Techniques, Addison-Wesley Professional, 2002.
27. OMG, "Unified Modeling Language (UML) Version 2.1.2", Object Management Group, 2007.
28. P. Ovaska, M. Rossi, and K. Smolander, "Filtering, Negotiating and Shifting in the Understanding of Information System Requirements", Scandinavian Journal of Information Systems 17 (2005), 31-66.
29. B. Paech, J. Dörr, and M. Koehler, "Improving Requirements Engineering Communication in Multiproject Environments", IEEE Software 22 (2005), 40-47.
30. C. Potts, K. Takahashi, and A. Antón, "Inquiry-Based Requirements Analysis", IEEE Software (1994), pp.21-32.
31. B. Regnell, and S. Brinkkemper, "Market-Driven Requirements Engineering for Software Products". in: A. Aurum, and C. Wohlin, (Eds.), Engineering and Managing Software Requirements, Springer, 2005, pp.287-308.
32. C. Rupp, "Requirements and Psychology", IEEE Software(2000), pp.16-18.
33. I. van de Weerd, S. Brinkkemper, R. Nieuwenhuis, J. Versendaal, and L. Bijlsma, "Towards a Reference Framework for Software Product Management", 14th IEEE Intl. Requirements Engineering Conference (RE'06), 2006.
34. A. van Lamsweerde, "Goal-Oriented Requirements Engineering: A Roundtrip from Research to Practice", 5th IEEE Intl. Symp. on Requirements Engineering (RE'01), 2001.
35. J. Wood, and D. Silver, Joint Application Development, Wiley, 1995.
36. R. Yin, Case Study Research: Design and Methods, SAGE Publications, 2003.
37. E. Yu, "Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering", 3rd IEEE Intl. Symposium on Requirements Engineering (RE'97), 1997.