Human factors in developing automated vehicles: A requirements engineering perspective

Automated Vehicle (AV) technology has evolved significantly both in complexity and impact and is expected to ultimately change urban transportation. Due to this evolution, the development of AVs challenges the current state of automotive engineering practice, as automotive companies increasingly include agile ways of working in their plan-driven systems engineering—or even transition completely to scaled-agile approaches. However, it is unclear how knowledge about human factors (HF) and technological knowledge related to the development of AVs can be brought together in a way that effectively supports today\u27s rapid release cycles and agile development approaches. Based on semi-structured interviews with ten experts from industry and two experts from academia, this qualitative, exploratory case study investigates the relationship between HF and AV development. The study reveals relevant properties of agile system development and HF, as well as the implications of these properties for integrating agile work, HF, and requirements engineering. According to the findings, which were evaluated in a workshop with experts from academia and industry, a culture that values HF knowledge in engineering is key. These results promise to improve the integration of HF knowledge into agile development as well as to facilitate HF research impact and time to market

Effective and efficient requirement traceability in the software development and Information Technology industry

Requirements traceability has been identified as a quality factor and a characteristic a system should possess and include as a non-functional requirement. Requirements engineering processes should always include methods and tools of maintaining traces and relationships between requirements and product artefacts. To investigate the extent to which requirements traceability is used in software and information technology projects, a theoretical model of requirements traceability was presented in this research. Five organizations were investigated through semi-structured interviews and their requirements tracing practices were compared with the theoretical model. The extent to which organizations apply requirements traceability practices in their projects differs and as a result they were categorised as inactive, dormant and active users in this research. The advent of agile development methods is one of the major factors affecting requirements traceability practices. Among other recommended areas of further research, there is need for future research to look at how agile development and traditional methods can be implemented together in requirement tracing practices

Agile Testing: Improving the Process : Case Descom

The thesis was assigned by Descom, a marketing and technology company based in Jyväskylä. The aim of the thesis was to research the current state of testing inside the organization, and to improve on the existing processes and practices. The thesis was carried out as a design research (applied action research), because the focus was improving already existing processes inside a company. The theory base contains a wide range of subjects from agile development models, the testing process, and process improvement models to agile testing. Without a solid base of multiple aspects it would have been impossible to understand how the testing works as a process and how it could have been improved. As Descom uses agile development it was necessary to follow the same principles throughout the writing of the thesis and on results. As a result information was provided for the company about the current state of testing procedures at Descom and how to improve the testing and processes in the future. The documentation already existing for testing such as the test plan and test report were updated. New documents such as a process improvement plan based on Critical Testing Processes, test strategy and testing policy were also created. Figures of the testing process, and the processes for all test types in use were created to be used as a visual aid for understanding the testing as whole at Descom.Opinnäytetyön toimeksianto tuli Descomilta, joka on Jyväskylästä lähtöisin oleva markkinointi ja teknologia yritys. Työn tavoitteena oli tutkia testauksen tilaa organisaatiossa ja kehittää olemassa olevia prosesseja ja käytäntöjä. Tutkimusmenetelmäksi valikoitui kehittämistutkimus, koska painotus oli olemassa olevien prosessien kehityksessä yrityksen sisällä. Teoriapohjassa käsiteltiin monia aiheita ketterästä sovelluskehityksestä, testausprosessista ja prosessi kehityksestä aina ketterään testaukseen asti. Ilman kattavaa pohjaa monille osa-alueille, olisi ollut mahdotonta ymmärtää miten testaus toimii prosessina ja miten sitä pystyy kehittämään. Descom toimii ketterän sovelluskehityksen mukaisesti projekteissaan, joten oli tärkeää seurata samoja ketteriä periaatteita läpi opinnäytetyön kirjoittamisen ja tuloksissa. Tuloksena saatiin tietoa yritykselle, siitä miten testaus on toiminut Descomilla ja kuinka testausta ja prosesseja tulisi kehittää tulevaisuudessa. Myös aiemmin olemassa olleet testausdokumentit päivitettiin. Uusina dokumentteina laadittiin suunnitelma prosessikehitykseen, joka perustui Critical Testing Processes –malliin, testausstrategia ja testauspolitiikka. Prosessikuvaus tehtiin kaavioita käyttäen, joilla kuvattiin prosessi kokonaisuutena sekä käytettävät testaustasot

Managing Human Factors and Requirements in Agile Development of Automated Vehicles: An Exploration

Context: Automated Vehicle (AV) technology has evolved significantly incomplexity and impact; it is expected to ultimately change urban transporta-tion. However, research shows that vehicle automation can only live up to thisexpectation if it is defined with human capabilities and limitations in mind.Therefore, it is necessary to bring human factors knowledge to AV developers.Objective: This thesis aims to empirically study how we can effectivelybring the required human factors knowledge into large-scale agile AV develop-ment. The research goals are 1) to explore requirements engineering and humanfactors in agile AV development, 2) to investigate the problems of requirementsengineering, human factors, and agile way of working in AV development, and3) to demonstrate initial solutions to existing problems in agile AV development.Method: We conducted this research in close collaboration with industry,using different empirical methodologies to collect data—including interviews,workshops, and document analysis. To gain in-depth insights, we did a qualita-tive exploratory study to investigate the problem and used a design scienceapproach to develop initial solution in several iterations.Findings and Conclusions: We found that applying human factorsknowledge effectively is one of the key problem areas that need to be solved inagile development of artificial intelligence (AI)-intense systems. This motivatedus to do an in-depth interview study on how to manage human factors knowl-edge during AV development. From our data, we derived a working definitionof human factors for AV development, discovered the relevant properties ofagile and human factors, and defined implications for agile ways of working,managing human factors knowledge, and managing requirements. The designscience approach allowed us to identify challenges related to agile requirementsengineering in three case companies in iterations. Based on these three casestudies, we developed a solution strategy to resolve the RE challenges in agileAV development. Moreover, we derived building blocks and described guide-lines for the creation of a requirements strategy, which should describe howrequirements are structured, how work is organized, and how RE is integratedinto the agile work and feature flow.Future Outlook: In future work, I plan to define a concrete requirementstrategy for human factors knowledge in large-scale agile AV development.It could help establishing clear communication channels and practices forincorporating explicit human factors knowledge into AI-based large-scale agileAV development

Agile Processes in Software Engineering and Extreme Programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, Proceedings

agile software development; lean development; scrum; project management; software developmen

Käyttäjäymmärryksen kasvattaminen suunnittelukäytännöillä ketterissä sovelluskehitysprojekteissa

Modern software development aims to produce valuable digital solutions by benefiting from customer- and user-centred agility. These can be supported by design practices, with which user understanding can be deepened. The goal of this thesis was to study how design practices can help small companies to increase their user understanding in agile software development projects. The empirical study was conducted as an insider action research. In this study, four design practices were tested: semi-structured interviews, user stories, scenarios, and prototyping. The four design practices helped to increase user understanding, by explaining who the users are, why they use the product, and how they use it. Semi-structured interviews helped to discover users’ values and motivations to use the current and future versions of the product. User stories allowed for creative thinking and writing of perceived user needs in a clear sentence. Scenarios described realistic stories of users. The stories gave details of the user, their interactions, circumstances, goals, and environment. Prototyping was used alongside the other three design practices to help the users feel and test the product. Testing the product in real context allowed for spontaneous idea creation for system improvement. The results of this thesis indicate that a small company could use semi-structured interviews, user stories, scenarios, and prototyping to increase user understanding in agile software development projects. Increasing user understanding requires careful selection of design practices. The design practices should provide detailed information about who the users are, what their needs and motivations are, and how they would use a product.Nykyaikainen ohjelmistokehitys pyrkii tuottamaan arvokkaita digitaalisia ratkaisuja hyödyntäen asiakas- ja käyttäjäkeskeistä ketteryyttä. Näitä tukevat suunnittelukäytännöt, joilla syvennetään käyttäjäymmärrystä. Tämän työn tavoitteena oli tutkia, kuinka suunnittelukäytännöt voivat auttaa pieniä yrityksiä kasvattamaan käyttäjäymmärrystä ketterissä ohjelmistokehityksen projekteissa. Empiirinen tutkimus toteutettiin toimintatutkimuksena, jonka toteuttaja oli diplomityön tekijä. Tutkimuksessa testattiin neljää suunnittelukäytäntöä: puolistrukturoituja haastatteluja, käyttäjätarinoita, skenaarioita ja prototypointia. Nämä suunnittelukäytännöt auttoivat käyttäjäymmärryksen kasvattamisessa. Käyttäjäymmärryksellä selitetään tuotteen käyttäjäryhmät, syyt tuotteen käytölle ja kuinka tuotetta käytetään. Puolistrukturoidut haastattelut auttoivat löytämään käyttäjien arvoja ja motivaatioita tuotteen nyky- ja tulevien versioiden käytölle. Käyttäjätarinat sallivat luovaa ajattelua ja havaittujen käyttäjätarpeiden kirjoittamista selkeinä lauseina. Skenaarioilla kuvattiin realistisia tarinoita käyttäjistä. Tarinoissa kuvattiin yksityiskohtaisesti käyttäjät, heidän vuorovaikutukset, olosuhteet, tavoitteet ja ympäristö. Prototypointia käytettiin kolmen muun suunnittelukäytäntöjen ohessa testauksen ja kokeilun tukena. Tuotteen testaus oikeassa kontekstissa mahdollisti spontaanin tuotekehitysideoinnin. Tämän työn tulokset viittaavat siihen, että pienet yritykset voisivat käyttää puolistrukturoituja haastatteluja, käyttäjätarinoita, skenaarioita ja prototypointia käyttäjäymmärryksen kasvattamiseen ketterissä ohjelmistokehitysprojekteissa. Käyttäjäymmärryksen kasvattaminen vaatii käytettävien suunnittelukäytäntöjen huolellista valintaa. Niiden tulee vastata yksityiskohtaisesti siihen, keitä käyttäjät ovat, mitkä ovat heidän tarpeensa ja motivaationsa sekä kuinka he käyttävät tuotetta

An Empirical Study on the Role of Requirement Engineering in Agile Method and Its Impact on Quality

Agile Methods are characterized as flexible and easily adaptable. The need to keep up with multiple high-priority projects and shorter time-to-market demands could explain their increasing popularity. It also raises concerns of whether or not use of these methods jeopardizes quality. Since Agile methods allow for changes throughout the process, they also create probabilities to impact software quality at any time. This thesis examines the process of requirement engineering as performed with Agile method in terms of its similarities and differences to requirement engineering as performed with the more traditional Waterfall method. It compares both approaches from a software quality perspective using a case study of 16 software projects. The main contribution of this work is to bring empirical evidence from real life cases that illustrate how Agile methods significantly impacts software quality, including the potential for a larger number of defects due to poor non-functional requirements elicitation

Maps of Lessons Learnt in Requirements Engineering

Both researchers and practitioners have emphasized the importance of learning from past experiences and its consequential impact on project time, cost, and quality. However, from the survey we conducted of requirements engineering (RE) practitioners, over 70\% of the respondents stated that they seldom use RE lessons in the RE process, though 85\% of these would use such lessons if readily available. Our observation, however, is that RE lessons are scattered, mainly implicitly, in the literature and practice, which obviously, does not help the situation. We, therefore, present ``maps” of RE lessons which would highlight weak (dark) and strong (bright) areas of RE (and hence RE theories). Such maps would thus be: (a) a driver for research to ``light up” the darker areas of RE and (b) a guide for practice to benefit from the brighter areas. To achieve this goal, we populated the maps with over 200 RE lessons elicited from literature and practice using a systematic literature review and survey. The results show that approximately 80\% of the elicited lessons are implicit and that approximately 70\% of the lessons deal with the elicitation, analysis, and specification RE phases only. The RE Lesson Maps, elicited lessons, and the results from populating the maps provide novel scientific groundings for lessons learnt in RE as this topic has not yet been systematically studied in the field

Testing and Improving a Continuous Requirements Risk Profiling Method - A Case Study on Agile Software Projects

As requirements play key role in the success of a software development project, identifying and mitigating requirements related risks becomes an important factor in improving software quality. Still, only few methods are offered for that purpose and little results of the feasibility of such methods in industry are reported. In this thesis, feasibility of one requirements risk management methodology was tested in agile software projects and an improved version of the method proposed. The tested method consists of identifying, prioritizing and resolving risks using predefined checklists, patterns and techniques. The objectives of the study were to gain knowledge do professionals working in agile software projects find the method feasible, are such methods found useful and how the method should be improved so that it could be taken into use in the case company. The study was conducted as an interpretive case study which covered several agile software projects from the case company. The primary data collection method for the study were semi-structured theme-centered interviews, in which the method was tested and evaluated by conducting a requirements risk analysis for each of the case projects. The key selection criteria for the interviewees was participation to requirements work and use of some agile software development methodology. The collected qualitative interview data was analyzed using thematic analysis. Based on the results of this study, it was observed that the tested method helped professionals to identify different type of requirements risks and to prioritize those on high level. The interviewed professionals found the tested method useful and feasible in the agile software projects they were currently working with. However, it was also observed that the resolution proposals provided by the method would still need further development. For researchers, the study provided empirical evidence on the feasibility of the method and several suggestions for further research. For professionals working in industry, the study provided one empirically validated method for managing requirements risk, and encouragement for collecting the existing requirements risk management knowledge and sharing it with corresponding methods and tools.fi=Opinnäytetyö kokotekstinä PDF-muodossa.|en=Thesis fulltext in PDF format.|sv=Lärdomsprov tillgängligt som fulltext i PDF-format