Documentation During System Development: Maturity Levels for Decision-Making

Alexander Rauh (), Wolfgang Golubski (), André Pflüger () and Chris Rupp ()
Additional contact information
Alexander Rauh: Westsächsische Hochschule Zwickau – University of Applied Sciences
Wolfgang Golubski: Westsächsische Hochschule Zwickau – University of Applied Sciences
André Pflüger: SOPHIST GmbH
Chris Rupp: SOPHIST GmbH

A chapter in Software Engineering Education Going Agile, 2016, pp 99-103 from Springer

Abstract: Abstract During system development the decision which knowledge needs to be documented is quite difficult to answer. Too much documentation costs a lot of time and money. Too little documentation leads to a lack of information. The following paper describes how members of a project can decide which information need to be documented and for whom. This approach clusters the information within a development project and gives an overview about the involved disciplines and their need for information during system development.

Keywords: Agility; Documentation; Maturity levels; System development (search for similar items in EconPapers)
Date: 2016
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:prochp:978-3-319-29166-6_14

Ordering information: This item can be ordered from
http://www.springer.com/9783319291666

DOI: 10.1007/978-3-319-29166-6_14

Access Statistics for this chapter

More chapters in Progress in IS from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().