Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!
  • 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
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

system vs. business use case

 
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All ,
Can some one please tell me the difference between a system use case and a business use case? If possible with some example please
Thanks in advance
Regards
Johnson
[edited to give it a more significant subject - Ilja]
[ November 19, 2003: Message edited by: Ilja Preuss ]
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
A business use case, is a simplified, abstract, generalized use case that captures the intentions of a user in a technology and implementation independent manner.
The system use case has many implementation details embedded within it.
 
Ranch Hand
Posts: 260
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Krishna Neeraj:
Hi,
A business use case, is a simplified, abstract, generalized use case that captures the intentions of a user in a technology and implementation independent manner.
The system use case has many implementation details embedded within it.


The business use case tells you what your users want to have built.
U therefore can express your requirements as business usecases.
A system use case is describes the system you are going to build to cater the requirement your user has stated in his business use case.A system use case will therefore include high level implementation details like specific references to UI screens if your system has a user interface.
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It depends entirely on the book you're reading or who you're talking to at the moment. I avoid using the terms because I have no idea what they mean to anyone I'm talking to, which means I'm probably not communicating.
Alistair Cockburn defines five levels of abstraction in use cases. "Sea level" is the "just right" level for requirements analysis. Our team defines it as flows that describe an actor using the system under discussion to accomplish a business goal but with no implementation details like screens, buttons, checkboxes, databases, etc. Above that are "kite" and "cloud" levels. Clouds describe business flows without referencing systems at all. Below are "fish" and "clam" levels that get into implementation details. We like "fish" level docs to describe screens, fields, buttons, etc.
The names are silly, but who says there can be no levity in application development? They are a good mnemonic to remember relative levels of abstraction or detail.
 
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Are business and system use case synonymous with functional and non-functional requirement?
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ashish Pagare:
Are business and system use case synonymous with functional and non-functional requirement?


From the above descriptions I'd think they are not. Why would they?
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A business use case describes a (detailed) business process involving actors and activity steps. There does not have to be any computer-based systems involved here at all. On the other hand, a system use case describes the behaviour and scope of a (computer-based) system. Hence these different kind of use case models have different purposes.
Use case models normally focus on functional requirements, that is what a system should do as a response to user input. Other kinds of models are neccessary to address non-functional requirements.
[ December 04, 2003: Message edited by: Stefan Sorman ]
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I agree with Stefan Sorman. For example in the Petstore example
we can write the Business Use Case as:
customer -> ( purchase pets ) << include >> ( process order )
and system use case as:
OrderProcessingSystem -> ( process order )

Nalla
[ December 04, 2003: Message edited by: Nalla Senthilnathan ]
 
I AM MIGHTY! Especially when I hold this tiny ad:
The trailboss has a kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic