NRU :: Browsing by Author "Kasauli, Rashidah"

Browsing by Author "Kasauli, Rashidah"

Now showing 1 - 10 of 10

Adding Value Every Sprint: A Case Study on Large-Scale Continuous Requirements Engineering
(WS on Continuous Requirements Engineering, 2017) Kasauli, Rashidah; Knauss, Eric; Nilsson, Agneta; Klug, Sara
Agile development practices, such as continuous integration and continuous delivery, promise value through shorter time to market and increased exibility. While these practices have been widely adopted in small-scale, they have shown to be challenging to adopt in large-scale, system development. This is often due to a distance between customer and developer in large scale systems, and the need to break down value from the whole system into manageable parts. The notion of value is fundamental for agile methods, especially for practices such as continuous delivery to the customer. However, how value should be handled in development practices is not clearly understood. In this paper, we investigate how the notion of adding value in every sprint has been perceived in a large-scale system development. Based on an exploratory qualitative case study, the outcome shows that it is perceived bene cial by practitioners although it comes at a price and challenges exist.
Agile Islands in a Waterfall Environment: Challenges and Strategies in Automotive
(2020) Kasauli, Rashidah; Knauss, Eric; Nakatumba-Nabende, Joyce; Kanagwa, Benjamin
Driven by the need for faster time-to-market and reduced development lead-time, large-scale systems engineering companies are adopting agile methods in their organizations. This agile transformation is challenging and it is common that adoption starts bottom-up with agile software teams within the context of traditional company structures. This creates the challenge of agile teams working within a documentcentric and plan-driven (or waterfall) environment. While it may be desirable to take the best of both worlds, it is not clear how that can be achieved especially with respect to managing requirements in large-scale systems. This paper presents an exploratory case study focusing on two departments of a large-scale systems engineering company (automotive) that is in the process of company-wide agile adoption. We present challenges that agile teams face while working within a larger plan-driven context and propose potential strategies to mitigate the challenges. Challenges relate to, e.g., development teams not being aware of the high-level requirements, difficulties to manage change of these requirements as well as their relationship to backlog items such as user stories. While we found strategies for solving most of the challenges, they remain abstract and empirical research on their effectiveness is currently lacking
Challenges of Aligning Requirements Engineering and System Testing in Large-Scale Agile: A Multiple Case Study
(IEEE, 2017) Gomes de Oliveira Neto, Francisco; Horkoff, Jennifer; Knauss, Eric; Kasauli, Rashidah; Liebel, Grischa
As agile methods become more pervasive, agile practices are applied to more large-scale systems with a scope that goes beyond pure software. The expansion of agile in these contexts provides benefits, but creates new challenges. Widespread use of agile has changed the way we must think about practices both in Requirements Engineering (RE) and in System Testing (ST). Our experience shows that many challenges in the application of large-scale agile development relate to either RE or ST, and in particular to the alignment between these areas. In this paper we present large-scale agile-related challenges from a multiple case study which relate to REST alignment. We map our challenges to an existing framework for REST alignment, and make an initial attempt to suggest agile RE practices from the literature which may alleviate these challenges. Our results show that the interviewed companies need to first adopt more agile RE practices to enhance REST alignment and then leverage agile testing. Future work will look more towards evaluating these best practices.
Managing Traceability Information Models: Not such a simple task after all?
(IEEE Software, 2020) Maro, Salome; Steghofer, Jan-Philipp; Knauss, Eric; Horkoff, Jennifer; Kasauli, Rashidah; Wohlrab, Rebekka; Lysemose Korsgaard, Jesper; Wartenberg, Florian; Jørgen Strøm, Niels; Alexandersson, Ruben
Practitioners are poorly supported by the scientific literature when managing traceability information models (TIMs), which capture the structure and semantics of trace links. In practice, companies manage their TIMs in very different ways, even in cases where companies share many similarities. We present our findings from an in-depth focus group about TIM management with three different systems engineering companies. We find that the concrete needs of the companies as well as challenges such as scale and workflow integration are not considered by existing scientific work. We thus issue a call-to-arms for the requirements engineering and software and systems traceability communities, the two main communities for traceability research, to refocus their work on these practical problems.
Quality Requirements in Agile as a Knowledge Management Problem: More than Just-in-Time
(IEEE, 2017) Knauss, Eric; Liebel, Grischa; Schneider, Kurt; Horkoff, Jennifer; Kasauli, Rashidah
Just-in-time (JIT) approaches have been suggested for managing non-functional requirements in agile projects. However, many non-functional requirements cannot be raised and met on the spot. In this position paper, we argue that effective JIT engineering of quality requirements depends on a solid foundation of long-term knowledge about all relevant quality requirements. We present two examples from projects related to safety and security and show that not all aspects of these quality requirements can be invented and changed just in time. Further, managing, for example, operationalization of quality requirements just in time depends on sufficient understanding of (i) customer value and (ii) the system under construction that must be shared by the engineering team. If a Learning Software Organization (LSO) intends to increase agility and speed up system development, it needs a holistic concept for managing this knowledge. We propose that a knowledgemanagement framework can facilitate JIT-RE by structuring, representing, and allowing updates of long-term knowledge about quality requirements. Such a knowledge-management framework should allow to map user value to system requirements and have important properties to allow JIT RE and sustainable evolution.
Requirements engineering challenges and practices in large-scale agile system development
(The Journal of Systems & Software, 2020) Kasauli, Rashidah; Knauss, Eric; Horkoff, Jennifer; Liebel, Grischa; Gomes de Oliveira Neto, Francisco
Agile methods have become mainstream even in large-scale systems engineering companies that need to accommodate different development cycles of hardware and software. For such companies, requirements engineering is an essential activity that involves upfront and detailed analysis which can be at odds with agile development methods. Objective: This paper presents a multiple case study with seven large-scale systems companies, reporting their challenges, together with best practices from industry. We also analyse literature about two popular large-scale agile frameworks, SAFeR and LeSS, to derive potential solutions for the challenges. Method: Our results are based on 20 qualitative interviews, five focus groups, and eight cross-company workshops which we used to both collect and validate our results. Results: We found 24 challenges which we grouped in six themes, then mapped to solutions from SAFeR , LeSS, and our companies, when available. Conclusion: In this way, we contribute a comprehensive overview of RE challenges in relation to large-scale agile system development, evaluate the degree to which they have been addressed, and outline research gaps. We expect these results to be useful for practitioners who are responsible for designing processes, methods, or tools for large scale agile development as well as guidance for researchers
Requirements Engineering Challenges in Large-Scale Agile System Development
(IEEE., 2017) Kasauli, Rashidah; Liebel, Grischa; Knauss, Eric; Gopakumar, Swathi; Kanagwa, Benjamin
Motivated by their success in software development, companies implement agile methods and their practices increasingly for software-intense, large products, such as cars, telecommunication infrastructure, and embedded systems. Such systems are usually subject to safety and regulative concerns as well as different development cycles of hardware and software. Consequently, requirements engineering involves upfront and detailed analysis, which can be at odds with agile (software) development. In this paper, we present results from a multiple case study with two car manufacturers, a telecommunications company, and a technology company that are on the journey to introduce organization wide continuous integration and continuous delivery to customers. Based on 20 qualitative interviews, 5 focus groups, and 2 cross-company workshops, we discuss possible scopes of agile methods within system development, the consequences this has on the role of requirements, and the challenges that arise from the interplay of requirements engineering and agile methods in large-scale system development. These relate in particular to communicating and managing knowledge about a) customer value and b) the system under development. We conclude that better alignment of a holistic requirements model with agile development practices promises rich gains in development speed, flexibility, and overall quality of software and systems.
Requirements Engineering Challenges in Large-Scale Agile System Development
(IEEE, 2017) Kasauli, Rashidah; Liebel, Grischa; Knauss, Eric; Gopakumar, Swathi; Kanagwa, Benjamin
Motivated by their success in software development, companies implement agile methods and their practices increasingly for software-intense, large products, such as cars, telecommunication infrastructure, and embedded systems. Such systems are usually subject to safety and regulative concerns as well as different development cycles of hardware and software. Consequently, requirements engineering involves upfront and detailed analysis, which can be at odds with agile (software) development. In this paper, we present results from a multiple case study with two car manufacturers, a telecommunications company, and a technology company that are on the journey to introduce organization wide continuous integration and continuous delivery to customers. Based on 20 qualitative interviews, 5 focus groups, and 2 cross-company workshops, we discuss possible scopes of agile methods within system development, the consequences this has on the role of requirements, and the challenges that arise from the interplay of requirements engineering and agile methods in large-scale system development. These relate in particular to communicating and managing knowledge about a) customer value and b) the system under development. We conclude that better alignment of a holistic requirements model with agile development practices promises rich gains in development speed, flexibility, and overall quality of software and systems.
Requirements Engineering for Large Scale Agile Systems Development
(REFSQ Workshops, 2017) Kasauli, Rashidah
Agile practices such as continuous integration and delivery promise shorter time to market and improved quality. For this reason, such practices have been adopted in many software companies. In the context of systems development, additional constraints apply, e.g., as a result of scale or parallel development of hardware and software. Traditionally, stage-gate processes with a focus on up-front requirements analysis are common in large-scale systems engineering. However, long upfront analysis is considered anti agile and there is some friction between RE (which is often considered as a waterfall activity or phase) and agile practices. This paper describes a research agenda that plans to address this friction. The work proposes a series of empirical studies to discover the information needs and related knowledge, pertinent to product development. We expect to make a contribution by establishing guidelines and frameworks that can be used to make requirements engineering a foundation for agile systems development.
Safety-Critical Systems and Agile Development: A Mapping Study
(IEEE, 2018) Kasauli, Rashidah; Knauss, Eric; Kanagwa, Benjamin; Nilsson, Agneta; Calikli, Gul
In the last decades, agile methods had a huge impact on how software is developed. In many cases, this has led to significant benefits, such as quality and speed of software deliveries to customers. However, safety-critical systems have widely been dismissed from benefiting from agile methods. Products that include safety critical aspects are therefore faced with a situation in which the development of safety-critical parts can significantly limit the potential speed-up through agile methods, for the full product, but also in the non-safety critical parts. For such products, the ability to develop safety-critical software in an agile way will generate a competitive advantage. In order to enable future research in this important area, we present in this paper a mapping of the current state of practice based on a mixed method approach. Starting from a workshop with experts from six large Swedish product development companies we develop a lens for our analysis. We then present a systematic mapping study on safety-critical systems and agile development through this lens in order to map potential benefits, challenges, and solution candidates for guiding future research.

Browsing by Author "Kasauli, Rashidah"

Results Per Page

Sort Options