Browsing by Author "Airaksinen, Risto"

Now showing 1 - 2 of 2
  • No Thumbnail Available
    Item
    Pintaliitostekniikkaan siirtymisjärjestelyt yrityksissä
    (1990) Airaksinen, Risto; Sähkötekniikan osasto; Teknillinen korkeakoulu; Helsinki University of Technology; Jääskeläinen, Paavo
  • No Thumbnail Available
    Item
    Requirements engineering and Agile software development
    (2010) Kontro, Elina; Airaksinen, Risto; Informaatio- ja luonnontieteiden tiedekunta; Perustieteiden korkeakoulu; School of Science; Männistö, Tomi
    Requirements engineering is an important part of software development process as it addresses the challenges to find out the relevant requirements to be developed. It also covers issues like managing the changing requirements. Requirements engineering activities are needed no matter is the software development done according to classical waterfall or by using agile methods like Scrum. Though, the formal requirements engineering is easily linked to classical software development. The first chapters of the thesis includes literature review about the definitions of the requirement and requirements engineering, short description based on literature about the agile software development, focusing on Scrum and having a look into requirements engineering practices in Scrum. In this thesis the purpose was to study the status and needs of the requirements engineering practices in real product management and research & development environment in one organization. In addition the purpose was to evaluate have the requirements engineering practices changed after the Serum was taken into use. The case study was conducted using semi-structured theme interviews and fourteen people were interviewed from the chosen groups. The results of the case study are presented in the thesis. The findings in the case study show that in the studied organization requirements engineering is not conducted based on defined process or according to clearly agreed practices. Some requirements engineering activities like documenting the requirements and prioritization of those are in place, but e.g. no common rules exists how the prioritization should be done. Those practices had also changed after Serum was introduced, e.g. the importance of the prioritization had increased. However, based on the interviews the requirements engineering is considered important and the needs of the people does not equal to the status of it. Though requirements engineering process is missing there are two software development processes in use that are affecting the work with requirements and are at least partially conflicting and therefore causing challenges also with requirements. Last chapters of the thesis include evaluation of the results and thesis work from different aspects, conclusions and some suggestion for further studies.