ࡱ> uwt5@ .bjbj22 U\XXW%v $ """P"D6#l Q#%>&>&>&>&+t-$Q&Q&Q&Q&Q&Q&Q$SRUJQ P.>&>&P.P.JQ >&>&_Q000P.F >& >&$Q0P.$Q0n00:K hO>&# k} ".M<OuQ0Q0N8V.VxhO V hO P.P.0P.P.P.P.P.JQJQ "x0 " SUBJECT \* MERGEFORMAT  title \* Mergeformat Use-Case Specifications Version <1.0> [Note: The following template is provided for use with the Unified Process for EDUcation. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).] [To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.] Revision History DateVersionDescriptionAuthor

 Table of Contents  TOC \o "1-3" 1. Use-Case Model  PAGEREF _Toc5112018 \h 4 1.1 Introduction  PAGEREF _Toc5112019 \h 4 1.2 General Actors Descriptions  PAGEREF _Toc5112020 \h 4 1.3 Use-Case Model Hierarchy  PAGEREF _Toc5112021 \h 4 1.3.1  PAGEREF _Toc5112022 \h 4 1.3.2  PAGEREF _Toc5112023 \h 5 1.4 Diagrams of the Use-Case Model  PAGEREF _Toc5112024 \h 5 2.  PAGEREF _Toc5112025 \h 5 2.1 Brief Description  PAGEREF _Toc5112026 \h 5 2.2 Flow of Events  PAGEREF _Toc5112027 \h 5 2.2.1 Basic Flow  PAGEREF _Toc5112028 \h 5 2.2.2 Alternative Flows  PAGEREF _Toc5112029 \h 6 2.3 Special Requirements  PAGEREF _Toc5112030 \h 6 2.3.1 < First Special Requirement >  PAGEREF _Toc5112031 \h 6 2.4 Preconditions  PAGEREF _Toc5112032 \h 6 2.4.1 < Precondition One >  PAGEREF _Toc5112033 \h 6 2.5 Postconditions  PAGEREF _Toc5112034 \h 6 2.5.1 < Postcondition One >  PAGEREF _Toc5112035 \h 6 2.6 Extension Points  PAGEREF _Toc5112036 \h 6 2.6.1  PAGEREF _Toc5112037 \h 6 2.7 Relationships  PAGEREF _Toc5112038 \h 6 2.8 Use-Case Diagrams  PAGEREF _Toc5112039 \h 7 2.9 Other Diagrams  PAGEREF _Toc5112040 \h 7 3.  PAGEREF _Toc5112041 \h 8 3.1 Brief Description  PAGEREF _Toc5112042 \h 8  title \* Mergeformat Use-Case Specifications [The following template is provided for the Use-Case Specifications, which contains the textual properties of the use case. The use-case diagrams can be developed in a visual modeling tool, such as Rational Rose. A use-case report, with all properties, may be generated with Rational SoDA. ] Use-Case Model [This section contains an overview of the use-case model. This includes a list of names and brief descriptions of all use cases and actors, along with applicable diagrams and relationships. Refer to the Use-Case-Model Survey Report.] Introduction [Introduction to the use-case model] General Actors Descriptions [List Project actors and provide a brief description (role played).] Use-Case Model Hierarchy [This section presents the use-case packages hierarchically, explains the dependencies among them, and shows the content of each package recursively. If the model has several levels of packages, those at the top-level are presented first. The packages within these are presented next, and so on, all the way down to the packages at the bottom of the hierarchy. Description A Brief Description explaining the package's function and role in the system. The description must be understandable to any developer who wants to use the package. Use Cases A list of the use cases owned by the package (name only since descriptions and details are shown further in this document Actors A list of actors owned by the package, including the name and brief description (role involved) of each actor in this package RelationShips A list of relationships owned by the package, including the name and brief description of each relationship. Packages Owned A list of the packages directly owned by the package, with each package presented in the same hierarchical manner as shown in the Packages Diagram below. Packages Diagram [Include the Package Diagrams (Including a visual representation of the sub packages it owns] Description Use Cases Actors RelationShips [...] [...] Diagrams of the Use-Case Model [Diagrams, primarily use-case diagrams and use-case packages, of the entire use-case model are included here. If you are including use-case diagrams directly within each use-case section or subsection, briefly state so] Brief Description [The description briefly conveys the role and purpose of the use case. A single paragraph will suffice for this description.] Flow of Events Basic Flow [This use case starts when the actor does something. An actor always initiates use cases. The use case describes what the actor does and what the system does in response. It is phrased in the form of a dialog between the actor and the system. The use case describes what happens inside the system, but not how or why. If information is exchanged, be specific about what is passed back and forth. For example, it is not very illuminating to say that the actor enters customer information. It is better to say the actor enters the customers name and address. A Glossary of Terms is often useful to keep the complexity of the use case manageable(you may want to define things like customer information there to keep the use case from drowning in details. Simple alternatives may be presented within the text of the use case. If it only takes a few sentences to describe what happens when there is an alternative. Do it directly within the Flow of Events section. If the alternative flow is more complex, use a separate section to describe it. For example, an Alternative Flow subsection explains how to describe more complex alternatives. A picture is sometimes worth a thousand words, though there is no substitute for clean, clear prose. If it improves clarity, feel free to paste graphical depictions of user interfaces, process flows or other figures into the use case. If a flow chart is useful to present a complex decision process, by all means use it! Similarly for state-dependent behavior, a state-transition diagram often clarifies the behavior of a system better than pages upon pages of text. Use the right presentation medium for your problem, but be wary of using terminology, notations or figures that your audience may not understand. Remember that your purpose is to clarify, not obscure.] Alternative Flows < First Alternative Flow > [More complex alternatives are described in a separate section, referred to in the Basic Flow subsection of Flow of Events section. Think of the Alternative Flow subsections like alternative behavior( each alternative flow represents alternative behavior usually due to exceptions that occur in the main flow. They may be as long as necessary to describe the events associated with the alternative behavior. When an alternative flow ends, the events of the main flow of events are resumed unless otherwise stated.] < Second Alternative Flow > [There may be, and most likely will be, a number of alternative flows in a use case. Keep each alternative flow separate to improve clarity. Using alternative flows improves the readability of the use case, as well as preventing use cases from being decomposed into hierarchies of use cases. Keep in mind that use cases are just textual descriptions, and their main purpose is to document the behavior of a system in a clear, concise, and understandable way.] Special Requirements [A special requirement is typically a nonfunctional requirement that is specific to a use case, but is not easily or naturally specified in the text of the use cases event flow. Examples of special requirements include legal and regulatory requirements, application standards, and quality attributes of the system to be built including usability, reliability, performance or supportability requirements. Additionally, other requirements(such as operating systems and environments, compatibility requirements, and design constraints(should be captured in this section.] < First Special Requirement > Preconditions [A precondition of a use case is the state of the system that must be present prior to a use case being performed.] < Precondition One > Postconditions [A postcondition of a use case is a list of possible states the system can be in immediately after a use case has finished.] < Postcondition One > Extension Points [Extension points of the use case.] [Definition of the location of the extension point in the flow of events.] Relationships [The relationships involving the use case are included here. For communicates-associations, a brief description, multiplicity, and associated actors are included. Also, the navigability of the use-case role is included. For include- and extend-relationships, a brief description and associated use cases are included. ] Use-Case Diagrams [Use-Case Diagrams local to the use case.] Other Diagrams [Other graphs that illustrate the use case.] Brief Description [....]  DOCPROPERTY "Company" \* MERGEFORMAT  subject \* Mergeformat  Version: <1.0>title \* Mergeformat Use-Case Specifications Date:
 Confidentialsymbol 211 \f "Symbol" \s 10 DOCPROPERTY "Company" \* MERGEFORMAT ,  DATE \@ "yyyy" 2002Page page 7 )*+,BCZ[]kG g        ! " > ? W X Y Z [ \ _ ` y z jh=ChhUj/h=ChhUh=CmHnHujh=ChhUh=ChhCJaJh=ChhaJh=Chh5h=ChhCJ h=Chhjh=ChhU7+\]kl 2 3 4 5 6 G L T ` g $$Ifa$.$a$W-.g h t z lffff$Ifkd$$Ifl\ $  04 la lffff$Ifkd$$Ifl\ $  04 la lffff$Ifkd|$$Ifl\ $  04 la lffff$Ifkd:$$Ifl\ $  04 la  \ ljhb\\\VV @  kd$$Ifl\ $  04 la      01IJKLMNPQ`abz{|}~˽˯ˡҘҘˊjh=ChhUh=ChhaJjh=ChhUjh=ChhUjh=ChhU h=Chhh=ChhCJaJh=CmHnHujh=ChhUj!h=ChhU3 NI+\7k56ZiUb. @  +,DEFGHILMbc{|}~˽˯ˡ˓˅j h=ChhUjb h=ChhUjh=ChhUjph=ChhUjh=ChhU h=Chhh=ChhCJaJh=CmHnHujh=ChhUj~h=ChhU4 &'()*+./>?WXYZ[\abxyٽٯ١ٓj8 h=ChhUj h=ChhUjF h=ChhUj h=ChhUjT h=ChhU h=Chhh=ChhCJaJjh=ChhUh=CmHnHu:  234567:;MNfghijkno~˽˯ˡҘҘˊjh=ChhUh=ChhaJjh=ChhUj h=ChhUj* h=ChhU h=Chhh=ChhCJaJh=CmHnHujh=ChhUj h=ChhU3236Rjk2==K Dc;>~3 - ##溰|h=Ch=C5\h=C jh=Chhh=Chh0J15\ h=Ch=Ch=ChhCJh=Chh5\ h=Chh!jh=ChhCJOJQJUh=ChhCJaJh=CmHnHujh=ChhUjh=ChhU0bk3==Kabs2 & F 2 & F^2.!'>Dc?@Pbn ##9#<%X%$'9's))))*)*.#####$$((M)N)W-Y-Z----------------- . .G.H.I.e.f.g.i...............Ϲߵ߭ hh0Jjhh0JUh=CmHnHuhhOJQJh=CjhhUhhh=C5CJ$OJQJhh5CJ$OJQJjhh5CJ$OJQJU hhCJ jh=Chhh=Chh5\ h=Chh4)*8****++e+s++P,,,,--->-P-W-X-Y----- $&dPa$ $dN.---- .!.|lkd$$Ifl0$k 04 la oD($If]D$If!.".8.9.:.;.20.Ykd$$Ifl$V%04 la$Iflkd$$Ifl0$k 04 la;.H........ca__].kd'$$IflF H$Z Z Z 0    4 la $$Ifa$ $$Ifa$ h$If]h..... h=Chhhhjhh0JUh=C0JmHnHu*0PBP/ =!"#$%0'0 PBP/ =!"#$%$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4yDyK  _Toc5112018yDyK  _Toc5112019yDyK  _Toc5112020yDyK  _Toc5112021yDyK  _Toc5112022yDyK  _Toc5112023yDyK  _Toc5112024yDyK  _Toc5112025yDyK  _Toc5112026yDyK  _Toc5112027yDyK  _Toc5112028yDyK  _Toc5112029yDyK  _Toc5112030yDyK  _Toc5112031yDyK  _Toc5112032yDyK  _Toc5112033yDyK  _Toc5112034yDyK  _Toc5112035yDyK  _Toc5112036yDyK  _Toc5112037yDyK  _Toc5112038yDyK  _Toc5112039yDyK  _Toc5112040yDyK  _Toc5112041yDyK  _Toc5112042$$If!vh55k #v#vk :V l055k 4$$If!vh55k #v#vk :V l055k 4z$$If!vh5V%#vV%:V l05V%4$$If!vh5Z 5Z 5Z #vZ :V l05Z / 43B@B Normal 1$d_HmH sH tH d@d Heading 1'$ & F0x<@&^`05CJOJQJ<@< Heading 2  & F@&CJB@B Heading 3  & F@& 56CJ@@@ Heading 4  & F@&5CJL@L Heading 5 & F@ <@&^@ CJP@P Heading 6 & F@ <@&^@ 6CJH@H Heading 7 & F@ <@&^@ L@L Heading 8 & F@ <@&^@ 6R @R Heading 9 & F@ <@&^@ 56CJDA@D Default Paragraph FontVi@V  Table Normal :V 44 la (k@(No List POP Paragraph2$P^a$B*mH sH uB>@B Title$da$5CJ$OJQJPJ@P Subtitle $<a$6CJ$OJQJmH sH uF@"F Normal Indent|^`|>@> TOC 1 $<]>@> TOC 2 $]^:@: TOC 3 $`^`4@b4 Header  !4 @r4 Footer  !.)@. Page NumberHOH Paragraph3$dP^a$HOH Paragraph4$dP^a$6O6 Tabletext $x>B@> Body Text$x^.. TOC 4 X^X.. TOC 5  ^ .. TOC 6 ^.. TOC 7 ^.. TOC 8 !x^x.. TOC 9 "@^@O2 Bullet1p# & FP>T?^`POB Bullet2p$ & F>Th?^`B* @YR@  Document Map%-D OJQJD&aD Footnote ReferenceCJH*frf  Footnote Text&'$$h((&d^h` CJOJQJXOX Main Title($d<a$5CJ KHOJQJ@O@ Paragraph1)$dPa$8P@8 Body Text 2*6B*NC@N Body Text Indent +^ 6>*B*HOH Body,$dx1$a$OJQJtH ubOb Bullet4-$ & FQ hdx1$]h^a$OJQJ>O> InfoBlue.x^6B*0U@0 Hyperlink>*B*T^@T Normal (Web)0ddd1$[$\$CJaJ*W@* Strong5\8O"8 Body Text2 2 & F6&\,\+\]kl23456GLT`ghtz\ NI+\ 7 k  5 6 Z i U b  k3==Kabs!'>Dc?@Pbn 9<X$9s!!!!")"8""""##e#s##P$$$$%-%>%P%W%X%Y%%%%%%%% &!&"&8&9&:&;&H&&&&&&&00000.0.0000000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0000000000000000000000000000.0.0.0 0.0Z  0Z Z .0U  0Z Z .0  0Z Z .0 ( 0 0k 20k.0k 20k.0k 20k.0k 20k.0k 20k.0k20k8 0kk.0b8 0kk 20 20 20 20208 0kk.0( 0 .0' 0Z Z .0D0D 0 0@@.0P 0@@( 0.0.0.08.0( 08 0  .08 0  .0< 0@@.0$( 0$$0s! 0@@.0!( 0!! 0@@.0)"( 0)")" 0@@.0"( 0"".0# 0@@.0e#.0e#.0e# 0@@.0$ 0@@.0$ 0 0-%-%.0>%@0@0@0@0@0@0@0 @0 @0 @0 @0 @0 @0 @0 @0@0@0 @0 @0 @0 @0@0 0.Pu >>>>>>uuux #.. "#$%(-g b)*-!.;..!&')*+,.)+BZ>XZy  0JLa{}+EGb|~ ')>XZx   3 5 M g i ~    2 & %t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t%t*9>Wf9HK\ahnpxU9UT!6 _Toc423410237 _Toc425054503 _Toc423410238 _Toc425054504 _Toc492796464 _Toc3287869 _Toc5112018 _Toc5112019 _Toc5108141 _Toc5112020 _Toc5112021 _Toc5112022 _Toc5112023 _Toc5112024 _Toc5112025 _Toc5112026 _Toc423410239 _Toc425054505 _Toc5112027 _Toc423410240 _Toc425054506 _Toc5112028 _Toc423410241 _Toc425054507 _Toc5112029 _Toc423410242 _Toc425054508 _Toc423410243 _Toc425054509 _Toc423410251 _Toc425054510 _Toc5112030 _Toc423410252 _Toc425054511 _Toc5112031 _Toc423410253 _Toc425054512 _Toc5112032 _Toc423410254 _Toc425054513 _Toc5112033 _Toc423410255 _Toc425054514 _Toc5112034 _Toc423410256 _Toc425054515 _Toc5112035 _Toc5112036 _Toc5112037 _Toc5112038 _Toc5112039 _Toc5112040 _Toc5112041 _Toc51120423 3 Z Z Z Z Z U k'D@P   <<$$$s!s!s!!!!""")")")"""""#e#$$.%>%&   !"#$%&'()*+,-./0123454 4 h h h a =bOaaa88WW888!!!!!!("("("7"7"7"""""#r#$$=%O%&W%Y%%%%% &h&&&&W%&&>[y 0Ma~+Hb *>[x  6 M j ~ ;>3W%Y%%%%%%% &"&9&H&&&&&&&&&W%&& dgawnedgawnedgawnedgawnedgawne UPEDU Team SG" m%_p  5' 2m :D" NcK- E,1 Q+2 Hu3}tqT6 2g=nZV{B c]ExzpI +sdO NsR $W)X;sHC[^F}/m *q 6t Pau Q{{Ic4{ @.@.@..@...@ ....@ .....@ ......@ .......@ ........* hh^h`OJQJo(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo( hh^h`OJQJo(h 88^8`OJQJo(h ^`OJQJo(oh   ^ `OJQJo(h   ^ `OJQJo(h xx^x`OJQJo(oh HH^H`OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(h^`.h^`.hpLp^p`L.h@ @ ^@ `.h^`.hL^`L.h^`.h^`.hPLP^P`L. hh^h`OJQJo(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo(h^`CJOJQJo(h pp^p`OJQJo(oh @ @ ^@ `OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h PP^P`OJQJo(oh   ^ `OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo( hh^h`OJQJo(.Hu34{NsR+sdO$.SG"Paup qT6Q+26tE,1m*qpI:D"{BNcK-F}/m$W)Xc]EQ{{2g=mHC[5' .@h 8^8`OJQJo(0. @h ^`OJQJo(xd%5CTR!0F\D4:3d\N.n2 6                 p&R^iT~ H?@A?hN:j!_,hNxڌp&        ~,,j/Aw\ hlL9An=Ch6GLT`ghtzd#$$%O%Q%V%W%%%%% &!&"&8&9&:&;&H&&&&&@-%-% j0-%-%&@UnknownGz Times New Roman5Symbol3& z Arial5& z!Tahoma;& z HelveticaABook Antiqua?5 z Courier New;Wingdings"hM3fM3fCC!r4dD%D% 3QH(?>=CUse-Case Specifications<Project Name>Christian Robidoux UPEDU Teamx                      Oh+'0 $ 8D ` l x Use-Case SpecificationsiChristian Robidouxihrihri upedu_ucspecido UPEDU Teamc2EDMicrosoft Word 10.0@F#@@h} @h} ՜.+,0 px  dCD%A Use-Case Specifications Title  !"#$%&'()*+,-.012345679:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcefghijkmnopqrsvRoot Entry F[k} xData /1Table8WWordDocumentU\SummaryInformation(dDocumentSummaryInformation8lCompObjj  FMicrosoft Word Document MSWordDocWord.Document.89q