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

exam part 2 requirements

 
Peter Bergoff
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,
Very impressed with quality of responses to part 2 exam questions in this forum.
My question concerns the requirements. The requirements seem vague and in some cases purposefully misleading (e.g. a word meaning one thing in one use case and then meaning something different in another use case). Perhaps part of the exam is to untangle the requirements?
Any opinions on how to handle confusing requirements? Is this considered part of the "assumptions"? What would Sun think about modifications to the requirements?
Thanks.
 
W. Walden
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the confusing points are there on purpose, and I think the most important part about handling them is to:
1.) Make a decision on how to handle them. Meaning, don't try to figure out some complex solution for handling all possible cases - which I doubt could be done anyways. Just decide what you think makes the most sense and go with it.
2.) Most importantly, explain in your assumptions and notes why you took the route you did. The assumptions appear to matter a great deal, and what others might consider a bad design could make complete sense if your assumptions give a reasoning for it.
Of course, don't get carried away. I doubt you would make a very good score if your Assumptions said:
1.) It is assumed that funding for this project will be cut before completion of design...
and then turn in blank diagrams.
Good luck.
NOTE: These are just my views on the area. I have not passed this cert yet.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic