Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Documenting for Program Comprehension in Agile Software Development
University of Borås, School of Business and IT.
2011 (English)Independent thesis Advanced level (degree of Master (One Year))Student thesis
Abstract [en]

Program comprehension, i.e. to understand from its source code what a computer program does, is crucial for change and maintenance in software development. In this thesis, it is looked for innovative documentation techniques and tools that support program comprehension, but that are also conform to agile values and principles – commonly, documentation is considered critical due to the agile value “working software over comprehensive documentation.”1 First, a research framework is developed that embodies detailed requisites for such techniques and tools. Apart from its internal use for examining techniques and tools subsequently obtained from a literature search, this framework is intended to be likewise employed by software practitioners. Eventually, the findings of a series of survey studies conducted in an industrial software organization for the primary purpose of evaluating the obtained techniques and tools are analyzed. Three innovative techniques that meet all requisites are revealed. These are regarded by practitioners independently from the support of program comprehension as helpful for a change impact analysis conducted by non-developers. Therefore, a requisite deduced from the highest priority in agile software development – customer satisfaction – is met. It says that a technique or tool has to directly induce a benefit for non-developer stakeholders besides the benefits for them which are indirectly induced by the support of program comprehension, e.g. a potentially improved source code quality. Further, the technique most beneficial for developers as well as for non-developers among the three techniques is identified, which bases on design rationales – textual information related to the source code that states the reasons why a part of the program has been implemented in a certain way. Secondarily, the studies revealed that the research framework is difficult to understand for practitioners due to its unstructured form.

Place, publisher, year, edition, pages
University of Borås/School of Business and Informatics , 2011.
Series
Magisteruppsats ; 2010MI11
Keywords [en]
software documentation, source code documentation, program comprehension, program understanding, agile software development
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:hb:diva-20393Local ID: 2320/7977OAI: oai:DiVA.org:hb-20393DiVA, id: diva2:1312327
Note
Program: Magisterutbildning i informatikAvailable from: 2019-04-30 Created: 2019-04-30

Open Access in DiVA

fulltext(1906 kB)7 downloads
File information
File name FULLTEXT01.pdfFile size 1906 kBChecksum SHA-512
9cacf771902ad3d17f1032b35f5867feddadc48e2f014bac8a970a11210a1bbe8e848e6921d1ec93d7c58c1e4fd423c5a751c17332b0c48c683db2451f889ee6
Type fulltextMimetype application/pdf

By organisation
School of Business and IT
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar
Total: 7 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 3 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf