Essays collection 2012
Home Home SK
"documentation"
Macošínec Branislav

Abstract. This work shows why it is important to create documentation. Documentation is generally considered a necessary evil in the software development. My goal is to show that this is may not be good documentation and creating even a supports the process of software development hence the successful completion of the project. Consequently addressed the question: What is a document which contains? This work also shows how agile software development to build the documentation. Later in the document briefly outline what you should be good contains. The paper also addresses the question: Why do people need documentation. Additionally, this document contains the principles of documentation and its breakdown. At the end of the work I deal with documentation describing the distribution areas.


Zachar Radoslav

Abstract. Documentation is text necessary belong to every software product. Each developer or development team has to create their own documentation. Content of the documentation always strongly depends on the size and complexity of the product. It’s lot of time spending on creating documentation guarantees the quality of software? Creating high-quality documentation is not as easy as it may seem. It is very important to know how to reasonably divide the entire development time between the creation of documentation and writing source code.


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict