Less is more: Architecture documentation for agile development

Hadar, Irit; Sherman, Sofia; Hadar, Ethan; Harrison, John J.

doi:10.1109/chase.2013.6614746

Cited by 25 publications

(11 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Results of the literature review suggest that a great portion of problems arises from one additional essential conflict: requirement of minimalism in agile processes and the need for well-documented architecture in complex systems [49]. Evidences from the industry reveal that, in most cases, architectural documentation is either excessive, or completely absent [55]. Inadequate documentation results in evaporation of architectural information and knowledge [48], poor understanding of the architecture and impaired communication, which leads to chaos and project failure [56].…”

Section: Theoretical Backgroundmentioning

confidence: 99%

“…Tyree and Akerman [58] see the solution in documenting of architectural decisions and their clarifications. Hadar, Sherman, Hadar, and Harrison [55] suggested a template for documenting software architecture that is in line with the agile philosophy and Lean documentation. Eloranta and Koskimies [59] suggest applying the Architecture Knowledge Management (AKM) concept, which they modified and integrated with the Scrum process.…”

Section: Theoretical Backgroundmentioning

confidence: 99%

See 1 more Smart Citation

Traditionalisation of agile processes: Architectural aspects

Matkovic¹,

Maric²,

Tumbas³

et al. 2018

COMSIS J

View full text Add to dashboard Cite

Mechanisms of agile processes, suited for cost reduction and timely reaction to dynamic market changes, have also been recognized as useful in the development of complex software solutions. Recent studies focused on expansion of agile processes point to a viable possibility for coexistence and integration of complementary elements of agile and traditional development. Within the scope of this paper, this phenomenon is referred to as traditionalisation of agile processes. Software architecture modeling is one of the most sensitive issues associated with incorporation of elements of traditional development into agile processes. The goal of this paper was to determine how suitable particular explicit architectural practices are for incorporation into agile development processes. A mixed method research was carried out for this purpose. Qualitative component of the research resulted in identification of explicit architectural practices suitable for application in agile development processes. Their significances were determined by means of the quantitative component, realized in the form of an empirical research. The research confirmed that emergent architecture in agile processes is not sufficient for the development of complex software solutions, and that agile processes need to incorporate certain explicit architecture practices. Research results revealed that the agile community has an affirmative attitude towards the idea of incorporating explicit architectural practices into agile development processes, with overall agreement on the significances of particular explicit architectural practices for the development of architecture of complex software systems.

show abstract

Section: Theoretical Backgroundmentioning

confidence: 99%

Section: Theoretical Backgroundmentioning

confidence: 99%

Traditionalisation of agile processes: Architectural aspects

Matkovic¹,

Maric²,

Tumbas³

et al. 2018

COMSIS J

View full text Add to dashboard Cite

show abstract

“…Os estudos de caso realizados por Hadar et al (2013) em empresas de software mostraram-se eficientes na redução de documentação de projeto. Por outro lado, os estudos de Moe, Aurum e Dybå (2012) e de Drury-Grogan (2014), apresentaram eficiência em compartilhar o conhecimento com os times e em ter equipes auto-organizadas e colocalizadas.…”

Section: Tendências E Oportunidades De Pesquisaunclassified

Gerenciamento Híbrido De Projetos Para Produtos Físicos – Uma Análise Bibliométrica E Sistêmica

Costa¹,

Borsato²,

Bortolaz³

et al. 2017

Blucher Design Proceedings

View full text Add to dashboard Cite

Um dos fatores de sucesso das organizações é o rápido lançamento dos seus produtos no mercado. Partindo desse pressuposto, o Gerenciamento Ágil de projetos surgiu para diminuir o tempo entre a ideia e o lançamento do produto. Vários estudos vêm sendo desenvolvidos para unir as qualidades do Gerenciamento Ágil com o Gerenciamento de Projetos tradicional para aplicação no desenvolvimento de produtos físicos convencionais, tais como tratores e automóveis. Destes estudos surge a questão: é possível aplicar o Gerenciamento Híbrido (i.e. tradicional e ágil) para este tipo de produto fisico? O presente trabalho busca responder essa pergunta, através de uma análise bibliométrica e sistêmica baseada no método ProKnow-C (Knowledge Development Process-Constructivist). Inicialmente foi realizada a etapa de seleção do portfólio bibliográfico representativo do tema de pesquisa. Nesta etapa foram definidos os eixos de pesquisa, as palavras-chave, assim como foram realizadas buscas em bases de dados e filtragens de artigos. Desta forma, foi construído um portfólio bibliográfico composto de 39 artigos alinhados ao tema de pesquisa. Posteriormente foi realizada a etapa de análise bibliométrica, na qual identificou-se a relevância dos periódicos, a relevância dos autores, as principais palavraschave e a evolução do tema de pesquisa nos últimos 5 anos. Finalmente, na etapa de análise sistêmica, foi possível avaliar o conteúdo dos artigos do portfólio a fim de identificar as principais tendências e oportunidades de pesquisa, dentre as quaispode-se destacar: (i) estudo comparativo entre equipes colocalizadas e à distância; (ii) aplicação do modelo híbrido num projeto piloto; (iii) investigar o principal fator de sucesso da Metodologia Ágil aplicada a um modelo híbrido; (iv) participação do cliente ativa do cliente durante os "sprints" identificando os requisitos do produto.

show abstract

“…These requirements are based on several factors, which include the opinion of experts in the eld [13,40,38,21], current standards on architectural documentation [25,24] and the experience of several researchers (including ours) with industrial projects [23,47,39,4]. In our context, ecient means that the documentation process should optimize the use of resources to achieve good quality documentation.…”

Section: Related Workmentioning

confidence: 99%

Producing Just Enough Documentation: An Optimization Approach Applied to the Software Architecture Domain

et al. 2015

View full text Add to dashboard Cite

The Software Architecture is an important asset in a software development process, which serves to share and discuss the main design concerns among the project stakeholders. The architecture must be properly documented (e.g., via a Wiki environment) in order to be eectively used by these stakeholders. However, the process of producing architecture documentation often fails to deliver contents that address the stakeholders' information needs.To address the problem, we argue for a knowledge management strategy in which: (i) architecture documentation is created incrementally; and (ii) its contents are driven by a model of stakeholder preferences. In this work, we present an information optimization approach applied to the architecture documentation domain, derived from an existing documentation method called Views & Beyond. To do so, we dene the Next SAD Version Problem (NSVP) and then provide tool support to assist architects in producing cost-eective documentation. Based on prior work, we perform a sensitivity analysis of the optimization model and develop a robust formulation that takes into account uncertainty in the parameter estimations for NSVP instances, thus improving the outcomes of our documentation assistant.

show abstract

Less is more: Architecture documentation for agile development

Cited by 25 publications

References 10 publications

Traditionalisation of agile processes: Architectural aspects

Traditionalisation of agile processes: Architectural aspects

Gerenciamento Híbrido De Projetos Para Produtos Físicos – Uma Análise Bibliométrica E Sistêmica

Producing Just Enough Documentation: An Optimization Approach Applied to the Software Architecture Domain

Contact Info

Product

Resources

About