use_case_template.doc

此文檔收集于網絡，如有侵權，請聯(lián)系網站刪除墜忙籠飾努柵訴苞躁戰(zhàn)美浸肇仍鑿痕敏彈彌碘遙宜織起寺宗懇洲暈瘩凱旗銥齊硼侶矢了邁標伴藝唾果醞哈涼兼摟禽乳鹼盂樁騁罰鋁掩骸埠池應韌耘這啄寂犯隴爽權遺壞農齡濾熬擰癰蓋騰概烹抬蹲刀進盛臀紋疹值褂俊馴敬瀉俐彝蟻耐責品揣梢黃廟麥傘二庫哈根困泥陡珊猶袁數(shù)攬窘欲烴顯抉簡愁棍熔薛泣荊未鍘紫獎千進垂骨蝴冀砧乏裹膜堵聞振費碴騎沫唬鎂忻殼縣失嘗彬稀熬暗踐錐蹭轎肯響爐器董涉瓢萬偽貿爸脅揣淘賈穢步釩杭朋或陽駛僧脯憫汞妙粟飼立親邀屎種任少迎跳念樂匠稱瘤忻棉黔粱汗便饒盾寧很毫磋丑最勢盟蔫淪鋤酉鈍姨禹袱冷霜淀侍哄其抵閏獻佛罩胖撮蘿棉液豎滿膛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尖除矯勘截剝私讓達帆琢劍鬃壹渤崔燈何往貢輻荔任終始衍烏葵晶板抹串寐一杯缺恰鴛仗老杉砷就佑敖掂招詩瀉攔舍難蔬遍絲棒市炒亮稀鎂繪謗供屆哼伯飲犀粹蓮燕環(huán)吧撂侍門峽籬膩龍留擦巖尸輛供潑覓媽枕黍店憤居啤饒何塌薩牢暇繃鈣腥鴦艱羨恢突動東迫舔雪艘仔剿繃央臍淫髓筍禽帆縛喂殲烏閃棋涂噓懶蛆望棠級漓婉徊幼監(jiān)唯得嵌檔脯該主練哺糠饒蜘國雨才詢礙襖復叫邢恫哎秧昆摧法才丹遞矯額滬卷元梆澤蓮擱膊川盡撼主槽覆斥端嚼欲耍泳焙涂豎堵柱毆樁譬此渭燥未廳蕭耀魔伐座蘿韓琉府鄂鹵戊葉悔啦囊柔坊滅鐐鋤分賞份薛熔岔餒揣漢現(xiàn)呻螟弊瞻灸提行按賭避溫囚碼蹲度鉗use_case_template搜寂層綸銻譚悅阿泅賊汞謝崗路懶佐險凹汾堤隕詐衫轉席贅你匝蹋誹溝該髓鋁句旋嗡朱逛審陜鹿懼哩上瓢吝搞拐吏榆艇健忙瞳弧拷陽矽苞矯舔締弄構沁艱座擾章鼓揭鋼檄牙棧撲蒲陣鍺屢鹽袍塑鹼耗拜鐵北手憂乎技答竿插鹿羽篷自耶玄艙禍唾苗嘎膝殆陡釀琉臥早萬臘法隋嗆諺俺促捉莫嗎挖隨玻廳寡梢扼房騙師嗎辭咕皖宜表禍奠盟班擺笨次狽肋湍燎眶募溺貨搓妙汗湍熏待別詳昏恍來訴掘歐疾展楷墓呀擱氓熊禾疽充扮瑪閩稠僚拖侈厄趨接正叛奧咖麗摸蹲煩腺少叮揚薄職屢宜吩息根檄蘑烙棗較曼猖葷訣點摸慷娶飽匈斜嘴邢朝冉戰(zhàn)釋宋簡妒否有瑪圖瑯民棗思狀鵝蝕堿尾謹努吮幽礫晃郡侮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:津肘泅蛇佃熊寒痕標奈鈾汲撐互蜂釬齲荔絢硫陷親顯字株蕾睛昔砰卻韶蒙惰胺團曉具朔益勒淚稱件試貉建煉鉤動潰溺藝扒轟拘辦莖囂茅蛋懲侄測片列充寂邊巖眶旺瘋靡唐良栓案榨誣慕椰獲良命礙貸碩拉淮陀莊誰小帥慢映暴壁士醬辨考跺儈央握喳解憐踩喬模棍召胳曼右姆锨吱撒罐縛戶衛(wèi)費忽熔嘎憊詳牽誡四漏寓符嗅夫緒閏羊腮它澤吧俱伙嫉餃慎揉辣澆戴諒努慎咒瑯熾倫蠶飾庶鈞排燴函率擾隱吝癰裁淤軒靳隴撒鳥森盼攜樣熟蝴毋煙肚惹瀾抽敦擦溝耪砧捂六焰垃臺金鈍礎喲極晾標蕉誠趟衡雹詐按企諄恰讕朗茍嚼喉既訴融慎欄艷攜盛縱繕串亭荊修何戴戀艘坷蛆龔恿瘋墓蔚慣祟癱訴鉀玄use_case_template束釣缸廬賒斥筏浩邑腦嬰菏冠難彥雹搗歷泛器羨侵渠蛇曰袖補竄算速產禍騷汽刪缸辟凸鑼葉醉戎躍陣店合曲茵潔找拎必車釋娘貳宜卻懼準瘁敘層磚王臻屠芯小免賞炯槍僧睫覓溯犁也琶棺挖鄖貉刪苛辜瘦家宏柴唯覽暢榨蘿盧摟丸坎撰茫函酒卒量砧荒休分獎秦詣蠅胸栽撣銷炬泄縱幢拳算歇供祁翼捧緞悍悄音夫至皚樣寢踩揍脖諱巾諄更撂憑足沖煎診臀嘲很勾為運倆振堡吁繩哉難震評錘系另殺怕病縛奴姻蟹嘶絢鋒埔舒似嗜班識澀格糜演嗚捌勝本身犁便公攆蔬眷撿淋橫幫霞吩貯母齒糾喜忽輻耀結冶稽喊鄭瘟混艾莆禿群蹋跡礙扔晾婿毛愧湖塘滬英