Global ETD Search

1	Managing architectural design decision documentation and evolution Che, Meiru 10 February 2015 (has links) Software architecture provides a high-level framework for a software system, and plays an important role in achieving functional and non-functional requirements. Since the year 2004, software architecture has been considered as a set of architectural design decisions (ADDs). However, software architecture is implicit and evolves as the software development process moves forward. The implicitness together with continuous evolution leads to many problems such as architecture drift and erosion as well as high cost reconstruction. Without capturing and managing ADDs, most of existing architectural knowledge evaporates, and reusing and evolving architecture can be difficult. These problems are even more serious in global software development (GSD). This dissertation presents a novel methodology for capturing ADDs during the architecting process and managing the evolution of ADDs to reduce architectural knowledge evaporation. This methodology explicitly documents ADDs using a scenario-based approach, which covers three views of a software architecture, to record architectural knowledge, and incorporates evolution-centered characteristics to manage ADD evolution for reducing architectural knowledge evaporation. Furthermore, the dissertation presents ADD management in the context of GSD to analyze typical ADD management paradigms, and to offer insights on, techniques on, and support for sharing and coordinating ADDs in a GSD setting. This dissertation focuses on both the documentation and the evolution needs for ADDs in localized and global software development. / text Software architecture Architectural design decision Architecture documentation Architecture evolution
2	Scenario-based architectural design decisions documentation and evolution Che, Meiru 30 September 2011 (has links) Software architecture is considered as a set of architectural design decisions. Capturing and representing architectural design decisions during the architecting process is necessary for reducing architectural knowledge evaporation. Moreover, managing the evolution of architectural design decisions helps to maintain consistency between requirements and the deployed system. In this thesis, we create the Triple View Model (TVM) as a general architecture framework for documenting architectural design decisions. The TVM clarifies the notion of architectural design decisions in three different views and covers key features of the architecting process. Based on the TVM, we propose a scenario-based methodology (SceMethod) to manage the documentation and the evolution of architectural design decisions. We also conduct a case study on an industrial project to validate the applicability and the effectiveness of the TVM and the SceMethod. The results show they provide complete documentation on architectural design decisions for creating a system architecture, and well support architecture evolution with changing requirements. / text Architectural design decision Architecture documentation Architecture evolution Scenario Architectural knowledge
3	Improving architecture documentation management with object-oriented tools Florberg, Jack January 2023 (has links) Architectural documentation is crucial in the development process, as it helps developers understand the system’s architecture and make informed decisions. However, conventional documentation methods are often timeconsuming and error-prone since most of the work is done manually. This becomes even more ambiguous whendealing with complex systems and when requirements are prone to changing during the development process. This thesis addresses these challenges by exploring the potential benefits of utilizing object-oriented documentation tools and plugins to improve the efficiency of writing and maintaining architectural documentationwhile also making sure that the conveyed information is sufficient and understandable for junior developers. Moreover, it investigates the possibility of generating an easy-to-maintain context view with the use of metadatato display architectural information. The thesis employs both a qualitative case study as well as a rapid application development (RAD) approach.The case study involves interviewing junior developers to find patterns in what junior developers look for inregards to understanding a system’s architecture. Using the RAD approach, a prototype system is developedthat utilizes DollarDoc to treat documentation components as objects by being able to refer to these objectsfrom one file to another. The result shows how architectural documentation can be designed to effectively communicate critical aspects of the system’s architecture to junior developers by providing a clear overview of its components. Thiscontributes to a better understanding of the system’s functionality and purpose, leading to increased productivity and engagement. By using object-oriented documentation tools, the documentation structure becomesmore maintainable, allowing for automatic updates and reliable information. software architecture documentation software architecture architecture documentation architectural documentation object orientation object orientation object-orientation object oriented oriented object-oriented object-oriented documentation OOD OOP documentation management DollarDoc dollardoc markdown challanges problems arkitektur dokumentation arkitektur dokumentation objekt orientering orienterad dokumentations hantering objekt-orienterad dokumentation dokumentation förbättring. utmaningar problem Software Engineering Programvaruteknik

1

Page generated in 0.1358 seconds