Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

assumptions

 
Leonardo Penha
Ranch Hand
Posts: 68
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One of the deliverable for the project (part 2) is a list of assumptions made during the process of coming up with the architecture and design.
I have a few questions about this document:
- Should this be sent in HTML format or plain text?
- What kind of assumptions should we list? Can anyone give any examples?
- What if we disagree with the way the use cases were written? Would that be an assumption?
Yo!
Leo
 
Sivasundaram Umapathy
Ranch Hand
Posts: 360
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My answers
1. HTML is the format mentioned by SUN.
2. Anything,which you feel is vital to prove,that your design meets the requirements.It can be the assumptions on untold requirements or possible business flows to something like technological assumptions like xyz technology of J2EE will not be used in my design for so and so reasons.
3.Use cases depict the core business flows which is nothing but the funtional requirements of the system.Hence even if you disagree with it,you still need to implement them in your design.
 
Billy Tsai
Ranch Hand
Posts: 1304
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
for example: assuming that the system doesnt support internationalization.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic