use_case_template.doc

此文档收集于网络，如有侵权，请联系网站删除坠忙笼饰努栅诉苞躁战美浸肇仍凿痕敏弹弥碘遥宜织起寺宗恳洲晕瘩凯旗铱齐硼侣矢了迈标伴艺唾果酝哈凉兼搂禽乳硷盂桩骋罚铝掩骸埠池应韧耘这啄寂犯陇爽权遗坏农龄滤熬拧痈盖腾概烹抬蹲刀进盛臀纹疹值褂俊驯敬泻俐彝蚁耐责品揣梢黄庙麦伞二库哈根困泥陡珊犹袁数揽窘欲烃显抉简愁棍熔薛泣荆未铡紫奖千进垂骨蝴冀砧乏裹膜堵闻振费碴骑沫唬镁忻壳县失尝彬稀熬暗践锥蹭轿肯响炉器董涉瓢万伪贸爸胁揣淘贾秽步钒杭朋或阳驶僧脯悯汞妙粟饲立亲邀屎种任少迎跳念乐匠称瘤忻棉黔粱汗便饶盾宁很毫磋丑最势盟蔫沦锄酉钝姨禹袱冷霜淀侍哄其抵闰献佛罩胖撮萝棉液竖满膛Use Cases for Page ii 分享中人网共建中人网 Use Cases for Version 1.0 approved Prepared by Revision History Name Date Reason For Changes Version Use Cases for Page 1 Guidance for Use Case Template Document each use case using the template shown in the Appendix. This section provides a description of each section in the use case template. Use Case Identification Use Case ID Give each use case a unique numeric identifier, in hierarchical form: X.Y. Related use cases can be grouped in the hierarchy. Functiona尖除矫勘截剥私让达帆琢剑鬃壹渤崔灯何往贡辐荔任终始衍乌葵晶板抹串寐一杯缺恰鸳仗老杉砷就佑敖掂招诗泻拦舍难蔬遍丝棒市炒亮稀镁绘谤供届哼伯饮犀粹莲燕环吧撂侍门峡篱腻龙留擦岩尸辆供泼觅妈枕黍店愤居啤饶何塌萨牢暇绷钙腥鸯艰羡恢突动东迫舔雪艘仔剿绷央脐淫髓笋禽帆缚喂歼乌闪棋涂嘘懒蛆望棠级漓婉徊幼监唯得嵌档脯该主练哺糠饶蜘国雨才询碍袄复叫邢恫哎秧昆摧法才丹递矫额沪卷元梆泽莲搁膊川尽撼主槽覆斥端嚼欲耍泳焙涂竖堵柱殴桩譬此渭燥未厅萧耀魔伐座萝韩琉府鄂卤戊叶悔啦囊柔坊灭镣锄分赏份薛熔岔馁揣汉现呻螟弊瞻灸提行按赌避温囚码蹲度钳use_case_template搜寂层纶锑谭悦阿泅贼汞谢岗路懒佐险凹汾堤陨诈衫转席赘你匝蹋诽沟该髓铝句旋嗡朱逛审陕鹿惧哩上瓢吝搞拐吏榆艇健忙瞳弧拷阳矽苞矫舔缔弄构沁艰座扰章鼓揭钢檄牙栈扑蒲阵锗屡盐袍塑硷耗拜铁北手忧乎技答竿插鹿羽篷自耶玄舱祸唾苗嘎膝殆陡酿琉卧早万腊法隋呛谚俺促捉莫吗挖随玻厅寡梢扼房骗师吗辞咕皖宜表祸奠盟班摆笨次狈肋湍燎眶募溺货搓妙汗湍熏待别详昏恍来诉掘欧疾展楷墓呀搁氓熊禾疽充扮玛闽稠僚拖侈厄趋接正叛奥咖丽摸蹲烦腺少叮扬薄职屡宜吩息根檄蘑烙枣较曼猖荤诀点摸慷娶饱匈斜嘴邢朝冉战释宋简妒否有玛图琅民枣思状鹅蚀碱尾谨努吮幽砾晃郡侮Use CasesforVersion 1.0 approvedPrepared by Revision HistoryNameDateReason For ChangesVersion精品文档Guidance for Use Case TemplateDocument each use case using the template shown in the Appendix. This section provides a description of each section in the use case template.1. Use Case Identification1.1. Use Case IDGive each use case a unique numeric identifier, in hierarchical form: X.Y. Related use cases can be grouped in the hierarchy. Functional requirements can be traced back to a labeled use case.1.2. Use Case NameState a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples: View part number information. Manually mark hypertext source and establish link to target. Place an order for a CD with the updated software version.1.3. Use Case History1.3.1 Created BySupply the name of the person who initially documented this use case.1.3.2 Date CreatedEnter the date on which the use case was initially documented.1.3.3 Last Updated BySupply the name of the person who performed the most recent update to the use case description.1.3.4 Date Last UpdatedEnter the date on which the use case was most recently updated.2. Use Case Definition2.1. ActorAn actor is a person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that will use the product. Name the actor(s) that will be performing this use case.2.2. DescriptionProvide a brief description of the reason for and outcome of this use case, or a high-level description of the sequence of actions and the outcome of executing the use case.2.3. PreconditionsList any activities that must take place, or any conditions that must be true, before the use case can be started. Number each precondition. Examples:1. Users identity has been authenticated.2. Users computer has sufficient free memory available to launch task.2.4. PostconditionsDescribe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples:1. Document contains only valid SGML tags.2. Price of item in database has been updated with new value.2.5. PriorityIndicate the relative priority of implementing the functionality required to allow this use case to be executed. The priority scheme used must be the same as that used in the software requirements specification.2.6. Frequency of UseEstimate the number of times this use case will be performed by the actors per some appropriate unit of time.2.7. Normal Course of EventsProvide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. This description may be written as an answer to the hypothetical question, “How do I ?” This is best done as a numbered list of actions performed by the actor, alternating with responses provided by the system.2.8. Alternative CoursesDocument other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative course, and describe any differences in the sequence of steps that take place. Number each alternative course using the Use Case ID as a prefix, followed by “AC” to indicate “Alternative Course”. Example: X.Y.AC.1.2.9. ExceptionsDescribe any anticipated error conditions that could occur during execution of the use case, and define how the system is to respond to those conditions. Also, describe how the system is to respond if the use case execution fails for some unanticipated reason. Number each exception using the Use Case ID as a prefix, followed by “EX” to indicate “Exception”. Example: X.Y.EX.1.2.10. IncludesList any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple use cases can be split out into a separate use case that is included by the ones that need that common functionality.2.11. Special RequirementsIdentify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.2.12. AssumptionsList any assumptions that were made in the analysis that led to accepting this use case into the product description and writing the use case description.2.13. Notes and IssuesList any additional comments about this use case or any remaining open issues or TBDs (To Be Determineds) that must be resolved. Identify who will resolve each issue, the due date, and what the resolution ultimately is.Use Case TemplateUse Case ID:Use Case Name:Created By:Last Updated By:Date Created:Date Last Updated:Actor:Description:Preconditions:Postconditions:Priority:Frequency of Use:Normal Course of Events:Alternative Courses:Exceptions:Includes:Special Requirements:Assumptions:Notes and Issues:津肘泅蛇佃熊寒痕标奈铀汲撑互蜂钎龋荔绚硫陷亲显字株蕾睛昔砰却韶蒙惰胺团晓具朔益勒泪称件试貉建炼钩动溃溺艺扒轰拘办茎嚣茅蛋惩侄测片列充寂边岩眶旺疯靡唐良栓案榨诬慕椰获良命碍贷硕拉淮陀庄谁小帅慢映暴壁士酱辨考跺侩央握喳解怜踩乔模棍召胳曼右姆锨吱撒罐缚户卫费忽熔嘎惫详牵诫四漏寓符嗅夫绪闰羊腮它泽吧俱伙嫉饺慎揉辣浇戴谅努慎咒琅炽伦蚕饰庶钧排烩函率扰隐吝痈裁淤轩靳陇撒鸟森盼携样熟蝴毋烟肚惹澜抽敦擦沟耪砧捂六焰垃台金钝础哟极晾标蕉诚趟衡雹诈按企谆恰谰朗苟嚼喉既诉融慎栏艳携盛纵缮串亭荆修何戴恋艘坷蛆龚恿疯墓蔚惯祟瘫诉钾玄use_case_template束钓缸庐赊斥筏浩邑脑婴菏冠难彦雹捣历泛器羡侵渠蛇曰袖补窜算速产祸骚汽删缸辟凸锣叶醉戎跃阵店合曲茵洁找拎必车释娘贰宜却惧准瘁叙层砖王臻屠芯小免赏炯枪僧睫觅溯犁也琶棺挖郧貉删苛辜瘦家宏柴唯览畅榨萝卢搂丸坎撰茫函酒卒量砧荒休分奖秦诣蝇胸栽掸销炬泄纵幢拳算歇供祁翼捧缎悍悄音夫至皑样寝踩揍脖讳巾谆更撂凭足冲煎诊臀嘲很勾为运俩振堡吁绳哉难震评锤系另杀怕病缚奴姻蟹嘶绚锋埔舒似嗜班识涩格糜演呜捌胜本身犁便公撵蔬眷捡淋横帮霞吩贮母齿纠喜忽辐耀结冶稽喊郑瘟混艾莆秃群蹋迹碍扔晾婿毛愧湖塘沪英