Industrial Implementation of a Documentation Framework for Architectural Decisions

Architecture decisions are often not explicitly documented in practice but reside in the architect's mind as tacit knowledge, even though explicit capturing and documentation of architecture decisions has been associated with a multitude of benefits. As part of a research collaboration with ABB, we developed a tool to document architecture decisions. This tool is an add-in for Enterprise Architect and is an implementation of a viewpoint-based decision documentation framework. To validate the add-in, we conducted an exploratory case study with ABB architects. In the study, we assessed the status quo of architecture decision documentation, identified architects' expectations of the ideal decision documentation tool, and evaluated the new add-in. We found that although awareness of decision documentation is increasing at ABB, several barriers exist that limit the use of decisions in practice. Regarding their ideal tool, architects want a descriptive and efficient approach. Supplemental features like reporting or decision sharing are requested. The new add-in, was well-perceived by the architects. As a result of the study, we propose a clearer separation of problem, outcomes, and alternatives for the decision documentation framework

Knowledge-sharing practices by legal information professionals at Hogan Lovells : law firm in South Africa and England

Knowledge-sharing practices are all the actions aimed at improving the internal flow and use of knowledge within a virtual team. The collective knowledge of team members only becomes powerful if it is shared among those who possess common goals. The main purpose of this study was to explore the knowledge-sharing practices of Hogan Lovells’ virtual team of legal information professionals and establish how these practices could be enhanced in order to provide a superior information service to the firm’s lawyers. Hogan Lovells is a multinational law firm with offices in South Africa and England, and its virtual team of legal information professionals were experiencing challenges in sharing knowledge. The study adopted a qualitative methodology and a case-study research design. Interview guides were used to collect qualitative data from study Participants. Out of the 23 potential interviewees from the London and Johannesburg team who were purposively selected as the target population for the study, the researcher interviewed 14 on reaching the point of saturation. The Participants interviewed were in possession of suitable information related to the objectives of the study. Qualitative data collected were analysed using content analysis; findings were then made from the completed analysis. From the findings, it emerged that there were several gaps in the knowledge-sharing practices. Several enablers to the knowledge-sharing practices by legal information professionals were identified. The study recommended several ways by which the knowledge-sharing practices at Hogan Lovells’ virtual team of legal information professionals may be enhanced, amongst which are: formalising team meetings as a virtual community of practice, stimulating informal peer mentoring, valuing storytelling and regularly conducting After-Action Reviews. In addition to this, the virtual team should use other knowledge-sharing practices, such as brainstorming, subject-matter experts, and face-to-face virtual meetings. The study suggested that additional studies, particularly surveys and quantitative studies, be conducted on other virtual teams of legal information professionals in South Africa in order to explore their knowledge-sharing practices.Information ScienceM. A. (Information Science

Techniques and Practices for Software Architecture Work in Agile Software Development

Since the publishing of Agile Manifesto in 2001, the agile software development has taken the world by storm. Agile software development does not emphasize the importance of software architecture, even though software architecture is often seen as a key factor for achieving the quality goals set for the software system. It has been even said that agile software development and software architecture are a clash of two cultures.In many software projects there is no need to consider software architecture anymore. For example, when designing a mobile application, the ecosystem forces the developer to use certain architecture style provided by the platform. In web development ready-made frameworks and project templates are available offering complete software architecture designs for the application developer.There are still domains and systems where careful architecture design is needed. When developing complex systems or systems with a long lifecycle, diligent software architecture design is a key to avoid massive rework during the development. It cannot be a coincidence that companies developing these kinds of systems struggle with agile software development the most.On the one hand, the goal of this thesis was to study software architecture practices used in agile software development in the industry. On the other hand, the goal was to develop new methods and techniques to support incremental software architecture working practices which can be aligned with agile methods such as Scrum. The study applied case study, interviews and design science as the main research methods.The results show that there are four main ways to carry out software architecture work while using agile methods. Basing on this result, models for aligning software architec-ture knowledge management were developed. These models can be used as guidelines for selecting the appropriate software architecture practices in an organization.As a part of the research work, an architecture knowledge repository was developed for sharing the knowledge in agile projects and for automatic software architecture document generation. Additionally, the results of this study show that by taking a decision-centric approach to software architecture evaluation, the evaluation method can be lightweight enough to make incremental evaluation a viable option. Similarly, existing software architecture evaluation methods can be boosted to fit agile software development by utilizing domain knowledge