Agile development processes are adaptive rather than predictive. Therefore, agile processes emphasize operational system code rather than its documentation. To overcome the absence of comprehensive documentation artifacts, agile methods require constant interaction between the system stakeholders. Ironically, however, some traditional documentation artifacts come to support this kind of interaction. In this study, we examine the relationship between software and documentation. We develop an approach that enables incorporating domain documentation to agile development, while keeping the processes adaptive. We also provide a system design that actively uses domain knowledge documentation. These ideas have been applied through the implementation and use of agile documentation support components.
%0 Journal Article
%1 springerlink:10.1007/s00766-010-0113-9
%A Rubin, Eran
%A Rubin, Hillel
%D 2010
%I Springer London
%J Requirements Engineering
%K Domainknowledge Requirementsengineering Conceptualmodeling Agiledocumentation
%P 1--16
%T Supporting agile software development through active documentation
%U 10.1007/s00766-010-0113-9
%X Agile development processes are adaptive rather than predictive. Therefore, agile processes emphasize operational system code rather than its documentation. To overcome the absence of comprehensive documentation artifacts, agile methods require constant interaction between the system stakeholders. Ironically, however, some traditional documentation artifacts come to support this kind of interaction. In this study, we examine the relationship between software and documentation. We develop an approach that enables incorporating domain documentation to agile development, while keeping the processes adaptive. We also provide a system design that actively uses domain knowledge documentation. These ideas have been applied through the implementation and use of agile documentation support components.
@article{springerlink:10.1007/s00766-010-0113-9,
abstract = {Agile development processes are adaptive rather than predictive. Therefore, agile processes emphasize operational system code rather than its documentation. To overcome the absence of comprehensive documentation artifacts, agile methods require constant interaction between the system stakeholders. Ironically, however, some traditional documentation artifacts come to support this kind of interaction. In this study, we examine the relationship between software and documentation. We develop an approach that enables incorporating domain documentation to agile development, while keeping the processes adaptive. We also provide a system design that actively uses domain knowledge documentation. These ideas have been applied through the implementation and use of agile documentation support components.},
added-at = {2010-10-20T08:39:37.000+0200},
affiliation = {Faculty of Technology Management, Holon Institute of Technology, Holon, Israel},
author = {Rubin, Eran and Rubin, Hillel},
biburl = {https://www.bibsonomy.org/bibtex/279d693bd49aeb3a571d016c5e7491b43/lama},
file = {:Rubin,Rubin,SupportingAgileSoftwareDevelopmentThroughActiveDdocumentation.pdf:PDF},
interhash = {d1aa66536c16e43a96f40e68a5336b64},
intrahash = {79d693bd49aeb3a571d016c5e7491b43},
issn = {0947-3602},
journal = {Requirements Engineering},
keyword = {Computer Science},
keywords = {Domainknowledge Requirementsengineering Conceptualmodeling Agiledocumentation},
pages = {1--16},
publisher = {Springer London},
timestamp = {2010-10-20T08:39:37.000+0200},
title = {Supporting agile software development through active documentation},
url = {10.1007/s00766-010-0113-9},
year = 2010
}