Not logged in. · Lost password · Register

bulsa
Member since May 2011
568 posts
Subject: Technical debt
The capabilities timeline states that for the final release, it is necessary that "Technical debt is clear and adequate". What exactly is meant by that? A list of all open technical issues (or possible future issues)?
Dirk Riehle
Avatar
Member since Sep 2009
296 posts
It means that you have a clear understanding of where you wrote good code and where not and if things went overboard, you fixed. If not, you documented it.

In practical terms, for most, it means the sprint backlog for the last week mostly contains bug fix requests ;-)
http://osr.cs.fau.de
bulsa
Member since May 2011
568 posts
So if github contains open issues for all technical problems that are still not fixed at the final release, this counts as adequate?
Dirk Riehle
Avatar
Member since Sep 2009
296 posts
No.
http://osr.cs.fau.de
bulsa
Member since May 2011
568 posts
Do I understand it correctly then, that this means that there has to be additional documentation that states open problems and their associated risks, as a text file in the repository?

I have looked through all the lecture slides, but the only source of information I could find is the capabilities timeline.
Dirk Riehle
Avatar
Member since Sep 2009
296 posts
Yes, we didn't have an extra class after I was told that Ms Saglietti properly covers documentation.

The way to look at it is this: Imagine, you are given the software + documentation. What would you expect to be able to learn to continue the work? That's good documentation.

We understand that time is limited.
http://osr.cs.fau.de
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Go to forum
Datenschutz | Kontakt
Powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2011 by Yves Goergen