• 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:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Use Cases against Workshop output

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, I just started work on SCEA and as the requirements are changing I have a lot of pressure to finish it before August 1st.. So I pretty much need to get it right the first pass already.

So here is the question.. My background material deals with utilities company, and I have a handful of use cases with descriptions. It seems, however, that Workshop Output, which the use cases are based on, has extra features listed that are not in the use cases.

So I am tempted to drop them and mention in the assumptions part that I scope just current use cases and not the requirements in workshop output.. Since I cannot converse with the client and I feel I should not add use cases without conversing with the client. But I am a bit worried if I am scoping out something that would make me automatically fail.

So here is the question.. Scoping this assignment, are current use cases the proper scope, or should I include more use cases from other requirements? Do I take use cases as processed final list of requirements or should I add more work because the unpurified workshop output listed more? What is your take on this? I tried to do a search but could not find anyone having same problem.

I am tempted to scope out all not in use case scenarios and keep use cases as they are.
 
author & internet detective
Posts: 41860
908
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
You don't need to add use cases. (The only one I added was login.) The level of detail you go into for the provided use cases is much more important than adding stuff they didn't mention.

One thing I did when I wasn't sure about scope is list an assumption like "I asked the client if he wanted X and he said no." This shows I thought about it.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic