Difference between revisions of "Use Case Template"
| Line 1: | Line 1: | ||
| − | = | + | =Use Case AQ.FireOccurence.1.a: <br> |
| − | + | Spatial and temporal analysis of satellite derived fire occurrence data | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Purpose== | ==Purpose== | ||
| − | |||
Earth Information Exchange | Earth Information Exchange | ||
| + | To test web service orchestration for air quality data analysis. | ||
==Revision Information== | ==Revision Information== | ||
| − | Version | + | Version 0.1.a |
| − | |||
| − | |||
| − | + | Prepared by: | |
| + | Stefan Falke | ||
| + | Washington University and | ||
| + | Northrop Grumman IT - TASC | ||
| − | + | created: February 23, 2007 | |
Revision History | Revision History | ||
| − | Modified by <Modifier Name/Affil>, <Date/time>, <Brief Description> | + | Modified by |
| + | <Modifier Name/Affil>, | ||
| + | <Date/time>, | ||
| + | <Brief Description> | ||
==Use Case Identification== | ==Use Case Identification== | ||
| Line 134: | Line 133: | ||
==References (optional)== | ==References (optional)== | ||
| − | + | Soja, et al., 2005: http://www.epa.gov/ttn/chief/conference/ei14/session12/soja.pdf | |
| + | Describes method used for analysis of fire locations/areas for May-August 2002 in Florida. | ||
Revision as of 10:28, February 23, 2007
=Use Case AQ.FireOccurence.1.a:
Spatial and temporal analysis of satellite derived fire occurrence data
Purpose
Earth Information Exchange To test web service orchestration for air quality data analysis.
Revision Information
Version 0.1.a
Prepared by: Stefan Falke Washington University and Northrop Grumman IT - TASC
created: February 23, 2007
Revision History
Modified by <Modifier Name/Affil>, <Date/time>, <Brief Description>
Use Case Identification
Use Case Designation
<Cluster>.<SubArea>.<number>.<letter>
Use Case Name
<Insert short name and long name>
Use Case Definition
First paragraph is short description, second paragraph, etc. may contain further details.
Through this use case, the system User does THIS and it results in THIS and is used for THIS.
Actors
Always identify primary actors, may be more than one. Also identify other actor including any other systems or services which are important.
Primary Actors
The actor that initiates this use case is the portal User. Providers may also initiate this use case as a precursor to use case NNN...
Other Actors
Preconditions
- 1.XXX available
- 2.YYY validated
- 3.ZZZ published
Postconditions
- 1.Datasets are ..
- 2.Appropriate action ...
- 3.Controls are ...
Normal Flow (Process Model)
- 1)The user selects ...
- 2)The user then ...
- 3)The results of the XXX are ...
- 4)The user ...
Alternative Flows
- 1)The user selects the alternate ...
- 2)The user then ...
Successful Outcomes
- 1.Operation succeeds and user obtains QQQ.
Failure Outcomes
- 1.Operation fails to return any XXX. Should instead YYYY.
- 2.Illegal input of AAA, Should instead ZZZZ
Special Functional Requirements
None
Extension Points
- <Cluster>.<SubArea>.<number>.<letter+1> something added or a variant.
E.g. AQ.Smoke.1.b something added or a variant
- <Cluster>.<SubArea>.<number>.<letter+2> something added or a variant
- <Cluster>.<SubArea>.<number>.<letter+3> something added or a variant
Diagrams
Use Case Diagram
State Diagram (optional)
Activity Diagram (optional)
Other Diagrams (optional)
Non-Functional Requirements (optional)
Performance
Reliability
Scalability
Usability
Security
Other Non-functional Requirements
Selected Technology
Overall Technical Approach
Architecture
Technology A
Description
Benefits
Limitations
Technology B
Description
Benefits
Limitations
References (optional)
Soja, et al., 2005: http://www.epa.gov/ttn/chief/conference/ei14/session12/soja.pdf Describes method used for analysis of fire locations/areas for May-August 2002 in Florida.
