Using DITA for documenting software product lines
O Díaz, FI Anfurrutia, J Kortabitarte - … of the 9th ACM symposium on …, 2009 - dl.acm.org
O Díaz, FI Anfurrutia, J Kortabitarte
Proceedings of the 9th ACM symposium on Document engineering, 2009•dl.acm.orgAligning the software process and the documentation process is a recipe for having both
software and documentation in synchrony where changes in software seamlessly ripple
along its documentation counterpart. This paper focuses on documentation for Software
Product Lines (SPLs). A SPL is not intended to build one application, but a number of them:
a product family. In contrast to single-software product development, SPL development is
based on the idea that the distinct products of the family share a significant amount of assets …
software and documentation in synchrony where changes in software seamlessly ripple
along its documentation counterpart. This paper focuses on documentation for Software
Product Lines (SPLs). A SPL is not intended to build one application, but a number of them:
a product family. In contrast to single-software product development, SPL development is
based on the idea that the distinct products of the family share a significant amount of assets …
Aligning the software process and the documentation process is a recipe for having both software and documentation in synchrony where changes in software seamlessly ripple along its documentation counterpart. This paper focuses on documentation for Software Product Lines (SPLs). A SPL is not intended to build one application, but a number of them: a product family. In contrast to single-software product development, SPL development is based on the idea that the distinct products of the family share a significant amount of assets. This forces a change in the software process. Likewise, software documentation development should now mimic their code counterpart: product documentation should also be produced out of a common set of assets. Specifically, the paper shows how DITA process and documents are recasted using a feature-oriented approach, a realization mechanism for SPLs. In so doing, documentation artifacts are produced at the same pace and using similar variability mechanisms that those used for code artifacts. This accounts for three main advantages: uniformity, separation of concerns, and timely and accurate delivery of the documentation.
ACM Digital Library
以上显示的是最相近的搜索结果。 查看全部搜索结果