ࡱ> KMJ#`  bjbj\.\. .*>D>DFdrrrrdNT,$Ih88M  SB<r c0T88 d d $8F Header Use Case IDUC FORMTEXT 01Use Case VersionV. FORMTEXT 1.0Status FORMDROPDOWN Release FORMTEXT Release IDAuthor FORMTEXT Your NameBodyTitle FORMTEXT Descriptive Title For The Use CaseActors FORMTEXT Primary Actor (Secondary Actors)Normal Flow FORMTEXT The main text that describes the most common flow of the use case. This is a paragraph-form, or bulleted list of steps. An informal use case has less structure than a formal use case. An informal use case is designed to be rapidly developed. Alternate Flows FORMTEXT A1. Alternate flow  "#$&':<=GHILMOUVWefgipqr|}~ĹȰĄȰj hg^UjL hg^Ujhg^Ujhg^UhXsmHnHujhg^UhXsjhXsUhF,EmHnHujnhg^UjhF,EUhF,EhhXshF,EB*ph4 (s $$Ifa$gdXszkd$$Ifl,""  t 0644 lap ytF,E$If ():N{o $$Ifa$gdXs$If}kd$$Ifl0," t0644 laytF,ENOVh{o $$Ifa$gdXs$If}kd$$Ifl0," t0644 laytF,Ehiq{o $$Ifa$gdXs$If}kd<$$Ifl0," t0644 laytF,Eym $$Ifa$gdXs$Ifkd $$Iflk0," t0644 laytXs{$If}kd, $$Ifl0,"  t0644 laytXs$Ifzkd $$Ifl,""  t 0644 lap ytXs {{$If}kd!$$Ifl0,"t$ t0644 layt%0  + , - 7 8 9 - . 1 B C D N O P b c e ضɣh*33hg^6<h*33h6<h%0mHnHujh%0Ujh%0Uh3C"jWhg^Uh%0hXsmHnHujhg^UhXsjhXsUhF,E , / 0 {{{$If}kd$$Ifl0,"t$ t0644 layt%00 1 A {$If}kd3$$Ifl0,"t$ t0644 layt%0A B C d $Ifjkd$$Ifl,"" t0644 layt%0d e y$a$gd}kd$$Ifl0,"t$ t0644 layt%0,1h/ =!"#$% l$$If!vh5"#v":Vl  t 65"p ytF,ELD 01##Enter a unque ID for the use case. Something like "UC01" works well for organizing and traceability. The "UC" is added automaticallyeEnter a unque ID for the use case. Something like "UC01" works well for organizing and traceability.c$$If!vh55 #v#v :Vl t655 ytF,EDuseCaseVersion1.0Versions can be used to track changes in use cases over time. You can use different versions of the same use case in different releases of your software. See http://tynerblain.com/blog/2006/12/12/incremental-delivery-and-use-cases/ for more detailsc$$If!vh55 #v#v :Vl t655 ytF,E8DstatusDraft: Use case is being defined Proposed: Use case is being reviewed Approved: Use case has been approved for the current release Rejected: Use case has been rejected <select a status>DraftProposedApprovedRejectedc$$If!vh55 #v#v :Vl t655 ytF,EBD releaseID Release IDYEnter the name or number that identifies the release that this use case is scheduled for.g$$If!vh55 #v#v :Vlk t655 ytXsDText2 Your Name-Enter the name of the author of the use case.q$$If!vh55 #v#v :Vl t655 / ytXsl$$If!vh5"#v":Vl  t 65"p ytXsDtitle"Descriptive Title For The Use CaseA good use case title describes the use case at a high level. It serves as a good reminder of what the use case represents. Additional details are found in the description.c$$If!vh5t5$#vt#v$:Vl t65t5$yt%0lDactors Primary Actor (Secondary Actors)The actor is the primary person who performs the use case. There can also be secondary actors. Use the role (e.g. Operations Manager), not the name of a person in the role. Include any secondary actors in parenthesisc$$If!vh5t5$#vt#v$:Vl t65t5$yt%0D descriptionThe main text that describes the most common flow of the use case. This is a paragraph-form, or bulleted list of steps. An informal use case has less structure than a formal use case. An informal use case is designed to be rapidly developed.Enter enough information to describe the process unambiguously. The flow you document should cover the most likely situation. Alternatives are used to cover variations on the use case.c$$If!vh5t5$#vt#v$:Vl t65t5$yt%0M$$If!vh5"#v":Vl t65"yt%0D alternateA1. Alternate flowThe most common flow is listed above in the normal flow. Add each variation here. Use the syntax A1. Description of alternate 1 A2. Description of alternate 2 etc This allows for tracing to either the normal flow (UC01) or an alternate (UC01A1)c$$If!vh5t5$#vt#v$:Vl t65t5$yt%0@@@ NormalCJ_HaJmH sH tH DAD Default Paragraph FontRi@R  Table Normal4 l4a (k(No Listj@j  Table Grid7:V0* ):OViq ,/1BC!     !LLLL!L ():NOVhiq ,/01ABCde0000 000 00000000 0 00 00 0 00 0 0 0 00 0 0 00 0 00 ():NOVhiq ,/01ABCde000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 00 0 0 0 0 0 00 (Nh 0 A d   #&<HLVfq},8-CObFFS FFFFFF useCaseIDText1useCaseVersionstatus releaseIDText2titleactors description alternate:<Vq,C <Mg.c'<MVgq +,.11:@ABCcdfkD 3C"9Z&%0N1*33x5F,Eg^o/Xs_ ():NOVhiq ,01ABCde@$&2-$$P@UnknownGz Times New Roman5Symbol3& z Arial" h Yr!r!Y#r4pp2HP)?x52Informal Use Case Template+Goal: Help people create informal use casesScott SehlhorstScott SehlhorstOh+'0$@h    Informal Use Case Template,Goal: Help people create informal use casesScott Sehlhorsthttp://tynerblain.com/blog Informal Use Case.20070119.dotScott Sehlhorst8Microsoft Office Word@xA@X9^8<@NB<rG"VT$m ;q  ."System&&9* - - @ !s+\-  - @ !s+\-  - @ !s\- @Times New Roman- 2 )Header H,,2-! 2 ') 3 - @ !X-- @ !X-- @ !fX-- @ !X)-- @ !X)-- @ !s\-- @ !s\)-2 - L Use Case IDH',C,', H 2 -L  32 -P )UCHC2 -P )0122 2 -P ) 2- @ !-- @ ! -- @ !L -- @ !P -- @ !)-- @ !s-- @ !sL -- @ !s)-#2 L Use Case VersionH',C,',I,!'22 2 L  32  P )V.H2 P )1.022 2 P ) 2- @ !F-- @ ! F-- @ !FL -- @ !FP -- @ !F)-- @ !sJ-- @ !sJL -- @ !sJ)-2 L Status8,2' 2 L  2)P @Times New Roman-)P %2 iP )