Rationale in Development Chat Messages: An Exploratory Study

Chat messages of development teams play an increasingly significant role in software development, having replaced emails in some cases. Chat messages contain information about discussed issues, considered alternatives and argumentation leading to the decisions made during software development. These elements, defined as rationale, are invaluable during software evolution for documenting and reusing development knowledge. Rationale is also essential for coping with changes and for effective maintenance of the software system. However, exploiting the rationale hidden in the chat messages is challenging due to the high volume of unstructured messages covering a wide range of topics. This work presents the results of an exploratory study examining the frequency of rationale in chat messages, the completeness of the available rationale and the potential of automatic techniques for rationale extraction. For this purpose, we apply content analysis and machine learning techniques on more than 8,700 chat messages from three software development projects. Our results show that chat messages are a rich source of rationale and that machine learning is a promising technique for detecting rationale and identifying different rationale elements.Comment: 11 pages, 6 figures. The 14th International Conference on Mining Software Repositories (MSR'17

The use of non-intrusive user logging to capture engineering rationale, knowledge and intent during the product life cycle

Within the context of Life Cycle Engineering it is important that structured engineering information and knowledge are captured at all phases of the product life cycle for future reference. This is especially the case for long life cycle projects which see a large number of engineering decisions made at the early to mid-stages of a product's life cycle that are needed to inform engineering decisions later on in the process. A key aspect of technology management will be the capturing of knowledge through out the product life cycle. Numerous attempts have been made to apply knowledge capture techniques to formalise engineering decision rationale and processes; however, these tend to be associated with substantial overheads on the engineer and the company through cognitive process interruptions and additional costs/time. Indeed, when life cycle deadlines come closer these capturing techniques are abandoned due the need to produce a final solution. This paper describes work carried out for non-intrusively capturing and formalising product life cycle knowledge by demonstrating the automated capture of engineering processes/rationale using user logging via an immersive virtual reality system for cable harness design and assembly planning. Associated post-experimental analyses are described which demonstrate the formalisation of structured design processes and decision representations in the form of IDEF diagrams and structured engineering change information. Potential future research directions involving more thorough logging of users are also outlined

Automated knowledge capture in 2D and 3D design environments

In Life Cycle Engineering, it is vital that the engineering knowledge for the product is captured throughout its life cycle in a formal and structured manner. This will allow the information to be referred to in the future by engineers who did not work on the original design but are wanting to understand the reasons that certain design decisions were made. In the past, attempts were made to try to capture this knowledge by having the engineer record the knowledge manually during a design session. However, this is not only time-consuming but is also disruptive to the creative process. Therefore, the research presented in this paper is concerned with capturing design knowledge automatically using a traditional 2D design environment and also an immersive 3D design environment. The design knowledge is captured by continuously and non-intrusively logging the user during a design session and then storing this output in a structured eXtensible Markup Language (XML) format. Next, the XML data is analysed and the design processes that are involved can be visualised by the automatic generation of IDEF0 diagrams. Using this captured knowledge, it forms the basis of an interactive online assistance system to aid future users who are carrying out a similar design task

Holistic engineering design : a combined synchronous and asynchronous approach

To aid the creation and through-life support of large, complex engineering products, organizations are placing a greater emphasis on constructing complete and accurate records of design activities. Current documentary approaches are not sufficient to capture activities and decisions in their entirety and can lead to organizations revisiting and in some cases reworking design decisions in order to understand previous design episodes. Design activities are undertaken in a variety of modes; many of which are dichotomous, and thus each require separate documentary mechanisms to capture information in an efficient manner. It is possible to identify the modes of learning and transaction to describe whether an activity is aimed at increasing a level of understanding or whether it involves manipulating information to achieve a tangible task. The dichotomy of interest in this paper is that of synchronous and asynchronous working, where engineers may work alternately as part of a group or as individuals and where different forms of record are necessary to adequately capture the processes and rationale employed in each mode. This paper introduces complimentary approaches to achieving richer representations of design activities performed synchronously and asynchronously, and through the undertaking of a design based case study, highlights the benefit of each approach. The resulting records serve to provide a more complete depiction of activities undertaken, and provide positive direction for future co-development of the approaches

Considerations for a design and operations knowledge support system for Space Station Freedom

Engineering and operations of modern engineered systems depend critically upon detailed design and operations knowledge that is accurate and authoritative. A design and operations knowledge support system (DOKSS) is a modern computer-based information system providing knowledge about the creation, evolution, and growth of an engineered system. The purpose of a DOKSS is to provide convenient and effective access to this multifaceted information. The complexity of Space Station Freedom's (SSF's) systems, elements, interfaces, and organizations makes convenient access to design knowledge especially important, when compared to simpler systems. The life cycle length, being 30 or more years, adds a new dimension to space operations, maintenance, and evolution. Provided here is a review and discussion of design knowledge support systems to be delivered and operated as a critical part of the engineered system. A concept of a DOKSS for Space Station Freedom (SSF) is presented. This is followed by a detailed discussion of a DOKSS for the Lyndon B. Johnson Space Center and Work Package-2 portions of SSF

Capturing, using, and managing quality assurance knowledge for shuttle post-MECO flight design

Ascent initialization values used by the Shuttle's onboard computer for nominal and abort mission scenarios are verified by a six degrees of freedom computer simulation. The procedure that the Ascent Post Main Engine Cutoff (Post-MECO) group uses to perform quality assurance (QA) of the simulation is time consuming. Also, the QA data, checklists and associated rationale, though known by the group members, is not sufficiently documented, hindering transfer of knowledge and problem resolution. A new QA procedure which retains the current high level of integrity while reducing the time required to perform QA is needed to support the increasing Shuttle flight rate. Documenting the knowledge is also needed to increase its availability for training and problem resolution. To meet these needs, a knowledge capture process, embedded into the group activities, was initiated to verify the existing QA checks, define new ones, and document all rationale. The resulting checks were automated in a conventional software program to achieve the desired standardization, integrity, and time reduction. A prototype electronic knowledge base was developed with Macintosh's HyperCard to serve as a knowledge capture tool and data storage

Service Knowledge Capture and Reuse

The keynote will start with the need for service knowledge capture and reuse for industrial product-service systems. A novel approach to capture the service damage knowledge about individual component will be presented with experimental results. The technique uses active thermography and image processing approaches for the assessment. The paper will also give an overview of other non-destructive inspection techniques for service damage assessment. A robotic system will be described to automate the damage image capture. The keynote will then propose ways to reuse the knowledge to predict remaining life of the component and feedback to design and manufacturing

A design recording framework to facilitate knowledge sharing in collaborative software engineering

This paper describes an environment that allows a development team to share knowledge about software artefacts by recording decisions and rationales as well as supporting the team in formulating and maintaining design constraints. It explores the use of multi-dimensional design spaces for capturing various issues arising during development and presenting this meta-information using a network of views. It describes a framework to underlie the collaborative environment and shows the supporting architecture and its implementation. It addresses how the artefacts and their meta-information are captured in a non-invasive way and shows how an artefact repository is embedded to store and manage the artefacts

A study of information & knowledge generated during engineering design meetings

During the design process, there is a wealth of information generated, and although it may not be obvious at the time, this information can be extremely useful at a later instance when it may be no longer available. Many information capture solutions utilise tools such as video and media capture, incorporating the idea that if you capture all information then you will not miss anything. However, this creates another problem. Not all the information captured will be useful, therefore how can you distinguish the information that is useful from information that is not? The challenge many organisations face is how to capture and store valuable informal information in a way that is both simple and efficient, whilst remaining unobtrusive to the designers involved and without inhibiting the design activities. Through the undertaking of a series of case studies and test scenarios, it is possible to observe, identify and evaluate the various degrees of information and knowledge being generated and passed amongst design engineering teams whilst performing design activities in meeting situations. Using multi-media recording equipment and observation techniques, insight can be gained into the decision making process design engineering teams encounter during the course of a design project, and thus it is possible to evaluate where improved techniques can be applied to enhance the recording of information for re-use