Abstract
[Context & motivation] Specifying requirements and ensuring their quality are critical for the success of software development projects. A variety of practices have been suggested to manage these activities, including specification templates, collaborative workshops, and peer reviews, but few empirical studies exist on their inter-connection. [Question/problem] We studied the lessons learned from integrating these three practices: “what are the problems faced with the use of the three practices?” and “what kind of approach supports the integrated use of the three practices?” [Principal ideas/results] In the Finnish companies included in the study, the key problems with the use of the three practices seemed to be the following: 1) the use of the three practices was typically inadequately established to meet the needs of the particular projects and 2) the requirements were communicated to key participants late and insufficiently. To avoid these types of problems, it was found useful to use the practices in an integrated manner, so that the forms of collaboration between key participants were determined and the appropriate types of practices were selected and tailored in a project-specific way. [Contribution] The paper describes the success factors of the integration. The setup workshop is introduced to support the tailoring and integration of the practices.
Access provided by Autonomous University of Puebla. Download to read the full chapter text
Chapter PDF
Similar content being viewed by others
Keywords
References
Hofmann, H.F., Lehner, F.: Requirements Engineering as a Success Factor in Software Projects. IEEE Software 18(4), 58–66 (2001)
Katasonov, A., Sakkinen, M.: Requirements Quality Control: a Unifying Framework. Requirements Engineering 11(1), 42–57 (2006)
Tsumaki, T., Tamai, T.: Framework for Matching Requirements Elicitation Techniques to Project Characteristics. Software Process Improvement and Practice 11(5), 505–519 (2006)
Fitzgerald, B., Russo, N.L., O’Kane, T.: Software Development Method Tailoring at Motorola. Communications of the ACM 46(4), 64–70 (2003)
Uusitalo, E.J., Komssi, M., Kauppinen, M., Davis, A.M.: Linking Requirements and Testing in Practice. In: Proceedings of the 16th IEEE International Requirements Engineering Conference, pp. 265–270. IEEE CS Press, Barcelona (2008)
IEEE Recommended Practice for Software Requirements Specifications (IEEE Std-830), pp. 207–244 (1998)
Robertson, S., Robertson, J.: Mastering the Requirements Process, 2nd edn. Addison-Wesley, Boston (2006)
Sommerville, I., Sawyer, P.: Requirements Engineering: A Good Practice Guide. Wiley, Chichester (1997)
Davis, A.M.: Just Enough Requirements Management: Where Software Development Meets Marketing. Dorset House Publishing, New York (2005)
Wiegers, K.E.: Software Requirements, 2nd edn. Microsoft Press, Redmond (2003)
Brockmann, R.J.: Where Has the Template Tradition in Computer Documentation Led Us? In: Proceedings of the 2nd Annual International Conference on Systems Documentation, pp. 16–18. ACM, Seattle (1983)
Kaner, C., Bach, J., Pettichord, B.: Lessons Learned from Software Testing–A Context-driven Approach. Wiley, New York (2002)
Power, N., Moynihan, T.: A Theory of Requirements Documentation Situated in Practice? In: Proceedings of the 21st Annual International Conference on Documentation, pp. 86–92. ACM, San Francisco (2003)
Gottesdiener, E.: Requirements by Collaboration: Getting It Right the First Time. IEEE Software 20(2), 52–55 (2003)
Kylmäkoski, R.: Efficient Authoring of Software Documentation Using RaPiD7. In: Proceedings of the 25th International Conference on Software Engineering, pp. 255–261. IEEE Computer Society Press, Portland (2003)
Carmel, E., Whitaker, R.D., George, J.F.: PD and Joint Application Design: a Transatlantic Comparison. Communications of the ACM 36(6), 40–48 (1993)
Purvis, R., Sambamurthy, V.: An Examination of Designer and User Perceptions of JAD and the Traditional IS Design Methodology. Information & Management 32(3), 123–135 (1997)
Wood, J., Silver, D.: Joint Application Development, 2nd edn. Wiley, New York (1995)
Davidson, E.J.: Joint Application Design (JAD) in Practice: The Journal of Systems and Software 45(3), 215–223 (1999)
Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Upper Saddle River (2001)
Chrissis, M.B., Konrad, M., Shrum, S.: CMMI: Guidelines for Process Integration and Product Improvement. Addison-Wesley, Boston (2003)
Wiegers, K.E.: Peer Reviews in Software: A Practical Guide. Addison-Wesley, Massachusetts (2001)
Wiegers, K.: When Two Eyes Aren’t Enough. Software Development 9(10), 58–61 (2001)
Avison, D., Lau, F., Myers, M.D., Nielsen, P.A.: Action Research. Communications of the ACM 42(1), 94–97 (1999)
Avison, D.E., Baskerville, R., Myers, M.D.: Controlling Action Research Projects. Information Technology & People 14(1), 28–45 (2001)
Potts, C.: Software-Engineering Research Revisited. IEEE Software 10(5), 19–28 (1993)
Coghlan, D.: Insider Action Research Projects: Implications for Practising Managers. Management Learning 32(49), 49–60 (2001)
Gummesson, E.: Qualitative Methods in Management Research, 2nd edn. Sage Publications Inc., Thousand Oaks (2000)
Yin, R.K.: Case Study Research – Design and Methods, 3rd edn. Sage Publications Inc., Thousand Oaks (2003)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Komssi, M., Kauppinen, M., Toro, K., Soikkeli, R., Uusitalo, E. (2010). Lessons Learned from Integrating Specification Templates, Collaborative Workshops, and Peer Reviews. In: Wieringa, R., Persson, A. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2010. Lecture Notes in Computer Science, vol 6182. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-14192-8_16
Download citation
DOI: https://doi.org/10.1007/978-3-642-14192-8_16
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-14191-1
Online ISBN: 978-3-642-14192-8
eBook Packages: Computer ScienceComputer Science (R0)