Software Engineering Education Going Agile pp 99-103

Part of the Progress in IS book series (PROIS)

Documentation During System Development: Maturity Levels for Decision-Making

  • Alexander Rauh
  • Wolfgang Golubski
  • André Pflüger
  • Chris Rupp
Chapter

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 

References

  1. 1.
    Cunningham, Ward (2001): Manifesto for Agile Software Development. Retrieved from http://agilemanifesto.org/, last visited on 2013-07-31.
  2. 2.
    Cherry, K. A. (2007). Forgetting. Retrieved from http://psychology.about.com/od/cognitivepsychology/p/forgetting.htm, last visited on 2015-02-19.
  3. 3.
    Baddeley, Alan (2012): Working Memory: Theories, Models, and Controversies. Department of Psychology, University of York. York. Retrieved from http://sunburst.usd.edu/~schieber/psyc792/workload/Baddeley2012.pdf, last visited on 2013-07-02.
  4. 4.
    Miller, George A. (1955): The Magical Number Seven, Plus or Minus Two Some Limits on Our Capacity for Processing Information. American Psychological Association. Retrieved from http://www.psych.utoronto.ca/users/peterson/psy430s2001/Miller%20GA%20Magical%20Seven%20Psych%20Review%201955.pdf, last visited on 2013-06-28.
  5. 5.
    Federal Republic of Germany (2004): Fundamentals of the V-Modell. Retrieved from http://v-modell.iabg.de/index.php?option=com_docman&task=doc_download&gid=47, last visited on 2015-02-19.
  6. 6.
    Schwaber, Ken; Sutherland, Jeff (2013): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrum.org/Scrum-Guide, last visited on 2014-02-24.
  7. 7.
    IEEE - Institute of Electrical and Electronics Engineers (2013): Software Engineering Body of Knowledge (SWEBOK). v3. Retrieved from http://www.computer.org/portal/web/swebok/home, last visited on 2013-05-25.
  8. 8.
    Pohl, Klaus; Rupp, Chris (2011): Requirements engineering fundamentals. A study guide for the Certified Professional for Requirements Engineering exam: foundation level, IREB compliant. 1st ed. Santa Barbara, CA: Rocky Nook (Rocky Nook computing).Google Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  • Alexander Rauh
    • 1
  • Wolfgang Golubski
    • 1
  • André Pflüger
    • 2
  • Chris Rupp
    • 2
  1. 1.Westsächsische Hochschule Zwickau – University of Applied SciencesZwickauGermany
  2. 2.SOPHIST GmbHNürnbergGermany

Personalised recommendations