1 | <p> |
---|
2 | <p id="_0"> |
---|
3 | <span style="font-family: times new roman,times,serif; font-size: 10pt;">RUP Use Case Modeling Guidelines Document v1.0</span></p> |
---|
4 | |
---|
5 | <p id="_2" style="text-align: right;"> |
---|
6 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use-Case Modeling Guidelines</b></span></p> |
---|
7 | <p id="_3" style="text-align: right;"> |
---|
8 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b> </b></span></p> |
---|
9 | <p id="_4" style="text-align: right;"> |
---|
10 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Version </b>0.01</span></p> |
---|
11 | <p id="_5" style="text-align: center;"> |
---|
12 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b> </b></span></p> |
---|
13 | <p id="_6"> |
---|
14 | <span style="font-family: arial,sans-serif; font-size: 12pt;"> </span></p> |
---|
15 | <p id="_7"> |
---|
16 | <span style="font-family: arial,sans-serif; font-size: 12pt;"> Table of Contents</span></p> |
---|
17 | <p> |
---|
18 | [Table of Contents omitted]</p> |
---|
19 | <h1 id="_34"> |
---|
20 | <span><b>1. </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b> </b>Document Control Information</span></h1> |
---|
21 | <h2 id="_35"> |
---|
22 | <span><b>1.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Revision History</b></span></h2> |
---|
23 | <table border="1" cellpadding="0" cellspacing="0" id="_36"> |
---|
24 | <tbody> |
---|
25 | <tr> |
---|
26 | <th colspan="1" rowspan="1" style="width: 153.6px; vertical-align: top;"> |
---|
27 | <p id="_37" style="text-align: center;"> |
---|
28 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Date</b></span></p> |
---|
29 | </th> |
---|
30 | <th colspan="1" rowspan="1" style="width: 76.8px; vertical-align: top;"> |
---|
31 | <p id="_38" style="text-align: center;"> |
---|
32 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Version</b></span></p> |
---|
33 | </th> |
---|
34 | <th colspan="1" rowspan="1" style="width: 208.8px; vertical-align: top;"> |
---|
35 | <p id="_39" style="text-align: center;"> |
---|
36 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Description</b></span></p> |
---|
37 | </th> |
---|
38 | <th colspan="1" rowspan="1" style="width: 144px; vertical-align: top;"> |
---|
39 | <p id="_40" style="text-align: center;"> |
---|
40 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Author</b></span></p> |
---|
41 | </th> |
---|
42 | </tr> |
---|
43 | <tr> |
---|
44 | <td colspan="1" id="_41" rowspan="1" style="width: 153.6px; vertical-align: top;"> |
---|
45 | <p id="_42"> |
---|
46 | </p> |
---|
47 | </td> |
---|
48 | <td colspan="1" id="_43" rowspan="1" style="width: 76.8px; vertical-align: top;"> |
---|
49 | <p id="_44"> |
---|
50 | </p> |
---|
51 | </td> |
---|
52 | <td colspan="1" id="_45" rowspan="1" style="width: 208.8px; vertical-align: top;"> |
---|
53 | <p id="_46"> |
---|
54 | </p> |
---|
55 | </td> |
---|
56 | <td colspan="1" id="_47" rowspan="1" style="width: 144px; vertical-align: top;"> |
---|
57 | <p id="_48"> |
---|
58 | </p> |
---|
59 | </td> |
---|
60 | </tr> |
---|
61 | <tr> |
---|
62 | <td colspan="1" id="_49" rowspan="1" style="width: 153.6px; vertical-align: top;"> |
---|
63 | <p id="_50"> |
---|
64 | </p> |
---|
65 | </td> |
---|
66 | <td colspan="1" id="_51" rowspan="1" style="width: 76.8px; vertical-align: top;"> |
---|
67 | <p id="_52"> |
---|
68 | </p> |
---|
69 | </td> |
---|
70 | <td colspan="1" id="_53" rowspan="1" style="width: 208.8px; vertical-align: top;"> |
---|
71 | <p id="_54"> |
---|
72 | </p> |
---|
73 | </td> |
---|
74 | <td colspan="1" id="_55" rowspan="1" style="width: 144px; vertical-align: top;"> |
---|
75 | <p id="_56"> |
---|
76 | </p> |
---|
77 | </td> |
---|
78 | </tr> |
---|
79 | </tbody> |
---|
80 | </table> |
---|
81 | <p id="_57"> |
---|
82 | </p> |
---|
83 | <h2 id="_58"> |
---|
84 | <span><b>1.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Reviewers and Approvers</b></span></h2> |
---|
85 | <table border="1" cellpadding="0" cellspacing="0" id="_59"> |
---|
86 | <tbody> |
---|
87 | <tr> |
---|
88 | <td colspan="1" id="_60" rowspan="1" style="width: 294.8px; vertical-align: top;"> |
---|
89 | <p id="_61" style="text-align: center;"> |
---|
90 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Reviewer</b></span></p> |
---|
91 | </td> |
---|
92 | <td colspan="1" id="_62" rowspan="1" style="width: 288.4px; vertical-align: top;"> |
---|
93 | <p id="_63" style="text-align: center;"> |
---|
94 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Functional Area</b></span></p> |
---|
95 | </td> |
---|
96 | </tr> |
---|
97 | <tr> |
---|
98 | <td colspan="1" id="_64" rowspan="1" style="width: 294.8px; vertical-align: top;"> |
---|
99 | <p id="_65"> |
---|
100 | </p> |
---|
101 | </td> |
---|
102 | <td colspan="1" id="_66" rowspan="1" style="width: 288.4px; vertical-align: top;"> |
---|
103 | <p id="_67"> |
---|
104 | </p> |
---|
105 | </td> |
---|
106 | </tr> |
---|
107 | </tbody> |
---|
108 | </table> |
---|
109 | <p id="_68"> |
---|
110 | </p> |
---|
111 | <h1 id="_69"> |
---|
112 | <span><b>2. </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b> </b>Introduction</span></h1> |
---|
113 | <h2 id="_70"> |
---|
114 | <span><b>2.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Purpose</b></span></h2> |
---|
115 | <p id="_71"> |
---|
116 | <span style="font-family: arial,sans-serif; font-size: 12pt;">This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines This document describes use-case modeling guidelines</span></p> |
---|
117 | <h2 id="_72"> |
---|
118 | <span><b>2.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Scope</b></span></h2> |
---|
119 | <h2 id="_73"> |
---|
120 | <span><b>2.3 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>References</b></span></h2> |
---|
121 | <ul> |
---|
122 | <li id="_74" style="list-style-type: disc;"> |
---|
123 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><u>Use Case Mode</u>lling, Kurt Bittner, Ian Spence. June 2003.</span></li> |
---|
124 | <li id="_75" style="list-style-type: disc;"> |
---|
125 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Rational Unified Process</span></li> |
---|
126 | <li id="_76" style="list-style-type: disc;"> |
---|
127 | <span style="font-family: arial,sans-serif; font-size: 12pt;">OMG Unified Modeling Language Specification, Version 2.0. (</span><a href="http://www.omg.org" id="_77"><span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);">http://www.omg.org</span></a><span style="font-family: arial,sans-serif; font-size: 12pt;">)</span></li> |
---|
128 | </ul> |
---|
129 | <h2 id="_78"> |
---|
130 | <span><b>2.4 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Overview</b></span></h2> |
---|
131 | <p id="_79"> |
---|
132 | <span style="font-family: arial,sans-serif; font-size: 12pt;">This set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines is set of guidelines</span></p> |
---|
133 | <h1 id="_80"> |
---|
134 | <span><b>3. </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use-Case Modeling Guidelines</b></span></h1> |
---|
135 | <h2 id="_81"> |
---|
136 | <span><b>3.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Evolution of a Use Case</b></span></h2> |
---|
137 | <p id="_82"> |
---|
138 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution. </span></p> |
---|
139 | <h2 id="_83"> |
---|
140 | <span><b>3.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Evolution of a Use Case</b></span></h2> |
---|
141 | <p id="_84"> |
---|
142 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution. </span></p> |
---|
143 | <p id="_85"> |
---|
144 | <span style="font-family: arial,sans-serif; font-size: 12pt;">.</span></p> |
---|
145 | <h2 id="_86"> |
---|
146 | <span><b>3.3 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Evolution of a Use Case</b></span></h2> |
---|
147 | <p id="_87"> |
---|
148 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution. </span></p> |
---|
149 | <p id="_88"> |
---|
150 | <span style="font-family: arial,sans-serif; font-size: 12pt;">.</span></p> |
---|
151 | <h2 id="_89"> |
---|
152 | <span><b>3.4 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Evolution of a Use Case</b></span></h2> |
---|
153 | <p id="_90"> |
---|
154 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution. </span></p> |
---|
155 | <p id="_91"> |
---|
156 | <span style="font-family: arial,sans-serif; font-size: 12pt;">.</span></p> |
---|
157 | <h2 id="_92"> |
---|
158 | <span><b>3.5 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Evolution of a Use Case</b></span></h2> |
---|
159 | <p id="_93"> |
---|
160 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution. </span></p> |
---|
161 | <p id="_94"> |
---|
162 | <span style="font-family: arial,sans-serif; font-size: 12pt;">.</span></p> |
---|
163 | <h2 id="_95"> |
---|
164 | <span><b>3.6 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Evolution of a Use Case</b></span></h2> |
---|
165 | <p id="_96"> |
---|
166 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution Evolution. </span></p> |
---|
167 | <p id="_97"> |
---|
168 | <span style="font-family: arial,sans-serif; font-size: 12pt;">.</span></p> |
---|
169 | <h3 id="_98"> |
---|
170 | <span><b>3.6.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Actor Guidelines</b></span></h3> |
---|
171 | <p id="_99"> |
---|
172 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each concrete Use Case will be involved with at least one Actor.</span></p> |
---|
173 | <p id="_100"> |
---|
174 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Actors will be given intuitive and descriptive actor name(s) that correspond to their roles.</span></p> |
---|
175 | <h3 id="_101"> |
---|
176 | <span><b>3.6.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>Keep this section </i></b>Communicates Association</span></h3> |
---|
177 | <p id="_102"> |
---|
178 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each concrete Use Case will be involved with at least one Actor.</span></p> |
---|
179 | <p id="_103"> |
---|
180 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Actors will be given intuitive and descriptive actor name(s) that correspond to their roles.</span></p> |
---|
181 | <p id="_104"> |
---|
182 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each concrete Use Case will be involved with at least one Actor.</span></p> |
---|
183 | <p id="_105"> |
---|
184 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Actors will be given intuitive and descriptive actor name(s) that correspond to their roles.</span></p> |
---|
185 | <p id="_106"> |
---|
186 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each concrete Use Case will be involved with at least one Actor.</span></p> |
---|
187 | <p id="_107"> |
---|
188 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Actors will be given intuitive and descriptive actor name(s) that correspond to their roles.</span></p> |
---|
189 | <p id="_108"> |
---|
190 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each concrete Use Case will be involved with at least one Actor.</span></p> |
---|
191 | <p id="_109"> |
---|
192 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Actors will be given intuitive and descriptive actor name(s) that correspond to their roles.</span></p> |
---|
193 | <h3 id="_110"> |
---|
194 | <span><b>3.6.3 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><<Communicates>> relationship</b></span></h3> |
---|
195 | <p id="_111"> |
---|
196 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each concrete Use Case will be involved with at least one Actor.</span></p> |
---|
197 | <p id="_112"> |
---|
198 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Actors will be given intuitive and descriptive actor name(s) that correspond to their roles.</span></p> |
---|
199 | <h3 id="_113"> |
---|
200 | <span><b>3.6.4 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><<Include>> and <<Extend>> relationships</b></span></h3> |
---|
201 | <p id="_114"> |
---|
202 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be</i> performed by architects after use cases are detailed.</span></p> |
---|
203 | <p id="_115"> |
---|
204 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
205 | <p id="_116"> |
---|
206 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
207 | <p id="_117"> |
---|
208 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
209 | <p id="_118"> |
---|
210 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
211 | <p id="_119"> |
---|
212 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
213 | <p id="_120"> |
---|
214 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
215 | <p id="_121"> |
---|
216 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
217 | <h4 id="_122"> |
---|
218 | <span><b><i>3.6.4.1 </i></b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>«include» relationship</i></b></span></h4> |
---|
219 | <p id="_123"> |
---|
220 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
221 | <p id="_124"> |
---|
222 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
223 | <p id="_125"> |
---|
224 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
225 | <p id="_126"> |
---|
226 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
227 | <p id="_127"> |
---|
228 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
229 | <p id="_128"> |
---|
230 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
231 | <p id="_129"> |
---|
232 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
233 | <p id="_130"> |
---|
234 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information is not covered in the course. These activities should be performed by architects after use cases are detailed.</i></span></p> |
---|
235 | <h4 id="_131"> |
---|
236 | <span><b><i>3.6.4.2 </i></b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>«extend» relationship</i></b></span></h4> |
---|
237 | <p id="_132"> |
---|
238 | <span style="font-family: arial,sans-serif; font-size: 12pt;">If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary If there is a part of a base use case that is optional, or not necessary o understand the primary purpose of the use case, that part can be factored out, and put into an additional use case in order to simplify the structure of the base use case. The addition is implicitly inserted in the base use case, using the extend relationship.</span></p> |
---|
239 | <h3 id="_133"> |
---|
240 | <span><b>3.6.5 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Actor-Generalization</b></span></h3> |
---|
241 | <p id="_134"> |
---|
242 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information was not covered in the course.</i></span></p> |
---|
243 | <p id="_135"> |
---|
244 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information was not covered in the course.</i></span></p> |
---|
245 | <p id="_136"> |
---|
246 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information was not covered in the course.</i></span></p> |
---|
247 | <p id="_137"> |
---|
248 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information was not covered in the course.</i></span></p> |
---|
249 | <p id="_138"> |
---|
250 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information was not covered in the course.</i></span></p> |
---|
251 | <p id="_139"> |
---|
252 | <span style="font-family: arial,sans-serif; font-size: 12pt; color: rgb(0, 0, 255);"><i>This information was not covered in the course.</i></span></p> |
---|
253 | <h4 id="_140"> |
---|
254 | <span><b><i>3.6.5.1 </i></b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>Use of Actor-Generalization</i></b></span></h4> |
---|
255 | <p id="_141"> |
---|
256 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each use-case will. Each use-case will.</span></p> |
---|
257 | <p id="_142"> |
---|
258 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each use-case will.</span></p> |
---|
259 | <p id="_143"> |
---|
260 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each use-case will.</span></p> |
---|
261 | <p id="_144"> |
---|
262 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each use-case will.</span></p> |
---|
263 | <p id="_145"> |
---|
264 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Each use-case will.</span></p> |
---|
265 | <p id="_146"> |
---|
266 | </p> |
---|
267 | <h3 id="_147"> |
---|
268 | <span><b>3.6.6 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use-Case Generalization</b></span></h3> |
---|
269 | <p id="_148"> |
---|
270 | <span style="font-family: arial,sans-serif; font-size: 12pt;">This relationship is prohibited from use. his relationship is prohibited from use.</span></p> |
---|
271 | <p id="_149"> |
---|
272 | <span style="font-family: arial,sans-serif; font-size: 12pt;">his relationship is prohibited from use.</span></p> |
---|
273 | <p id="_150"> |
---|
274 | <span style="font-family: arial,sans-serif; font-size: 12pt;">his relationship is prohibited from use.</span></p> |
---|
275 | <p id="_151"> |
---|
276 | <span style="font-family: arial,sans-serif; font-size: 12pt;">his relationship is prohibited from use.</span></p> |
---|
277 | <p id="_152"> |
---|
278 | <span style="font-family: arial,sans-serif; font-size: 12pt;">his relationship is prohibited from use.</span></p> |
---|
279 | <p id="_153"> |
---|
280 | <span style="font-family: arial,sans-serif; font-size: 12pt;">his relationship is prohibited from use.</span></p> |
---|
281 | <p id="_154"> |
---|
282 | </p> |
---|
283 | <h3 id="_155"> |
---|
284 | <span><b>3.6.7 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of Interaction Diagrams</b></span></h3> |
---|
285 | <p id="_156"> |
---|
286 | <span style="font-family: arial,sans-serif; font-size: 12pt;">In some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, some cases, Interaction diagrams are optional.</span></p> |
---|
287 | <h3 id="_157"> |
---|
288 | <span><b>3.6.8 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of Activity Diagrams</b></span></h3> |
---|
289 | <p id="_158"> |
---|
290 | <span style="font-family: arial,sans-serif; font-size: 12pt;">In some cases, it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
291 | <p id="_159"> |
---|
292 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
293 | <p id="_160"> |
---|
294 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
295 | <p id="_161"> |
---|
296 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
297 | <p id="_162"> |
---|
298 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
299 | <p id="_163"> |
---|
300 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
301 | <p id="_164"> |
---|
302 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output messages) and treat the system as a black box. Use boundary objects with logical names as defined in the use case flow of events, without assigning them to classes at this point.</span></p> |
---|
303 | <p id="_165"> |
---|
304 | <span style="font-family: arial,sans-serif; font-size: 12pt;">it is beneficial to include, in addition to the textual flow of events, an Interaction diagram to illustrate the “high level” flow of events of the use case. It is recommended the sequence diagram for this be drawn in Rational Rose. Include only the communication between the actors and the boundary objects (covering both the input and the output The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
305 | <p id="_166"> |
---|
306 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
307 | <p id="_167"> |
---|
308 | </p> |
---|
309 | <h1 id="_168"> |
---|
310 | <span><b>4. </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>How to Describe a Use Case</b></span></h1> |
---|
311 | <h2 id="_169"> |
---|
312 | <span><b>4.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>General Style</b></span></h2> |
---|
313 | <p id="_170"> |
---|
314 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases Use Case Name</span></p> |
---|
315 | <h2 id="_171"> |
---|
316 | <span><b>4.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use Case Brief Description</b></span></h2> |
---|
317 | <h2 id="_172"> |
---|
318 | <span><b>4.3 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases </b>Use Case Flows of Events Style</span></h2> |
---|
319 | <p id="_173"> |
---|
320 | <span style="font-family: arial,sans-serif; font-size: 12pt;">step. </span></p> |
---|
321 | <h2 id="_174"> |
---|
322 | <span><b>4.4 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Basic Flow</b></span></h2> |
---|
323 | <p id="_175"> |
---|
324 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The use-case flows will make use of tag headings to describe the steps at a high-level, followed by numbered descriptions of what the actor does and what the system does under the heading. These tagged steps will be referenced in alternative flows and sub-flows.</span></p> |
---|
325 | <p id="_176"> |
---|
326 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The use-case flows will make use of tag headings to describe the steps at a high-level, followed by numbered descriptions of what the actor does and what the system does under the heading. These tagged steps will be referenced in alternative flows and sub-flows.</span></p> |
---|
327 | <h3 id="_177"> |
---|
328 | <span><b>4.4.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases </b>Using Alternative flows</span></h3> |
---|
329 | <p id="_178"> |
---|
330 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
331 | <p id="_179"> |
---|
332 | </p> |
---|
333 | <h2 id="_180"> |
---|
334 | <span><b>4.5 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Sub-flow</b>s</span></h2> |
---|
335 | <p id="_181"> |
---|
336 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
337 | <p id="_182"> |
---|
338 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
339 | <p id="_183"> |
---|
340 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
341 | <p id="_184"> |
---|
342 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
343 | <h3 id="_185"> |
---|
344 | <span><b>4.5.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>Using Sub-flows</i></b></span></h3> |
---|
345 | <p id="_186"> |
---|
346 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
347 | <p id="_187"> |
---|
348 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
349 | <p id="_188"> |
---|
350 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
351 | <h2 id="_189"> |
---|
352 | <span><b>4.6 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Preconditions and </b>Post-conditions</span></h2> |
---|
353 | <p id="_190"> |
---|
354 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
355 | <h3 id="_191"> |
---|
356 | <span><b>4.6.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of Preconditions</b></span></h3> |
---|
357 | <p id="_192"> |
---|
358 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
359 | <h3 id="_193"> |
---|
360 | <span><b>4.6.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of </b>post-conditions</span></h3> |
---|
361 | <p id="_194"> |
---|
362 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
363 | <h2 id="_195"> |
---|
364 | <span><b>4.7 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Extension Points</b></span></h2> |
---|
365 | <h3 id="_196"> |
---|
366 | <span><b>4.7.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Include Relationship</b></span></h3> |
---|
367 | <h3 id="_197"> |
---|
368 | <span><b>4.7.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Extend Relationship</b></span></h3> |
---|
369 | <h2 id="_198"> |
---|
370 | <span><b>4.8 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of Scenarios</b></span></h2> |
---|
371 | <p id="_199"> |
---|
372 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
373 | <h2 id="_200"> |
---|
374 | <span><b>4.9 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of Glossary Terms</b></span></h2> |
---|
375 | <p id="_201"> |
---|
376 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
377 | <p id="_202"> |
---|
378 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
379 | <h2 id="_203"> |
---|
380 | <span><b>4.10 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Additional </b>Guidelines</span></h2> |
---|
381 | <h3 id="_204"> |
---|
382 | <span><b>4.10.1 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Inline conditional and repetitive behavior</b></span></h3> |
---|
383 | <p id="_205"> |
---|
384 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
385 | <p id="_206"> |
---|
386 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
387 | <h3 id="_207"> |
---|
388 | <span><b>4.10.2 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Consistent Use of Actor Name(s) </b></span></h3> |
---|
389 | <p id="_208"> |
---|
390 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
391 | <h3 id="_209"> |
---|
392 | <span><b>4.10.3 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Consistent </b>use of the imperative: Will</span></h3> |
---|
393 | <p id="_210"> |
---|
394 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
395 | <h3 id="_211"> |
---|
396 | <span><b>4.10.4 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of “Action” Terms</b></span></h3> |
---|
397 | <h4 id="_212"> |
---|
398 | <span><b><i>4.10.4.1 </i></b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>Define where the system is responsible for presenting the Action Option</i></b></span></h4> |
---|
399 | <p id="_213"> |
---|
400 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
401 | <p id="_214"> |
---|
402 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
403 | <h4 id="_215"> |
---|
404 | <span><b><i>4.10.4.2 </i></b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>Consistent use of the term throughout the Use Case</i></b></span></h4> |
---|
405 | <p id="_216"> |
---|
406 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
407 | <p id="_217"> |
---|
408 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
409 | <p id="_218"> |
---|
410 | </p> |
---|
411 | <h3 id="_219"> |
---|
412 | <span><b>4.10.5 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use of placeholders for missing detail (TBD</b> or None)</span></h3> |
---|
413 | <p id="_220"> |
---|
414 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
415 | <h3 id="_221"> |
---|
416 | <span><b>4.10.6 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Definition of and Reference to Supplementary Specifications</b></span></h3> |
---|
417 | <p id="_222"> |
---|
418 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
419 | <h3 id="_223"> |
---|
420 | <span><b>4.10.7 </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>User Interface</b></span></h3> |
---|
421 | <p id="_224"> |
---|
422 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases The Use Cases</span></p> |
---|
423 | <p id="_225" style="text-align: center;"> |
---|
424 | </p> |
---|
425 | <p id="_226" style="text-align: center;"> |
---|
426 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Words to AVOID</span></p> |
---|
427 | <table border="1" cellpadding="0" cellspacing="0" id="_227"> |
---|
428 | <tbody> |
---|
429 | <tr> |
---|
430 | <td colspan="1" id="_228" rowspan="1" style="width: 79.3333px; vertical-align: top;"> |
---|
431 | <p id="_229"> |
---|
432 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Click</span></p> |
---|
433 | </td> |
---|
434 | <td colspan="1" id="_230" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
435 | <p id="_231"> |
---|
436 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Drag</span></p> |
---|
437 | </td> |
---|
438 | <td colspan="1" id="_232" rowspan="1" style="width: 79.6667px; vertical-align: top;"> |
---|
439 | <p id="_233"> |
---|
440 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Form</span></p> |
---|
441 | </td> |
---|
442 | </tr> |
---|
443 | <tr> |
---|
444 | <td colspan="1" id="_234" rowspan="1" style="width: 79.3333px; vertical-align: top;"> |
---|
445 | <p id="_235"> |
---|
446 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Open</span></p> |
---|
447 | </td> |
---|
448 | <td colspan="1" id="_236" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
449 | <p id="_237"> |
---|
450 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Close</span></p> |
---|
451 | </td> |
---|
452 | <td colspan="1" id="_238" rowspan="1" style="width: 79.6667px; vertical-align: top;"> |
---|
453 | <p id="_239"> |
---|
454 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Drop</span></p> |
---|
455 | </td> |
---|
456 | </tr> |
---|
457 | <tr> |
---|
458 | <td colspan="1" id="_240" rowspan="1" style="width: 79.3333px; vertical-align: top;"> |
---|
459 | <p id="_241"> |
---|
460 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Button</span></p> |
---|
461 | </td> |
---|
462 | <td colspan="1" id="_242" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
463 | <p id="_243"> |
---|
464 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Field</span></p> |
---|
465 | </td> |
---|
466 | <td colspan="1" id="_244" rowspan="1" style="width: 79.6667px; vertical-align: top;"> |
---|
467 | <p id="_245"> |
---|
468 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Drop-down</span></p> |
---|
469 | </td> |
---|
470 | </tr> |
---|
471 | <tr> |
---|
472 | <td colspan="1" id="_246" rowspan="1" style="width: 79.3333px; vertical-align: top;"> |
---|
473 | <p id="_247"> |
---|
474 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Pop-up</span></p> |
---|
475 | </td> |
---|
476 | <td colspan="1" id="_248" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
477 | <p id="_249"> |
---|
478 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Scroll</span></p> |
---|
479 | </td> |
---|
480 | <td colspan="1" id="_250" rowspan="1" style="width: 79.6667px; vertical-align: top;"> |
---|
481 | <p id="_251"> |
---|
482 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Browse</span></p> |
---|
483 | </td> |
---|
484 | </tr> |
---|
485 | <tr> |
---|
486 | <td colspan="1" id="_252" rowspan="1" style="width: 79.3333px; vertical-align: top;"> |
---|
487 | <p id="_253"> |
---|
488 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Record</span></p> |
---|
489 | </td> |
---|
490 | <td colspan="1" id="_254" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
491 | <p id="_255"> |
---|
492 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Windw</span></p> |
---|
493 | </td> |
---|
494 | <td colspan="1" id="_256" rowspan="1" style="width: 79.6667px; vertical-align: top;"> |
---|
495 | <p id="_257"> |
---|
496 | </p> |
---|
497 | </td> |
---|
498 | </tr> |
---|
499 | </tbody> |
---|
500 | </table> |
---|
501 | <p id="_258" style="text-align: center;"> |
---|
502 | </p> |
---|
503 | <p id="_259" style="text-align: center;"> |
---|
504 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Words to Use</span></p> |
---|
505 | <table border="1" cellpadding="0" cellspacing="0" id="_260"> |
---|
506 | <tbody> |
---|
507 | <tr> |
---|
508 | <td colspan="1" id="_261" rowspan="1" style="width: 82.9333px; vertical-align: top;"> |
---|
509 | <p id="_262"> |
---|
510 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Prompots</span></p> |
---|
511 | </td> |
---|
512 | <td colspan="1" id="_263" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
513 | <p id="_264"> |
---|
514 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Chooses</span></p> |
---|
515 | </td> |
---|
516 | </tr> |
---|
517 | <tr> |
---|
518 | <td colspan="1" id="_265" rowspan="1" style="width: 82.9333px; vertical-align: top;"> |
---|
519 | <p id="_266"> |
---|
520 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Initiates</span></p> |
---|
521 | </td> |
---|
522 | <td colspan="1" id="_267" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
523 | <p id="_268"> |
---|
524 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Specifies</span></p> |
---|
525 | </td> |
---|
526 | </tr> |
---|
527 | <tr> |
---|
528 | <td colspan="1" id="_269" rowspan="1" style="width: 82.9333px; vertical-align: top;"> |
---|
529 | <p id="_270"> |
---|
530 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Submits</span></p> |
---|
531 | </td> |
---|
532 | <td colspan="1" id="_271" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
533 | <p id="_272"> |
---|
534 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Selects</span></p> |
---|
535 | </td> |
---|
536 | </tr> |
---|
537 | <tr> |
---|
538 | <td colspan="1" id="_273" rowspan="1" style="width: 82.9333px; vertical-align: top;"> |
---|
539 | <p id="_274"> |
---|
540 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Starts</span></p> |
---|
541 | </td> |
---|
542 | <td colspan="1" id="_275" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
543 | <p id="_276"> |
---|
544 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Displays</span></p> |
---|
545 | </td> |
---|
546 | </tr> |
---|
547 | <tr> |
---|
548 | <td colspan="1" id="_277" rowspan="1" style="width: 82.9333px; vertical-align: top;"> |
---|
549 | <p id="_278"> |
---|
550 | <span style="font-family: arial,sans-serif; font-size: 12pt;">Informs</span></p> |
---|
551 | </td> |
---|
552 | <td colspan="1" id="_279" rowspan="1" style="width: 100.8px; vertical-align: top;"> |
---|
553 | <p id="_280"> |
---|
554 | </p> |
---|
555 | </td> |
---|
556 | </tr> |
---|
557 | </tbody> |
---|
558 | </table> |
---|
559 | <p id="_281"> |
---|
560 | </p> |
---|
561 | <h4 id="_282"> |
---|
562 | <span><b><i>4.10.7.1 </i></b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b><i>Crosscheck with UI Prototype/ Design</i></b></span></h4> |
---|
563 | <p id="_283"> |
---|
564 | <span style="font-family: arial,sans-serif; font-size: 12pt;">The use case contents will be cross-checked against the UI Prototype/ Design to ensure no system require</span></p> |
---|
565 | <p id="_284"> |
---|
566 | <span style="font-family: arial,sans-serif; font-size: 12pt;">ments are missing from the use case or the UI Prototype/ Design. Where changes are required to the use case, the use case must be updated to reflect the UI design requirements. </span></p> |
---|
567 | <p id="_285"> |
---|
568 | </p> |
---|
569 | <h1 id="_286"> |
---|
570 | <span><b>5. </b></span><span style="font-family: arial,sans-serif; font-size: 12pt;"><b>Use Case Checkpoints</b></span></h1> |
---|
571 | <p id="_287"> |
---|
572 | <span>1. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question:</i> Is each concrete use case involved with at least one actor? </span></p> |
---|
573 | <p id="_288"> |
---|
574 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer</i>: If not, something is wrong; a use case that does not interact with an actor is superfluous, and you should remove it.</span></p> |
---|
575 | <p id="_289"> |
---|
576 | <span>2. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question</i>: Is each use case independent of the others? </span></p> |
---|
577 | <p id="_290"> |
---|
578 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If two use cases are always activated in the same sequence, you should probably merge them into one use case. </span></p> |
---|
579 | <p id="_291"> |
---|
580 | <span>3. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question</i>: For an included use case: does it make assumptions about the use cases that include it? </span></p> |
---|
581 | <p id="_292"> |
---|
582 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> Such assumptions should be avoided, so that the included use case is not affected by changes to the including use cases. </span></p> |
---|
583 | <p id="_293"> |
---|
584 | <span>4. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question:</i> Do any use cases have very similar behaviors or flows of events? </span></p> |
---|
585 | <p id="_294"> |
---|
586 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If so - and if you wish their behavior to be similar in the future - you should merge them into a single use case. This makes it easier to introduce future changes. Note: you must involve the users if you decide to merge use cases, because the users, who interact with the new, merged use case will probably be affected. </span></p> |
---|
587 | <p id="_295"> |
---|
588 | <span>5. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Has part of the flow of events already been modeled as another use case?</span></p> |
---|
589 | <p id="_296"> |
---|
590 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If so, you can have the new use case use the old one. </span></p> |
---|
591 | <p id="_297"> |
---|
592 | <span>6. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question:</i> Is some part of the flow of events already part of another use case? </span></p> |
---|
593 | <p id="_298"> |
---|
594 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If so, you should extract this subflow and have it be used by the use cases in question. Note: you must involve the users if you decide to "reuse" the subflow, because the users of the existing use case will probably be affected. </span></p> |
---|
595 | <p id="_299"> |
---|
596 | <span>7. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Should the flow of events of one use case be inserted into the flow of events of another? </span></p> |
---|
597 | <p id="_300"> |
---|
598 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If so, you model this with an extend-relationship to the other use case. </span></p> |
---|
599 | <p id="_301"> |
---|
600 | <span>8. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question</i>: Do the use cases have unique, intuitive, and explanatory names so that they cannot be mixed up at a later stage? </span></p> |
---|
601 | <p id="_302"> |
---|
602 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If not, you change their names. </span></p> |
---|
603 | <p id="_303"> |
---|
604 | <span>9. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Do customers and users alike understand the names and descriptions of the use cases? </span></p> |
---|
605 | <p id="_304"> |
---|
606 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> Each use-case name must describe the behavior the use case supports. </span></p> |
---|
607 | <p id="_305"> |
---|
608 | <span>10. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Does the use case meet all the requirements that obviously govern its performance? </span></p> |
---|
609 | <p id="_306"> |
---|
610 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> You must include any (nonfunctional) requirements to be handled in the object models in the use-case Special Requirements. </span></p> |
---|
611 | <p id="_307"> |
---|
612 | <span>11. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Does the communication sequence between actor and use case conform to the user's expectations? </span></p> |
---|
613 | <p id="_308"> |
---|
614 | <span>12. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Is it clear how and when the use case's flow of events starts and ends? </span></p> |
---|
615 | <p id="_309"> |
---|
616 | <span>13. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Behavior might exist that is activated only when a certain condition is not met. </span></p> |
---|
617 | <p id="_310"> |
---|
618 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> Is there a description of what will happen if a given condition is not met? </span></p> |
---|
619 | <p id="_311"> |
---|
620 | <span>14. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Are any use cases overly complex? </span></p> |
---|
621 | <p id="_312"> |
---|
622 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If you want your use-case model to be easy to understand, you might have to split up complex use cases. </span></p> |
---|
623 | <p id="_313"> |
---|
624 | <span>15. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Does a use case contain disparate flows of events? </span></p> |
---|
625 | <p id="_314"> |
---|
626 | <span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Answer:</i> If so, it is best to divide it into two or more separate use cases. A use case that contains disparate flows of events will be very difficult to understand and to maintain. </span></p> |
---|
627 | <p id="_315"> |
---|
628 | <span>16. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Is the subflow in a use case modeled accurately? </span></p> |
---|
629 | <p id="_316"> |
---|
630 | <span>17. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Is it clear who wishes to perform a use case? Is the purpose of the use case also clear? </span></p> |
---|
631 | <p id="_317"> |
---|
632 | <span>18. </span><span style="font-family: arial,sans-serif; font-size: 12pt;"><i>Question: </i>Does the brief description give a true picture of the use case?</span></p> |
---|
633 | <p id="_318"> |
---|
634 | </p> |
---|
635 | |
---|
636 | <p id="_1" style="text-align: center;"> |
---|
637 | <span style="font-family: times new roman,times,serif; font-size: 10pt;">7 of 15</span></p> |
---|
638 | |
---|
639 | |
---|
640 | <!--Section 0 end--> |
---|