• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

SCEA Assignment - The level of detail of an assumption

 
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.


 
author & internet detective
Posts: 41147
848
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unless you feel your assumption is controversial, just listing the assumption is fine. My assumptions were mostly less than ten words long each.
 
Arnold Reuser
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I was considering, to defend an assumption, to introduce a scenario to identify the gap of an assumption.
So it's good to know that just listing the assumption is sufficient.
 
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?

Thank you
Giuseppe
 
Arnold Reuser
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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!
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic