This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
A file called choices.txt that containing pure ASCII (not a word processor format) text describing the significant design choices you made. Detail the problems you perceived, the issues surrounding them, your value judgments, and the decisions that you made. This document should also describe any uncertainties you had regarding the project, and the decisions you made when resolving them.
My goddddd this a lot of things!!! problems, issues surrounding them, judgments and decisions !!!
I've read some simples here in foruns and the just wrote :
I decided generate it......bla bla bla....
So....this is wrong...for me !! or not ?
Maybe somenthing like:
problems: how to deal with pk......
issues : I could ignore it cause...or start 1 bla bla.....or start 0 cause...bla bla bla...Anyway.......
decisions: i decided by bla bla bla.....because.....bla bla
Someone that already passed have some tips ?
As you can see I followed closely the different grading sections. Between brackets the number of points in the section.
My choices.txt was reasonable big (36kb and 519 lines), because I certainly not wanted to forget to mention something The only advice I can give you: don't underestimate it. In my opinion it's the easiest part of the assignment (after the essay exam), because it's just putting down your ideas and decisions, but I wanted to be so complete I almost ran out of time (that's why my assignment was submitted just 45 minutes before I took the essay exam after).
I kept during development a small file where I added some reminders of things I should certainly put in the file, some nice explanations resulting from all the great discussions I had on this forum,... And I decided to keep the same structure as the grading sections, because it seemed to me that such an approach made sense and I think it's easy for the accessor too.