CRUD

Use Case Description

Description

The Creation, Retrieval, Update and Deletion of Email Distribution Lists.  This case is a first draft and is intended for a general audience. The scenarios for the Creation, Retrieval, Update and Delete Use Case share many common elements.  The Create a Distribution List is fully documented and “Other” scenarios will identify how they differ.  An Email system without Distribution Lists is like a Kitchen that you can only make one item at a time

1.0      Revision History

<01/08/00> <GJohnson> <Initial Rev> <>

2.0      Flow of Events for CRUD Distribution Lists Use Case

 

Use Case: CRUD Distribution Lists
Actors: Subscriber, Presentation Application, Database Application
Purpose/Goal: Create, Retrieve, Update and Delete of Distribution Lists for Email
Scope: Voice, Fax and Mixed Distribution Lists are not covered.

See open issues to get an idea of what else is not covered by this document

Owner: TBD ?
Domain Expert: Tim D., Eric M., Al T., John L.
Sign-off: ?
Open Issues: a) All Send Issues

I)                   Notifications
II)                 R2L
III)               Send Types (Urgent, Bulk (after hours) etc

b) What is the Domain of Distribution Lists?  For the purposes of this first draft I am assuming a Domain is a set of Lists and elements associated with an Organization, or a Subscriber or a User.  The Domain would include any “Organization Wide” Lists, Address Books as well as any sub groups, sub group lists and user Lists.  It might be useful to develop a classification / naming system or conventions for types of lists.

c) Access to lists could be restricted by type of Access:

I)                   None
II)                 Read
III)               Read and Write
IV)               Read, Write and Delete

c) Fields to Display
d) Billing issues

I)                  Storage used
II)                 Quotas
e) Help

 

f) Other Presentation Application Features and Issues to coexist with Lists

I)                    Display Names versus internal names
II)                 Adding new atomic elements from within List CRUD
III)               Search for existing elements (Fuzzy search types)
IV)               Drill down display of “nested” Lists

g) Import of “external” lists or export to an external file

h) When a Subscriber/ User is Updated or Deleted, what actions take place in lists?

i) A List is created.  It includes other lists and / or atomic elements.

At the atomic (or even List level) there are duplicates?  What happens?

Business Rules:  
Pre-Conditions: Subscriber Authorized for this class of service
Post-Conditions: A new Distribution List is Created (or abandoned)
Description: A subscriber creates a list of people to send email to.  A List is short hand way of grouping recipients of a message together

 

 

2.1      Scenarios for the CRUD Distribution Lists Use Case

Actors: Subscriber, Presentation Application, Database Application
Purpose/Goal: Create a Distribution List
Rank: ?
Iteration: ?
Owner: Application Team?
Sign-off: ?
Open Issues: Physical Storage of Distribution Lists not addressed
Pre-Conditions: Subscriber Logged in
Post-Conditions: ?

 

 

Actor Activities

System Activities

1) Subscriber Selects “Create a Distribution List” Prompt Subscriber for List Name and Present a List of Domains to Select Elements from.
   
   
2) Subscriber Enters a Name and Selects Domain Presentation Application requests Table(s) from Database Application.  Presentation Application creates a “Pick List” of all the individual elements in the Domain selected.  These elements can be “atomic” elements or other Lists
   
3) Subscriber selects elements from Pick List to be included on the new Distribution List Presentation Application provides mechanism to

a)       Select List Members

b)       Keep track of them.

Note: In this case a simple diagram would be very useful.  Can I reference one?

   
4) Subscriber Saves List The Presentation Application issues a Save List request to the Database application
   
E3) User is not Authorized for this type of access for this List  
   
E5) Save error

a)       Quota exceeded

b)       Database error

c)       Bit Bucket is Full

 

2.2      Subflows

For examples see Open Items:  Other Presentation Application Features and Issues to coexist with Lists  f)

S-1:Name

2.3      Alternative Flows

Alternative flows describe exceptions.

E-1:Name

2.4      Candidate Objects

Candidate Classification

 

Security Table An association of SubscriberID, Userids and Distribution Lists and Access Rights (None, R, RW, RWD)
Distribution List Table Distribution List Friendly Name

Distribution List Internal Name

Owner ID

Security Access Key

Creation and Modification Dates

Fields from Source Lists to be displayed

 

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s