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

Organization of Assumptions Section

 
giuseppe fanuzzi
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
i'm arranging all the work for upload it, but i've some doubt where to specify use case prerequisites.
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?

Thank you
Giuseppe
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I put general assumptions on the index.html page and diagram specific assumptions under/above each diagram.
 
Rajan Choudhary
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I added a generic assumption link after class, deployment, sequence, component, risk links in index.html.

In addition to that, I kept adding notes all over the places where applicable so easy for the examiner to refer that right on the same page.
 
Rajan Choudhary
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
like minded people think like at the same time
 
Will Myers
Ranch Hand
Posts: 392
Java jQuery Scala
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I added an assumption page that is linked from the index. They were grouped together but in no particular order - I haven't had the result yet so this may cost me!
 
Arnold Reuser
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've separated my list in two dimensions :
* levels of assumptions e.g. business, information, system, ...
* granularity of assumptions e.g. back office component to handle order processing is a coarse grained component

I've used the assumptions paragraph to :
* Introduce coarse grained assumptions
* Provide a list of all assumptions including references e.g. references to artificats like use case specification, business domain model, ...

The rest, of the assumptions, is applied whenever applicable. The reference back to the global list provides the consistent view.
 
giuseppe fanuzzi
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thank you folks!
Surely there is no the perfect way to, but there could be the wrong way ...

Giuseppe
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic