Use Case Name: Alert Group Members of Group Action Point of Contact Name: Katie Pratt, Patrick West



Download 40.66 Kb.
Date conversion13.12.2016
Size40.66 Kb.

Use Case Name: Alert Group Members of Group Action

Point of Contact Name: Katie Pratt, Patrick West



Use Case Name

Give a short descriptive name for the use case to serve as a unique identifier. Consider goal-driven use case name.
Alert Group Members of Group Action


Goal

The goal briefly describes what the user intends to achieve with this use case.
To alert members of a group to new content within the group.


Summary

Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.
There are various aspects of the group collaborative tools that require some form of notification functionality. These include, but are not necessarily limited to, the addition of calendar items, task assignments, new page created, and document updating. The alert should function both upon login to the group page by each unique user, and send an email alert to any group members who have turned on group notification, to their DCO registered email address.


Actors

List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.
Primary - Group member - member of a group who creates content that triggers notification

Secondary - Group members – all members of a group to whom notification is to be made to



Portal – The Deep Carbon Community Portal in which the action is taken and notifications come from


Preconditions

Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.





Triggers

Here we describe in detail the event or events that brings about the execution of this use case. Triggers can be external, temporal, or internal. They can be single events or when a set of conditions are met, List all triggers and relationships.
New task created in a group by a member of the group.


Basic Flow

Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)


  1. Group member adds a group task.

  2. All members of the group who have enabled group notification are notified of the new task via email

  3. Group members who visit the group pages see that there is new content in the group




Alternate Flow

Here we give any alternate flows that might occur. May include flows that involve error conditions. Or flows that fall outside of the basic flow.


  1. Group member adds any of the group content available to the group




Post Conditions

Here we give any conditions that will be true of the state of the system after the use case has been completed.


  • Group members who have enabled group notifications receive email and are able to click on a link to the new content

  • Group members see activity notification when visiting group home page




Activity Diagram

Here a diagram is given to show the flow of events that surrounds the use case. It might be that text is a more useful way of describing the use case. However often a picture speaks a 1000 words.




Notes

There is always some piece of information that is required that has no other place to go. This is the place for that information.
Drupal Commons does not allow for subscribing to individual types of events in a group. You can receive notifications for the group as a whole.



Resources

In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.
Data:

Data

Type

Characteristics

Description

Owner

Source System

(dataset name)

Remote,

In situ,



Etc.

e.g. – no cloud cover

Short description of the dataset, possibly including rationale of the usage characteristics

USGS, ESA, etc.

Name of the system which supports discovery and access

New Gorup Content




Any type of content

Any one of existing group content that is added within the group

Group

DCO Community Portal

Group Email







Email received by all group members who have group notification turned on of new group content

Group

DCO Community Portal

Group notification







Visible notification that new content has been added to the group

Group

DCO Community Portal


Modeling Services

Model

Owner

Description

Consumes

Frequency

Source System

(model name)

Organization that offers the model

Short description of the model

List of data consumed

How often the model runs

Name of the system which offers access to the model




















Event Notification Services

Event

Owner

Description

Subscription

Source System

(Event name)

Organization that offers the event

Short description of the event

List of subscriptions (and owners)

Name of the system which offers this event

Group Email

Group

When new content is added to the group an email is sent to members of the group who have notification turned on.

Group Members who have enabled group notifications

DCO Community Portal

Visible Notification

Group

When new content is added to the group there is a visible notification to group members who visit the group pages.

All Group Members

DCO Community Portal


Application Services

Application

Owner

Description

Source System

(Application name)

Organization that offers the Application

Short description of the application portal

Name of the system which offers access to this resource

Drupal

DCO

The DCO Community Portal is the website used by members of the community to coordinate DCO information

DCO Community Portal


Other resources

Resource

Owner

Description

Availability

Source System

(sensor name)

Organization that owns/ manages resource

Short description of the resource

How often the resource is available

Name of system which provides resource



















UseCase- -Template http://en.wikipedia.org/wiki/Use_cases#Use_case_templates


The database is protected by copyright ©dentisty.org 2016
send message

    Main page