Define Use Case Boundary (Process Notes 2.2.2)


Determine the use case(s) for business events. For each business event:

  • Consider the business opportunities.

  • Review the work knowledge.

Decide the boundary between the product and the actor. For each use case (there might be more than one per business event):

  • Define the actor names.

  • Define the use case name.

  • Define the use case boundary data.

  • Record the product context by adding the use case to a use case diagram.

  • Keep track of which business event name(s) is (are) related to this use case.

If you have more than 15 to 20 use cases, then a use case diagram will be too complex and you will need to draw a leveled use case diagram or create a use case list.

Diagram 2.3. Do Event Reconnaissance





Mastering the Requirements Process
Mastering the Requirements Process (2nd Edition)
ISBN: 0321419499
EAN: 2147483647
Year: 2006
Pages: 371

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net