Architectural design and documentation: Waste in agile development?

Prause,; Durdik,

doi:10.1109/icssp.2012.6225956

Cited by 20 publications

(17 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Of all the processes only the altered XP_AD process produced better results for efficiency. This is in keeping with the literature [18] [24] [25] and [34] that indicate that an architectural design provides general direction for the product team by giving an overview of the general project direction. This result may be in support of the upfront architectural design in extreme processing process.…”

Section: Findings and Analysissupporting

confidence: 87%

Sustainable Software Development : A Comparison of Tailored Agile Processes:

Bogle¹,

McNamarah²,

Pyne³

2019

Proceedings of the 17th LACCEI International Multi-Conference for Engineering, Education, and Technology: “Industry, Innovation

View full text Add to dashboard Cite

Agile methods have the potential for cost effective and efficient software development thereby facilitating economic sustainability. A well-defined process is associated with a better quality software product and a sustainable production flow. However, agile processes have their shortcomings such as inadequately detailed user stories and lack of overall (architectural) design. Such shortcomings can affect the effectiveness of the agile process. Using principles of process tailoring, three agile processes are tailored by adding steps that address their weaknesses. The tailored processes once derived were implemented and tested. The results of the controlled case study show that the altered extreme programming resulted in better cost effectiveness and may be a useful angle for enhancing economic sustainability.

show abstract

Section: Findings and Analysissupporting

confidence: 87%

Sustainable Software Development : A Comparison of Tailored Agile Processes:

Bogle¹,

McNamarah²,

Pyne³

2019

Proceedings of the 17th LACCEI International Multi-Conference for Engineering, Education, and Technology: “Industry, Innovation

View full text Add to dashboard Cite

show abstract

“…Related work confirms especially the importance of architecture models and descriptions that can play the role of boundary objects [25]. The importance of architecture models in the automotive domain (and above all when moving to agile in the large) and the need to explicitly document them has been stressed by related work [27,28]. We found that engineers are more motivated to keep prescriptive artifacts updated as they are directly related to other artifacts:…”

Section: Low-level Requirements and Testssupporting

confidence: 54%

“…In the focus group sessions in Companies E and F, several participants stressed the usefulness of the distinction between boundary objects Part. Implications/Relation to Challenges (RQ2) [10,17,18,26,30] Artifacts (RQ1) [9,25,27,28,32] F1: Artifacts are either important to support systemlevel thinking in an organization or are used inside a team. I1: Tool solutions should allow for flexibility with the definition of important artifacts and processes to create, update, and use them.…”

Section: 34mentioning

confidence: 99%

Boundary objects in Agile practices

Wohlrab

Knauss

Larsson

2018

Proceedings of the 2018 International Conference on Software and System Process

View full text Add to dashboard Cite

Automotive companies increasingly include proven agile methods in their plan-driven system development. The adoption of agile methods impacts not only the way individuals collaborate, but also the management of artifacts like requirements, test cases, safety documentation, and models. While practitioners aim to reduce unnecessary documentation, there is a lack of guidance for automotive companies with respect to what artifacts are needed and how to manage them. To close this knowledge gap and create practical guidelines, we conducted a design-science study together with 53 practitioners from six automotive companies. Using interviews, surveys, and focus groups, we analyzed categories of artifacts and practical challenges to create applicable guidelines to collaboratively manage artifacts in agile automotive contexts. Our findings indicate that different practices are required to manage artifacts that are shared among different teams within the company (boundary objects) and those that are relevant within a specific team (locally relevant artifacts). CCS CONCEPTS• Software and its engineering → Software development methods; Agile software development; Documentation; Collaboration in software development; KEYWORDSAgile systems engineering, empirical software engineering, largescale agile, documentation ACM Reference Format: Rebekka Wohlrab, Patrizio Pelliccione, Eric Knauss, and Mats Larsson. 2018.

show abstract

“…() Especially in the transition to large‐scale automotive agile practices, the need to explicitly document the architecture has been proclaimed. () In the questionnaire, 17 respondents indicated in the free‐text field that they see requirements as boundary objects, and six mentioned architecture models. Interface descriptions were mentioned by six participants, and signals specifications/lists and communication databases were mentioned by five of our 31 participants.…”

Section: Resultsmentioning

confidence: 99%

Boundary objects and their use in agile systems engineering

Wohlrab

Knauss

Larsson

2019

J Software Evolu Process

View full text Add to dashboard Cite

Summary Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders and makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design‐science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry.

show abstract

Architectural design and documentation: Waste in agile development?

Cited by 20 publications

References 14 publications

Sustainable Software Development : A Comparison of Tailored Agile Processes:

Sustainable Software Development : A Comparison of Tailored Agile Processes:

Boundary objects in Agile practices

Boundary objects and their use in agile systems engineering

Contact Info

Product

Resources

About