https://wiki.esipfed.org/w/index.php?title=Use_Case_Process_Comments&feed=atom&action=historyUse Case Process Comments - Revision history2024-03-28T16:15:23ZRevision history for this page on the wikiMediaWiki 1.35.14https://wiki.esipfed.org/w/index.php?title=Use_Case_Process_Comments&diff=7489&oldid=prevKbene at 15:01, March 7, 20072007-03-07T15:01:32Z<p></p>
<p><b>New page</b></p><div><br><br />
<center>(added by [[User:HowardBurrows|HowardBurrows]] 10:29, 7 February 2007 (EST))</center><br />
<br><br />
# I don't think we should use "TIWG" in page title. Maybe call it "Application Use Cases"? <br />
# 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]]. <br />
# Here is a partial comparison of the document structure used for the previous cases with that proposed here:<br />
<br><br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
!New proposal<br />
!Previous example<br />
|- valign="top"<br />
|<br />
1 Use Case <Cluster>.<SubArea>.<number>.<letter>: <Short Name><br />
:1.1 Purpose<br />
:1.2 Revision Information<br />
:1.3 Use Case Identification<br />
::1.3.1 Use Case Designation<br />
::1.3.2 Use Case Name<br />
----<br />
:1.4 Use Case Definition<br />
::1.4.1 Actors<br />
:::1.4.1.1 Primary Actors<br />
:::1.4.1.2 Other Actors<br />
<br><br />
----<br />
::1.4.2 Preconditions<br />
::1.4.3 Postconditions<br />
::1.4.4 Normal Flow (Process Model)<br />
::1.4.5 Alternative Flows<br />
::1.4.6 Successful Outcomes<br />
::1.4.7 Failure Outcomes<br />
::1.4.8 Special Functional Requirements<br />
::1.4.9 Extension Points<br />
----<br />
:1.5 Diagrams<br />
::1.5.1 Use Case Diagram<br />
::1.5.2 State Diagram (optional)<br />
::1.5.3 Activity Diagram (optional)<br />
::1.5.4 Other Diagrams (optional)<br />
:1.6 Non-Functional Requirements (optional)<br />
::1.6.1 Performance<br />
::1.6.2 Reliability<br />
::1.6.3 Scalability<br />
::1.6.4 Usability<br />
::1.6.5 Security<br />
::1.6.6 Other Non-functional Requirements<br />
:1.7 Selected Technology<br />
::1.7.1 Overall Technical Approach<br />
::1.7.2 Architecture<br />
::1.7.3 Technology A<br />
:::1.7.3.1 Description<br />
:::1.7.3.2 Benefits<br />
:::1.7.3.3 Limitations<br />
::1.7.4 Technology B<br />
:::1.7.4.1 Description<br />
:::1.7.4.2 Benefits<br />
:::1.7.4.3 Limitations<br />
:1.8 References (optional)<br />
|<br />
<br><br><br><br />
1. Use Case Identification<br />
:1.1 Use Case Number<br />
:1.2 Use Case Name<br />
----<br />
2.Use Case Definition<br />
:2.1 Actors<br />
<br><br><br />
:2.2 Business Rules<br />
----<br />
:2.3 Preconditions<br />
:2.4 Normal Flow<br />
:2.5 Alternative Flows<br />
:2.6 Postconditions<br />
:2.7 Extension Points<br />
:2.8 Special Requirements<br />
<br><br><br />
----<br />
:2.9 Assumptions<br />
:2.10 Notes<br />
:2.11 Issues<br />
|-<br />
|}</div>Kbene