Sökning: "Agile software development process"

Visar resultat 16 - 20 av 228 uppsatser innehållade orden Agile software development process.

  1. 16. Kvalitetssäkring i agila team : Hur balanseras kundnytta mot ökad risk för instabil mjukvara?

    Kandidat-uppsats, Umeå universitet/Institutionen för informatik

    Författare :Nils-Ivar Holmgren; Nils Bergström; [2022]
    Nyckelord :agile; agile in large organisations; scrum; quality assurance; software testing; why test software; risks in agile software development; agil; agil i stora organisationer; scrum; kvalitetssäkring; testning av mjukvara; varför vi testar mjukvara; riskhantering i agil mjukvaruutveckling;

    Sammanfattning : Agile software development aims to minimize risk by using a short and iterative process, a test-centric development approach by continuous integration, and test automation. Scrum aims to maximize collaboration and collective responsibility for quality by using a team approach. LÄS MER

  2. 17. Agile Hardware Prototyping : A case study on agility and prototype workshops,obstacles and enablers

    Master-uppsats, KTH/Skolan för industriell teknik och management (ITM)

    Författare :Albin Göransson; Felicia Lindgren; [2022]
    Nyckelord :Agile Hardware Prototyping; Agile Hardware Development; Hardware Prototyping; Prototype Workshop; Agilt Hårdvaruprototypande; Agil Hårdvaruutveckling; Hårdvaruprototyper; Prototypverkstad;

    Sammanfattning : Agile is on the rise. The popular software development practice is making its way over to hardware development and companies are adopting it to reap the benefits. This phenomenon has been investigated to some degree and many companies are still trying to figure out if it is a useful way of working for them or not. LÄS MER

  3. 18. A Tool Prototype Supporting Risk-Based Testing in Agile Embedded Software Development

    Kandidat-uppsats, Mälardalens universitet/Akademin för innovation, design och teknik

    Författare :Saef Jasem; [2022]
    Nyckelord :Risk-Based Testing; Risk Analysis; Qualitative Research; Risk Management Tools; Design Thinking; Riskbaserad Testning; Riskanalys; Kvalitativ forskning; Riskhanteringsverktyg; Designtänkande;

    Sammanfattning : Risk-Based Testing is a testing approach in software development that involves identifying, analyzing, controlling, testing, and reporting risks. The strategy provides several benefits and helps companies control risks and manage them effectively. LÄS MER

  4. 19. A DevOps Approach to the EA Blueprint Architectural Pattern

    Kandidat-uppsats, Linnéuniversitetet/Institutionen för datavetenskap och medieteknik (DM)

    Författare :Susanna Persson; [2022]
    Nyckelord :Software Architectural Patterns; DevOps; Infrastructure as Code; CI CD; Deployment Pipeline; Digital Twin of an Organization; DTO;

    Sammanfattning : In the world of software development, there is an increasing demand for software to keep up with rapid changes in its real-world context. A Resilient Digital Twin of an Organization is a type of software whose purpose is to digitally represent an organization or a component of an organization - as a Digital Twin -, and to keep doing so accurately throughout the real-world organization’s changes - a Resilient Digital Twin. LÄS MER

  5. 20. The impact that the quality of requirements can have on the work and well-being of practitioners in software development. : An interview study

    Magister-uppsats, Blekinge Tekniska Högskola/Institutionen för programvaruteknik

    Författare :Emil Lind; [2022]
    Nyckelord :Requirements analysis; Programming teams; Agile software development; Empirical; Fintech;

    Sammanfattning : Requirements, key artifacts of requirements engineering, are a fundamental part of any software development, used by the different software development roles in their activities, such as designing the interface for a feature, its development, and the creation of test cases made by testers. This study aims to investigate the impact of misalignment in the use, understanding, and intent of requirements between the requirements engineers that create the requirements and other software roles that use them in their work activities and betweendevelopers and testers in their software development and testing activities. LÄS MER