Introducing requirements engineering into product development : towards systematic user requirements definition

 |  Login

Show simple item record

dc.contributor Aalto-yliopisto fi
dc.contributor Aalto University en Kauppinen, Marjo 2012-02-17T07:18:47Z 2012-02-17T07:18:47Z 2005-11-18
dc.identifier.isbn 951-22-7923-1
dc.identifier.issn 1795-4584
dc.description.abstract Without knowing the requirements of customers and users, it is difficult to build the right product. Although requirements engineering (RE) is considered a critical activity in product development, the state of RE practices seems to be immature in many organizations. For several years, researchers have tried to understand why so many companies have informal RE processes and why it is so difficult to introduce RE technology into mainstream practice. This thesis investigates how RE can be introduced into organizations that develop market-driven products. The results are based on the experiences gathered from four Finnish organizations that considered it essential to improve their product development processes by investing in RE. To gain a deep understanding of RE process improvement in real product development contexts, we conducted four longitudinal case studies using an action research approach. One of our main findings is that introducing RE into product development appears to involve a cultural change. By this we mean that development personnel need to adopt a new way of thinking and working when defining requirements systematically from the customers' and users' points of view. Furthermore, this cultural change involves such human factors as beliefs, attitudes, motivation, and commitment of development engineers and managers. One way of supporting the cultural change is to define a simple RE process model that links business goals to technical requirements via user needs and user requirements. The purpose of the process model is to give an overview of RE, support communication by providing common terminology, and emphasize the importance of systematic user requirements definition. On the basis of the lessons learned from the four case studies, we also recommend a set of RE practices that support the systematic definition of user requirements. Furthermore, the thesis provides a model of factors that affect organization-wide implementation of RE practices and describes challenges organizations may face when introducing RE into product development. The main conclusion drawn from this work is that changing the perspective from technical requirements to user requirements can be difficult for product development personnel. Furthermore, it can take several years for the cultural change towards systematic user requirements definition to spread throughout the whole product development organization. However, the experiences from the case studies show that the organization-wide adoption of RE practices can be enhanced by offering Just-in-Time training and an RE expert's assistance for development teams when they are defining user requirements for the first time. en
dc.format.extent 104, [56]
dc.format.mimetype application/pdf
dc.language.iso en en
dc.publisher Helsinki University of Technology en
dc.publisher Teknillinen korkeakoulu fi
dc.relation.ispartofseries TKK dissertations en
dc.relation.ispartofseries 15 en
dc.relation.haspart Kauppinen, M. and Kujala, S. (2001) Assessing Requirements Engineering Processes with the REAIMS Model: Lessons Learned. Proceedings of the Eleventh Annual International Symposium of the International Council on Systems Engineering (INCOSE2001), 7 pages in the electronic proceedings. [article1.pdf] © 2001 International Council on Systems Engineering (INCOSE). By permission.
dc.relation.haspart Kauppinen, M., Aaltio, T., and Kujala, S. (2002) Lessons Learned from Applying the Requirements Engineering Good Practice Guide for Process Improvement. Proceedings of the Seventh European Conference on Software Quality (QC2002), Springer-Verlag, pp. 73-81.
dc.relation.haspart Kauppinen, M. and Kujala, S. (2001) Starting Improvement of Requirements Engineering Processes: An Experience Report. Proceedings of the 3rd International Conference on Product Focused Software Process Improvement (Profes2001), Springer-Verlag, pp. 196-209.
dc.relation.haspart Kauppinen, M., Kujala, S., Aaltio, T., and Lehtola, L. (2002) Introducing Requirements Engineering: How to Make a Cultural Change Happen in Practice. Proceedings of the IEEE Joint International Requirements Engineering Conference (RE'02), IEEE Computer Society, pp. 43-51. [article4.pdf] © 2002 IEEE. By permission.
dc.relation.haspart Kauppinen, M., Vartiainen, M., Kontio, J., Kujala, S., and Sulonen, R. (2004) Implementing Requirements Engineering Processes throughout Organizations: Success Factors and Challenges. Information and Software Technology, 46 (14), 937-953. [article5.pdf] © 2004 Elsevier Science. By permission.
dc.subject.other Economics en
dc.title Introducing requirements engineering into product development : towards systematic user requirements definition en
dc.type G5 Artikkeliväitöskirja fi
dc.description.version reviewed en
dc.contributor.department Department of Computer Science and Engineering en
dc.contributor.department Tietotekniikan osasto fi
dc.subject.keyword requirements engineering en
dc.subject.keyword software process improvement en
dc.subject.keyword user requirement en
dc.subject.keyword user need en
dc.subject.keyword action research en
dc.identifier.urn urn:nbn:fi:tkk-005856
dc.type.dcmitype text en
dc.type.ontasot Väitöskirja (artikkeli) fi
dc.type.ontasot Doctoral dissertation (article-based) en
dc.contributor.lab Software Business and Engineering Institute en
dc.contributor.lab Ohjelmistoliiketoiminnan ja -tuotannon laboratorio fi

Files in this item

This item appears in the following Collection(s)

Show simple item record

Search archive

Advanced Search

article-iconSubmit a publication


My Account