Software engineers rely on program documentation as an aid in understanding the functional nature, high-level design, and implementation details of complex applications. Without such documentation, engineers are forced to rely solely on source code. This is a time-consuming and error-prone process, especially when one considers the amount of information assimilation and domain mapping that is required to understand the architecture of a large-scale software system. This paper describes an integrated approach to documenting software systems based on XML. In particular, the paper focuses on the creation and use of specific Document Type Definitions (DTD) that are defined by MSR as a standard for software documentation. MSR is a consortium of several German automotive companies whose goal is to support cooperative development between car manufacturers and their electronic system suppliers. To illustrate the approach, selected aspects of the document creation process for an engine control system are presented.
[1]
Hausi A. Müller,et al.
Personalized information structures
,
1993,
SIGDOC '93.
[2]
Hausi A. Müller,et al.
Structural Redocumentation: A Case Study
,
1995,
IEEE Softw..
[3]
Hausi A. Müller,et al.
Documenting software systems with views
,
1992,
SIGDOC '92.
[4]
Scott R. Tilley,et al.
Documentation for software engineers: what is needed to aid system understanding?
,
2001,
SIGDOC '01.
[5]
K. Beck,et al.
Extreme Programming Explained
,
2002
.
[6]
Hausi A. Müller,et al.
INFO: a simple document annotation facility
,
1991,
SIGDOC '91.
[7]
Kent L. Beck,et al.
Extreme programming explained - embrace change
,
1990
.
[8]
James H. Cross,et al.
Reverse engineering and design recovery: a taxonomy
,
1990,
IEEE Software.