Use Case Name: dco member Directory page in dco community Portal



Download 39.83 Kb.
Date conversion13.12.2016
Size39.83 Kb.

Use Case Name: DCO Member Directory page in DCO Community Portal

Point of Contact Name: 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.
DCO Member Directory page in DCO Community Portal


Goal

The goal briefly describes what the user intends to achieve with this use case.
Allow Web Users to view a list of the DCO Member Directory with the ability to view more information.


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.

The DCO Community Portal is the place for people to view information about the DCO project, including, but not limited to, a directory of all DCO Community Members. Currently this page is generated from user information collected in the DCO Community Portal. But with user information now being pushed into the DCO Information Portal, this directory page now needs to query the Information Portal in order to populate the DCO Directory but provide a Web User with the same functionality as they have in the current system.


This use case formalizes this requirement by specifying that there is indeed a DCO Directory page in the Community Portal and how DCO Member information is retrieved and rendered on pages in the DCO Community Portal.
This use case does not cover a web user viewing information in the Information Portal by clicking on a member’s name or image in the directory listing


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.
Web User – Any person who browses to the DCO Community Portal

DCO Community Portal – DCO web site for community collaboration and information sharing

DCO Information Portal – DCO web site used to create, edit, and provide information about resources related to DCO


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.
DCO Community Portal is available to anyone

DCO Information Portal is available for queries



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.
Web User browses to the DCO Member Directory page


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. Web User visits the DCO Community Portal at https://deepcarbon.net

  2. Web User clicks on link to view the DCO Directory

  3. Web User is taken to page that shows the first set of users

  4. Web User clicks a next link to get to the next set of users

  5. Web User clicks on a page number to get to that set of users




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. Web User attempts to click on a next link but receives an error

  2. Web User attempts to click on a page number but receives an error




Post Conditions

Here we give any conditions that will be true of the state of the system after the use case has been completed.
DCO Community Members shown on a page with basic information and ability to click on their name or picture to get to that Members full information.


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.
macintosh hd:users:westp:downloads:dcomemberdirectorypage_activitydiagram - new page.jpeg

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.
Current DCO Directory lists 12 members at a time. This number could change
This use case does not cover the web user filtering the list of members or the web user clicking on a name or image to view more information.
The Member Directory is, in fact, the S2S People Browser



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

Member Information

In situ




Only basic information shown in directory, full information shown on member’s profile page

DCO Information Portal

DCO Information 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

First Page Members

DCO Community Portal

The first page of the DCO Directory showing the first 12 members in alphabetical order and their basic information.

Web User

DCO Community Portal

Second Page Members

DCO Community Portal

The second page of the DCO Directory showing the second 12 members in alphabetical order and their basic information.

Web User

DCO Community Portal

Fifth Page Members

DCO Community Portal

The 5th page of the DCO Directory showing the 5th set of 12 members in alphabetical order and their basic information.

Web User

DCO Community Portal

Error

DCO Community Portal

The Community Portal is unable to process the request and presents the Web User with information about this failure

Web User

DCO Community Portal

Information Error

DCO Information Portal

The Community Portal receives an error response from the Information Portal and presents the Web User with information about this failure

DCO Community Portal and Web User

DCO Information 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

DCO Community Portal

DCO

The DCO Community Portal is the web-based front for the DCO project providing collaboration information, new articles, social media content for DCO, etc…

DCO Community Portal

DCO Information Portal Endpoint

DCO

The DCO Information Portal provides an endpoint for various systems, both internal and external, to query for resources within the DCO system including, but not limited to, user information, event information, publication information and dataset information.

DCO Information 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- - DCO Member Directory page in DCO Community Portal


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

    Main page