Agile processes enable software development projects to react to rapid changes in the development environment. However, they are often criticized for not creating and maintaining standard documentation such as requirements and design documentation. The lack of documentation can be detrimental for maintaining knowledge, especially in the long run, because there is no explicit medium for communic...

Software developers make various decisions when implementing software. For instance, they decide on how to implement an algorithm most efficiently or in which way to process user input. When code is revisited during maintenance, the underlying decisions need to be understood and possibly adjusted to the current situation. Common documentation approaches like JavaDoc neither cover knowledge rela...

Information and knowledge management were introduced in the engineering field to help product developers avoid "reinventing the wheel". As PDM and DMS systems manage the whole information about a developed product, no software systems for capturing, managing and analysis of the product development processes are available. This information is usually stored only in the mind of the involved engin...

In this chapter we report case studies in two companies to investigate how the use of file-based and ontology-based documentation influences AK retrieval (RQ4). A common approach to SA documentation in industry projects is the use of filebased documents. This approach offers a single-dimensional arrangement of the AK. AK retrieval from file-based documentation is efficient if the organisation o...

Software architectural knowledge (AK) is the integrated representation of the software architecture (SA) of a software-intensive system, the architectural design decisions, and the external context/environment. AK annotation using AK conceptual model is used to recover formal AK from SA documentation, including architecture design as well as the design decisions, rationale, context, and other f...

In the development of embedded systems the context is of vital importance, as embedded systems interact with the context through sensing and actuation. Information about the system’s context is contained within different knowledge sources and must be elicited and negotiated during embedded systems development. Examples for such knowledge sources may be: laws, standards, internal process specifi...

The insurance mediation directive of the EU contributes to the recent regulation of financial services markets in order to improve customer protection. Many financial services providers as well as insurance intermediaries fear expensive documentation overhead. In this paper, we argue that the documentation requirements offer a variety of chances. As neither the directive nor national law explic...

Documentation maintainence is a difficult and costly process. Existing forms of software documentation exist independent from the code it describes. As a result, problems arise when source code evolves since there is no traceability between the documentation and code domains. CodeLink, a semantic wiki designed for code documentation attempts to address this problem. CodeLink provides a platform...

OBJECTIVE We investigate a knowledge-based help system for developers of an integrated clinical information system (CIS). The first objective in the study was to determine the system's ability to answer users' questions effectively. User performance and behavior were studied. The second objective was to evaluate the effect of using questions and answers to augment or replace traditional program...