INFO: a simple document annotation facility
SIGDOC '91 Proceedings of the 9th annual international conference on Systems documentation
Documenting software systems with views
SIGDOC '92 Proceedings of the 10th annual international conference on Systems documentation
Personalized information structures
SIGDOC '93 Proceedings of the 11th annual international conference on Systems documentation
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Documentation for software engineers: what is needed to aid system understanding?
SIGDOC '01 Proceedings of the 19th annual international conference on Computer documentation
Reverse Engineering and Design Recovery: A Taxonomy
IEEE Software
Structural Redocumentation: A Case Study
IEEE Software
Automatically connecting documentation to code with rose
Proceedings of the 20th annual international conference on Computer documentation
Proceedings of the 20th annual international conference on Computer documentation
Towards a documentation maturity model
Proceedings of the 21st annual international conference on Documentation
Reuse of software in distributed embedded automotive systems
Proceedings of the 4th ACM international conference on Embedded software
Documenting software systems with views IV: documenting web transaction design with UWAT+
Proceedings of the 22nd annual international conference on Design of communication: The engineering of quality documentation
WikiWiki weaving heterogeneous software artifacts
Proceedings of the 2005 international symposium on Wikis
Using DITA for documenting software product lines
Proceedings of the 9th ACM symposium on Document engineering
Documenting software systems with views VI: lessons learned from 15 years of research & practice
Proceedings of the 27th ACM international conference on Design of communication
Proceedings of the 2013 International Conference on Software and System Process
Hi-index | 0.00 |
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.