Comparison of requirements hand-off, analysis, and negotiation: Case study

Proceedings of the 2010 18th IEEE International Requirements Engineering Conference, RE2010

Volumn , Issue , 2010, Pages 167-176

  Fricker, Samuel ^a   Glinz, Martin ^a  

^a UNIVERSITY OF ZURICH   (Switzerland)

Author keywords

Empirical study; Requirements communication; Requirements negotiation; Requirements specification

Indexed keywords

EMPIRICAL STUDIES; HAND OFF; MUTUAL UNDERSTANDING; NEGOTIATION PROCESS; PHASE SOLUTIONS; PRODUCT MANAGEMENT; REQUIREMENTS COMMUNICATION; REQUIREMENTS NEGOTIATION; REQUIREMENTS SPECIFICATIONS; SHARED RESPONSIBILITY; SOFTWARE BUSINESS; SPECIFIC KNOWLEDGE;

PRODUCT DEVELOPMENT; REQUIREMENTS ENGINEERING; SPECIFICATIONS;

RESEARCH AND DEVELOPMENT MANAGEMENT;

EID: 78650369747     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2010.29     Document Type: Conference Paper

References (32)

1. A. Griffin, and J. Hauser, "Integrating R&D and Marketing: A Review and Analysis of the Literature," Journal of Product Innovation Management, vol. 13, pp. 191-215, 1996.
2. C. Ebert, "Software Product Management," Crosstalk, vol. 22, no. 1, pp. 15-19, 2009.
3. I. Sommerville, Software Engineering, 8th ed.: Addison Wesley, 2006.
4. B. Regnell, P. Beremark, and O. Eklundh, "A Market-Driven Requirements Engineering Process: Results from an Industrial Process Improvement Programme," Requirements Engineering, vol. 3, pp. 121-129, 1998.
5. T. Gorschek, and C. Wohlin, "Requirements Abstraction Model,"Requirements Engineering, vol. 11, no. 1, pp. 79-101, 2006.
6. I. van de Weerd, S. Brinkkemper, R. Nieuwenhuis, J. Versendaal, and L. Bijlsma, "Towards a Reference Framework for Software Product Management," in 14th IEEE International Requirements Engineering Conference (RE'06), Minneapolis, 2006.
7. IEEE 830-1998, IEEE Recommended Practice for Software Requirements Specifications, 1998.
8. M. Glinz, S. Berner, and S. Joos, "Object-Oriented Modeling with ADORA," Information Systems, vol. 27, pp. pp.425-444, 2002.
9. OMG, Unified Modeling Language (UML) Version 2.1.2, Object Management Group, 2007.
10. B. Nuseibeh, "Weaving Together Requirements and Architectures," Computer, vol. 34, no. 3, pp. pp.115-117, 2001.
11. S. Fricker, T. Gorschek, and P. Myllyperkiö, "Handshaking between Software Projects and Stakeholders Using Implementation Proposals," in Intl. Working Conference on Requirements Engineering: Foundation for Software Quality (RefsQ'07), Trondheim, Norway, 2007.
12. S. Fricker, T. Gorschek, C. Byman, and A. Schmidle, "Handshaking with Implementation Proposals: Negotiating Requirements Understanding," IEEE Software, vol. 27, no. 2, pp. 72-80, 2010.
13. T. Gorschek, P. Garre, S. Larsson, and C. Wohlin, "Industry Evaluation of the Requirements Abstraction Model," Requirements Engineering, vol. 12, pp. 163-190, 2007.
14. J. Tyree, and A. Akerman, "Architecture Decisions: Demystifying Architecture," IEEE Software, no. March/April 2005, pp. pp.19-26, 2005.
15. P. Kruchten, P. Lago, and H. van Vliet, "Building Up and Reasoning About Architectural Knowledge," in 2nd Intl. Conference on the Quality of Software Architectures (QoSA 2006), Västerås, Sweden, 2006.
16. J. S. van der Ven, A. Jansen, J. Nijhuis, and J. Bosch, "Design Decisions: the Bridge between Rationale and Architecture," Rationale Management in Software Engineering, A. Dutoit, R. McCall, I. Mistrík, B. Paech, eds.: Springer, 2006.
17. P. Kruchten, "An Ontology of Architectural Design Decisions in Software Intensive Systems," in 2nd Groningen Workshop on Software Variability, 2004.
18. R. Yin, Case Study Research: Design and Methods, 3rd ed.: SAGE Publications, 2003.
19. C. Rupp, "Requirements and Psychology," IEEE Software, vol. 19, no. 3, pp. 16-18, 2000.
20. L. Thompson, The Mind and Heart of the Negotiator, 3rd ed.: Prentice Hall, 2004.
21. J. Dick, "Design Traceability," IEEE Software, vol. 22, no. 6, pp. 14-16, 2005.
22. A. Dardenne, S. Fickas, and A. van Lamsweerde, "Goal-Directed Requirements Acquisition," Science of Computer Programming, vol. 20, no. 1, pp. pp.3-50, 1991.
23. O. Gotel, and A. Finkelstein, "An Analysis of the Requirements Traceability Problem," in 1st International Conference on Requirements Engineering (ICRE'94), 1994.
24. N. Medvidovic, P. Grünbacher, A. Egyed, and B. Boehm, "Bridging Models Across the Software Lifecycle," The Journal of Systems and Software, vol. 68, no. 3, pp. 199-215, 2003.
25. A. Van Lamsweerde, "From System Goals to Software Architecture," Formal Methods for Software Architectures, M. Bernardo and P. Inverardi, eds.: Springer, 2003.
26. E. Sikora, M. Daun, and K. Pohl, "Supporting the Consistent Specification of Scenarios across Multiple Abstraction Levels," in 16th International Working Conference on Requirements Engineering: Foundation for Software Quality (RefsQ 2010), Essen, Germany, 2010.
27. A. Chakrabarti, S. Morgenstern, and H. Knaab, "Identification and Application of Requirements and Their Impact on the Design Process: A Protocol Study," Research in Engineering Design, vol. 15, no. 1, pp. 22-39, 2004.
28. P. Grünbacher, and R. Briggs, "Surfacing Tacit Knowledge in Requirements Negotiation: Experiences using EasyWinWin," in 34th Hawaii International Conference on System Sciences, 2001.
29. K. Pohl, "The Three Dimensions of Requirements Engineering," Information Systems, vol. 19, no. 3, pp. 243-258, 1994.
30. A. Davis, S. Overmyer, K. Jordan, J. Caruso, F. Dandashi, A. Dinh, G. Kincaid, G. Ledeboer, P. Reynolds, P. Sitaram, A. Ta, and M. Theofanos, "Identifying and Measuring Quality in a Software Requirements Specification," in 1st International Software Metrics Symposium, 1993.
31. R. Costello, and D.-B. Liu, "Metrics for Requirements Engineering," Journal of Systems and Software, vol. 29, pp. 39-63, 1995.
32. M. Höst, B. Regnell, and C. Wohlin, "Using Students as Subjects - A Comparative Study of Students and Professionals in Lead-Time Impact Assessment," Empirical Software Engineering, vol. 5, pp. 201-214, 2000.