Software Architecture Knowledge Management

Vliet, Hans van

doi:10.1109/aswec.2008.4483186

Cited by 21 publications

(14 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This is useful for multiple activities such as building a safety case, or simply communicating information to developers and testers (Kruchten, 2004;Mirakhorli and Cleland-Huang, 2011a;Tang et al, 2007;van Vliet, 2008;.…”

Section: Benefits Of Tracing Nfrsmentioning

confidence: 99%

“…Software architectural knowledge management tools provide support for documenting architecturally significant requirements, the decisions that were made to satisfy those requirements, and the rationale behind those decisions (van Vliet, 2008). Documenting architectural knowledge helps developers and architects maintain existing systems, and can also be used to improve the architectural design of future systems.…”

Section: Knowledge Management Toolsmentioning

confidence: 99%

See 1 more Smart Citation

Software and Systems Traceability

Cleland‐Huang¹,

Gotel²,

Zisman³

2012

130

View full text Add to dashboard Cite

Section: Benefits Of Tracing Nfrsmentioning

confidence: 99%

Section: Knowledge Management Toolsmentioning

confidence: 99%

Software and Systems Traceability

Cleland‐Huang¹,

Gotel²,

Zisman³

2012

130

View full text Add to dashboard Cite

“…The practice describes how functional specifications are produced as a result of this collocated analysis phase with a high-level architecture as input. Based on the similarities between requirements and architecture [32,19], we conjecture that a similar practice is applicable for architectural knowledge management in a GSD setting. We are aware that this practice removes the global aspect in GSD by introducing collocatedness.…”

Section: Collocated High-level Architecture Phasementioning

confidence: 94%

“…The requirements engineering discipline is a well-discussed example of a discipline that becomes challenging in GSD [11,26]. We observe a close resemblance between a set of requirements for a software system and a set of architectural decisions taken for that software system: what one person regards as requirements for a software system, another person may regard as architectural decisions [32]. Furthermore, we conjecture that the same challenges that the requirements engineering discipline faces with GSD hold for architectural knowledge management practices in GSD as well: as with requirements, architectural decisions too need to be communicated across different sites in order to maintain a shared vision of the software system that is designed.…”

Section: Introductionmentioning

confidence: 93%

Towards architectural knowledge management practices for global software development

Clerc¹

2008

Proceedings of the 3rd International Workshop on Sharing and Reusing Architectural Knowledge

View full text Add to dashboard Cite

In the past few years, an increasing interest in architectural knowledge is recognized in the software architecture community. Architectural knowledge is generally regarded as important to guide the development of software systems. With the trend of Global Software Development (GSD), the management of architectural knowledge becomes even more important due to the geographical, temporal, and sociocultural distance innate to GSD. In this paper we build on the requirements engineering discipline to identify practices that can aid in overcoming GSD challenges and assess their applicability for management of architectural knowledge in a GSD setting. We provide a light-weight pattern language that we use to describe architectural knowledge management practices and provide a first validation of these practices from an ongoing case study.

show abstract

“…One of the key inputs needed to design the architecture of a system is software's requirements specifications. Some requirements can also serve as design decisions [20]. Thus, in our approach we use system requirements as an input to the APR.…”

Section: Introductionmentioning

confidence: 99%

Apr

Sharma

Sodhi

2017

Proceedings of the Symposium on Applied Computing

View full text Add to dashboard Cite

This paper proposes Architectural Pattern Recommender (APR) system which helps in such architecture selection process. Main contribution of this work is in replacing the manual effort required to identify and analyse relevant architectural patterns in context of a particular set of software requirements. Key input to APR is a set of architecturally significant use cases concerning the application being developed. Central idea of APR's design is two folds: a) transform the unstructured information about software architecture design into a structured form which is suitable for recognizing textual entailment between a requirement scenario and a potential architectural pattern. b) leverage the rich experiential knowledge embedded in discussions on professional developer support forums such as Stackoverflow to check the sentiment about a design decision. APR makes use of both the above elements to identify a suitable architectural pattern and assess its suitability for a given set of requirements. Efficacy of APR has been evaluated by comparing its recommendations for "ground truth" scenarios (comprising of applications whose architecture is well known).

show abstract

Software Architecture Knowledge Management

Abstract: Abstract

Cited by 21 publications

References 20 publications

Software and Systems Traceability

Software and Systems Traceability

Towards architectural knowledge management practices for global software development

Apr

Contact Info

Product

Resources

About