Samir Jahic; Selda Kocacenk MCS-2004:26, pp. 30. TEK/avd. för interaktion och systemdesign, 2004.
There are several methods and models within the areas of software engineering on how to proceed during a software development process. For each of these methods and models there are benefits and drawbacks, depending on how you choose to look at them. A difference of principle between the different models is that they either advocate iterative development or not.
In parts of software engineering one makes use of different methods depending on which is most fitting in a specific situation. There are several methods on how to recieve more qualitative data from the end-users during the requirement collection, but the reappearing pattern is still user centric participation, which means that the user participates more actively in part of or the entire development process. The reason for this is that the user can steer and direct the development in such a way that the user can benefit from the system being developed. The end-user is in fact the one holding all the information on how the future system shall function, knows what has to be computerized and what functions that will facilitate the workload.
What will then happen if one makes use of a modern solution, such as user-centric participation, and integrate it in a problem domain on an elder model such as the waterfall model? In this research, the problem domain has been the requirements collection, since the rest of the model only considers choises regarding what modelling- and programming tools to be used. When requirement collection is in focus one is faced with the choice of several methods to use in this purpose. In this research user-centric participation has been chosen as the requirement collection method. Furthermore, to get a larger perspective on the end-users requirements and wishes, additional four metohods (observation, interview, group-discussion and survey) has been chosen.
The results of this research show that this combination of model and methods has been successful. A close cooperation with the end-users has, in this case, resulted in clear requirements and mutual understanding between system developer and end-user.
Samir Jahic, firstname.lastname@example.org
Selda Kocacenk, email@example.com