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.
As part of the assignment one should provide a list of assumptions.
Currently I consider an assumption to be something that is not explicitly explained in the requirements document, but was understood in some way.
As such, an assumption can be used to explicitly fill an existing gap in the requirements.
My question is related to the level of detail one should provide :
Is it sufficient to just mention the assumption?
Or should one also provide a detailed reasoning of why one has made the assumption?
Because especially the reasoning can be very time consuming.
about this topic, i have another question: the "assumptions paragraph" is a good place where to specify use case prerequisites? Or is it better add a note in the sequence diagrams? Or create an html file for each sequence diagram where to write the relative prerequisites?
Or all the things?
GiUsEpPe (SCJP, SCWCD, SCBCD, IBM OOAD, SCEA/OCMJEA 5)
Joined: Nov 20, 2003
Your question is related to 'How to document the assumption' instead of 'The level of detail of an assumption.'
Hence, because of separation of concerns, please create a different topic on this. Thanks!