Use case & use case diagram

Use Cases

Deborah E. Swain, Ph.D.

 

EXAMPLE

 

 

Name:

Provision Service Data on Platform

Owner:

<initials>

Actor:

Service

Administrator

Assets Impacted:

DataManager, Platform

 

Type:

Standalone

DB Identifier:

XXX-YY-001

 

Customer:

All

Scope:

Network

Function:

Configuration

Related Use Cases:

 

Description:

The DataManager provisions Services. The user will be able to create, update and delete data objects. The data can be provisioned for one or more network elements running onthe Platform.

 

Frequency:

Used whenever a Service object needs to be created or updated.  The frequency of operation is dependent upon the Service’s provisioning requirements and the number of DataManager provisioning users.  An example frequency might be 2 transactions per hour per administrator.

 

Precondition(s):

1.             DataManager is running

2.             Service to be provisioned is installed.

3.             Views for the Service are created.

4.             Owners of Service have been defined.

5.             Provisioner (administrator) has login and permissions in DataManager to perform provisioning tasks.

 

Postcondition(s):

Service object data is provisioned on the selected network elements for the Service. 

 

Main Scenario:

1.             Provisioner/Service administrator logs into DataManager via graphical interface.

2.             Provisioner/Service administrator selects the Service Object option.

3.             Provisioner/Service administrator defines the Service Object name to be provisioned.

4.             Provisioner/Service administrator then selects the network elements for which the data needs to be provisioned from the list of available network elements for the selected category. Alternatively, the Provisioner/Service administrator can also choose to use the distribution rules to distribute the data.

5.                    Provisioner/Service administrator then is prompted to select the categories for the feature capability to be provisioned. Provisioner/Service administrator then keys in the data that need to be provisioned. Multiple service object categories and capabilities can be provisioned.

6.             Provisioner/Service administrator scan also select if they want to send to only particular network element. (This may be used when the Provisioner/Service administrator knows one of the NE is out of service)

7.             On completion of creation of one service object request, the Provisioner/Service administrator will be provided option to: 

Ÿ  select particular NE for the provisioning from the NE group (optional)

Ÿ  add more capabilities to the just created service object (optional)

Ÿ  make changes to the data entered for different capabilities (optional)

8.             On completion of creating the data to be provisioned, the user will be prompted to provide:

Ÿ  a work order name, or

Ÿ  let DataManager select a work order name

9.             The user can also select one of the following types of processing for a work order:

Ÿ  Save it for later provisioning

Ÿ  Submit it for immediate processing

Ÿ  Submit it for later processing

10.          A summary of a work order being created is provided.

11.          Provisioner/Service administrators are prompted if they wanted to add more service object requests to the work order.

12.          When submitted for provisioning, the DataManager performs validation of the data provided in the work order.

13.          Upon completion of validation, the DataManager distributes provisioning data to the network elements.

14.              Provisioner/Service administrator can use the work order ID to check the status of the work order from the work order summary page.

 

Extensions:

5a.          One of the service data types could be Flexible Service Logic.

 

12a.        Validation error occurs in a work order:

the user may correct the data entered and re-submit the work order

 

13a.        Distribution to the network element fails:

The DataManager marks the status of the work order as failed.

NOTE: Possible types of failures include:

1)     Platform-DataManager Link failure,

2)     No DataManager communication possible with Platform

3)     Invalid login/password between Platform and DataManager

4)     Missing target Platform directory,

5)     Insufficient disk space on Platform.

The Platform-DataManager corrects the work order and resubmits for provisioning.

 

*a.           User wants to cancel the creation of the service object work order (which can happen at any time during the creation process, i.e., steps 3-8 of the main scenario):

         User chooses cancel operation

        Creation of service object work order is abandoned

 

Variations:

3a.          User can choose to update an existing service object

3b.          User can choose to delete an existing service object

 

Issues/Comments:

1.             DataManager can accept work orders containing service objects to be provisioned from an upstream system. DataManager accepts the request through its well defined CORBA API. DataManager applies the validation rules before starting to distribute it to the network elements.

 

 

Associated Specification Textual Requirements:     ZZZ        

 

 

 

 

 

 

 

 

 

Graphical Example of Scope

 

The figure below provides a visual depiction of an Scope combined with the Actors defined for a particular set of Use Cases.   Actors are identified for each set of Use Cases and there is the flexibility to add Actors as the need arises.

 

 

 

 

 

 

 

 

 

 

UML Use Case Diagram

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

UML Collaboration Diagram

 

 

 

Process

 

  1. Define Problem to be solved.
  2. Determine Scope of system (boundaries, domain, customer/business objectives)
  3. Identify Actors (role or roles relative to system, event analysis: when do actor and scope need to interact, any related goals/mission to consider)
  4. “Discover” the Use Cases
    1. Separate Processes (i.e., any mini-scopes)
    2. Form Use Cases (interaction context, scenarios, structure, i.e., any sub-use cases)
  5. Specify Use Case
    1. Define pre- and post- events
    2. Write primary scenario
    3. Determine logic structure (i.e., any extensions or variations)
    4. Write extensions
    5. Write variations

 

Tips

·         Use Action Statement Format

(time factor or sequence -> actor-> action ->constraints)

·         Number each action sequentially

·         Follow the primary course (separate extensions and variations)

 

 

 

Practical Reference Contacts

 

 

 

 

 

 

 

 

Template

 

 

Name:

 

 

Owner/Author:

 

 

Actor(s):

            Primary  –

 

            Secondary  –

 

 

Systems Impacted:

 

 

Frequency:

 

 

Precondition(s):

1.     ____________________________

2.     ____________________________

3.     ____________________________

 

Postcondition(s):

 

 

Main Scenario:

 

1.     ___________________________________________________________________

 

2.     ___________________________________________________________________

 

3.     ___________________________________________________________________

 

4.     ___________________________________________________________________

 

5.     ___________________________________________________________________

 

6.     ___________________________________________________________________

 

7.     ___________________________________________________________________

 

8.     ___________________________________________________________________

 

9.     ___________________________________________________________________

 

10.  ___________________________________________________________________

 

 

Extensions:

1.     ____________________________

2.     ____________________________

3.     ____________________________

 

 

Variations:

1.     ____________________________

2.     ____________________________

3.     ____________________________

 

Issues/Comments:

1.     ____________________________

2.     ____________________________

3.     ____________________________

           

 

           

 

Use Case Template

 

 

Name:

 

 

Owner/Author:

 

 

Actor(s):

            Primary  –

 

            Secondary  –

 

 

Systems Impacted:

 

 

Frequency:

 

 

Precondition(s):

1.     ____________________________

2.     ____________________________

3.     ____________________________

 

Postcondition(s):

 

 

Main Scenario:

 

1.     ___________________________________________________________________

 

2.     ___________________________________________________________________

 

3.     ___________________________________________________________________

 

4.     ___________________________________________________________________

 

5.     ___________________________________________________________________

 

6.     ___________________________________________________________________

 

7.     ___________________________________________________________________

 

8.     ___________________________________________________________________

 

9.     ___________________________________________________________________

 

10.  ___________________________________________________________________

 

 

Extensions:

1.     ____________________________

2.     ____________________________

3.     ____________________________

 

 

Variations:

1.     ____________________________

2.     ____________________________

3.     ____________________________

 

Issues/Comments:

1.     ____________________________

2.     ____________________________

3.     ____________________________

           

           

 

 

 

Order a unique copy of this paper
(550 words)

Approximate price: $22

Basic features
  • Free title page and bibliography
  • Unlimited revisions
  • Plagiarism-free guarantee
  • Money-back guarantee
  • 24/7 support
On-demand options
  • Writer’s samples
  • Part-by-part delivery
  • Overnight delivery
  • Copies of used sources
  • Expert Proofreading
Paper format
  • 275 words per page
  • 12 pt Arial/Times New Roman
  • Double line spacing
  • Any citation style (APA, MLA, Chicago/Turabian, Harvard)

Our guarantees

We value our customers and so we ensure that what we do is 100% original..
With us you are guaranteed of quality work done by our qualified experts.Your information and everything that you do with us is kept completely confidential.

Money-back guarantee

You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.

Read more

Zero-plagiarism guarantee

The Product ordered is guaranteed to be original. Orders are checked by the most advanced anti-plagiarism software in the market to assure that the Product is 100% original. The Company has a zero tolerance policy for plagiarism.

Read more

Free-revision policy

The Free Revision policy is a courtesy service that the Company provides to help ensure Customer’s total satisfaction with the completed Order. To receive free revision the Company requires that the Customer provide the request within fourteen (14) days from the first completion date and within a period of thirty (30) days for dissertations.

Read more

Privacy policy

The Company is committed to protect the privacy of the Customer and it will never resell or share any of Customer’s personal information, including credit card data, with any third party. All the online transactions are processed through the secure and reliable online payment systems.

Read more

Fair-cooperation guarantee

By placing an order with us, you agree to the service we provide. We will endear to do all that it takes to deliver a comprehensive paper as per your requirements. We also count on your cooperation to ensure that we deliver on this mandate.

Read more

Calculate the price of your order

550 words
We'll send you the first draft for approval by September 11, 2018 at 10:52 AM
Total price:
$26
The price is based on these factors:
Academic level
Number of pages
Urgency