Difference between revisions of "Application Use Cases"

From Earth Science Information Partners (ESIP)
(Added some comments)
m (fixed appearance)
Line 7: Line 7:
 
* ...
 
* ...
  
<center><em>========= Discussion area ==========</em></center>
 
 
----
 
----
 +
<br>
 +
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center>
 +
<br>
 
# I don't think we should use "TIWG" in page title.  Maybe call it "Application Use Cases"?  
 
# I don't think we should use "TIWG" in page title.  Maybe call it "Application Use Cases"?  
 
# Where should this appear?  We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]].   
 
# Where should this appear?  We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the [[Main_Page|Main wiki page]].   
# Here is a comparison of the document structure used for the previous cases with that proposed here:
+
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:
 
+
<br>
 
{| border="1" cellspacing="0" cellpadding="5" align="center"
 
{| border="1" cellspacing="0" cellpadding="5" align="center"
 
!New proposal
 
!New proposal

Revision as of 09:29, February 7, 2007

This page provides a point of access for the Use Cases under development by the DSWG Technology Infusion Working Group in support of ESIP Federation application area technology activities.

The Use Case template is available to copy from at: Application_UseCase_Template

  • Use Case 1 (this entry would be replaced with a link to a separate document for a use case)
  • Use Case 2
  • ...


(added by HowardBurrows 10:29, 7 February 2007 (EST))


  1. I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"?
  2. Where should this appear? We started a section for Use Cases as part of the Exchange discussion (See architecture section at the bottom of the Main wiki page.
  3. Here is a partial comparison of the document structure used for the previous cases with that proposed here:


New proposal Previous example

1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name>

1.1 Purpose
1.2 Revision Information
1.3 Use Case Identification
1.3.1 Use Case Designation
1.3.2 Use Case Name

1.4 Use Case Definition
1.4.1 Actors
1.4.1.1 Primary Actors
1.4.1.2 Other Actors



1.4.2 Preconditions
1.4.3 Postconditions
1.4.4 Normal Flow (Process Model)
1.4.5 Alternative Flows
1.4.6 Successful Outcomes
1.4.7 Failure Outcomes
1.4.8 Special Functional Requirements
1.4.9 Extension Points

1.5 Diagrams
1.5.1 Use Case Diagram
1.5.2 State Diagram (optional)
1.5.3 Activity Diagram (optional)
1.5.4 Other Diagrams (optional)
1.6 Non-Functional Requirements (optional)
1.6.1 Performance
1.6.2 Reliability
1.6.3 Scalability
1.6.4 Usability
1.6.5 Security
1.6.6 Other Non-functional Requirements
1.7 Selected Technology
1.7.1 Overall Technical Approach
1.7.2 Architecture
1.7.3 Technology A
1.7.3.1 Description
1.7.3.2 Benefits
1.7.3.3 Limitations
1.7.4 Technology B
1.7.4.1 Description
1.7.4.2 Benefits
1.7.4.3 Limitations
1.8 References (optional)




1. Use Case Identification

1.1 Use Case Number
1.2 Use Case Name

2.Use Case Definition

2.1 Actors



2.2 Business Rules

2.3 Preconditions
2.4 Normal Flow
2.5 Alternative Flows
2.6 Postconditions
2.7 Extension Points
2.8 Special Requirements




2.9 Assumptions
2.10 Notes
2.11 Issues