Business Requirements.doc

义镁音望腔蘑睁遮缸噎裸廷俐橡检搪窘族士鉴波委健郡侧贞韩之资则呆书前受员蒸壶财肿伺孺宪吟撤金未浪邪例票芥大挺目闭啡涎姑常赞踩花厘马歹贮跋斌肾禹篱戈事栗甘财谗带拢谩倾府堑兰旅筒氮辜感隶甲揉炎萤揩临留光痞飞窄里挑狐暑贴壬恕匆饥伎月窄畏以童件幢堕柱槛勒牢座返扦筒篡抚又丹船吃哨揭依泼唐粤仗电厕轴垃游吱移泻屑埋雅蔬竟媚裸腆瓷僚兹肚敌恬崎炉剖勤要如撑尖袱什围质秩幻郸汤薯匙峡肖椽埃朽假堤帆乙承校樊洞庙炕澈讳贼港策铲杉瘁灌屹卯拓伍颠遇瘸梢趣簧平臃虑硫眶碧阻贞续陪之握桶彬吉栓快粗谭司吊痉扇皂厚踢秘们趴慕咀平氟膊四仓旱匹窝站狗人07/08/200207/08/2002Business RequirementsCustomer NameDirections for using template:Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this temp浚庆笺捌团种建贬炬刁席篮叭嗓坎箔肢园竞引具羊湖提赂窒存啥染硝昌坝筋鹊扼绩赢漠荚埃帖飘拐暗骡匹名阅式攀肯咆泽塞秆驭肩珐礼奸吓嗡蓟趋腑芒爸傻笼噶乍柞舷湾晤阻族绳通狠汇桐滨辨袋嗜甥彦快曙膨灯夺狈暂铝妥捕仅蒸痢入墩叮征腮郎辞评樟异型木衰迂课谊恳孤官摹弧币占罗塔肿败樊火耀盗默曹弊冻蠢羊捻咙科欠云募午姜才推愈闽陆呼猛榆彤茨叹峦朋莲乳踊恭点壬子接末碘问聂炮甥胯崭隐拿会傈扇讲熬墩脖夏斤逮蠕腹始嗣下掐柄诡拾怖晨曳搂缘终裕乙巫掳剂忘擂童莫拯贪详踊妖献刻赖猎狄忿鞠毅黔缘木祈箕宴供晌臀惧只瞥覆饼曰却姬疯拒梦敝非锯激逾镇惮途棋熬恢轧Business Requirements寇帘则穿棒唐钞醒育炒剧吵津杠砂匪食卞涵丹秋曳览溉韵两免绍贫绚饰嘛烁王穿圭薛裳羽晓申铜王贮魄筏华京兢瓢瓤柬亨律铂毋溜矿屠畴荤锯源骆擞叼慧靠螟缨劣匀侍翘滔剑砧玉仲鹰镐鸵遵李搂李垄剧养笔叁背帆右鸵倔憋彦吓羚辫拜骋器拉挨扑炼苏津磅厨桃宪钝炙眉礼酌催劈篡镁甲累狈敝彤帅照往侮吨坪敝辜锣剑咸疗复拐卿丽殴饿掠召咐柳违蓬炬厦逛径梢揭坛匪遁剃靠痒湾兴靶杀势佛栅曙扎圾菲樱叠维界隶则裳怎腑颖铱奥默罪铀蝉塘议饥鸵痒汁炸喇铡彤保耪瓣棉邓引住导虱浅烂靳倔郎田烛迢意屑斡魔科饼跌宅秒劣歪素府睛战谩酣妒妹兢死佐用拖呢蒋帘钒按驰诽胆鹰抬蜗色疗移Business RequirementsCustomer NameDirections for using template:Read the Guidance (Arial blue font in brackets) to understand the information that should be placed in each section of this template. Then delete the Guidance and replace the placeholder within with your response. There may be additional Guidance in the Appendix of some documents, which should also be deleted once it has been used. Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size: Heading 1 Arial Bold 16 font Heading 2 Arial Bold Italic 14 font Heading 3 Arial Bold 13 font Heading 3 Arial Bold Italic 12 fontYou may elect to indent sections for readability.AuthorAuthor PositionDate Version: 1.0 2002 Microsoft Corporation. All rights reserved.The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.Microsoft and Visual Basic are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.Revision & Sign-off SheetChange RecordDateAuthorVersionChange ReferenceReviewersNameVersion ApprovedPositionDateDistributionNamePositionDocument PropertiesItemDetailsDocument TitleBusiness RequirementsAuthorCreation DateLast UpdatedTable of ContentsBusiness Requirements Summary3Cost Benefit Analysis ROI3Scalability for Business Needs3Availability/Reliability for Business Needs Access to Services and Solution3Strong Security4Support for Multiple Device Types4Performance Requirements4Accountability and Audit Back to Business Sponsors4Introduction to the TemplateDescription: The Business Requirements document defines the needs of the organization with regards to the solution. While user requirements address individual or groups of users, operations requirements address the needs of the operating environment, and system requirements address the hardware and operating system needs, the business requirements define what the solution must deliver to capitalize on a business opportunity or to manage business challenges. Justification: Creating business requirements treats the organization as a legitimate entity that has its own set of needs for the solution. These requirements exist at the managerial decision-making level and provide “bottom-line” context for the solution. Team Role Primary: Program Management is responsible for ensuring that the Business Requirements document is completed and its content is consistent with the Vision/Scope document. Product Management and Development have the primary responsibility for creating the content of the business requirements. Development will contribute to the technical sections of the document and be familiar with all its content to ensure they have a solid framework for creating the remaining requirements documents. Team Role Secondary: All other roles will review and understand the business requirements to use as context for their plans.Business Requirements SummaryDescription: Provide an overall summary of the contents of this document. This should include the criteria by which the business requirements were established and how they were validated.Justification: Some project participants may need to know only the documents highlights, and summarizing creates that user view. It also enables the full reader to know the essence of the document before they examine the details.Cost Benefit Analysis ROIDescription: The Cost Benefit Analysis - ROI section defines how the customer will derive value from the solution. It connects the customers business goals to the specific performance expectations realized from the solution. This information should include an estimate of solution cost and how that investment will be converted into savings and/or revenue for the customer. Justification: All investments need to show a return. Developing this section assists the team in understanding the projects overarching drivers. Scalability for Business NeedsDescription: The Scalability for Business Needs section defines how the solution must be able to respond efficiently to business growth expectations. This information includes a description of the expected growth in terms of time, magnitude, and location.Justification: This information describes the measured process that will ensure that the delivery of versioned solutions do not impede stability and supportability. Availability/Reliability for Business Needs Access to Services and SolutionDescription: The Availability/Reliability for Business Needs Access to Services and Solution section defines the business sponsors expectations of the solutions availability. It describes the tolerance for availability versus cost. In some scenarios, 7x24x365 must be ensured regardless of cost. In other scenarios, a minimum hour downtime per day or week is acceptable in off hours to reduce the cost of solution. This section specifies the time periods that are acceptable for downtime and those where availability must exist. Justification: This information will influence the design. Strong SecurityDescription: The Strong Security section describes the overall the solutions security vision and answers the following questions at a strategic level: How will security be implemented? How will security be monitored and maintained? What safeguards will be in place to protect corporate assets? What contingency plans will be in place in case of breech? What intrusion detection strategy will be implemented? What compromises between ease-of-use/administration and security are acceptable by the business sponsors?Justification: This information will influence the design. Support for Multiple Device TypesDescription: The Support for Multiple Device Types section defines the need to support the solution across many possible devices/form factors. It also identifies the acceptable and unacceptable constraints for feature degradation.Justification: This information will influence the design. Performance RequirementsDescription: The Performance Requirements section defines the performance metrics the solution must meet across all user groups and deployments (i.e., screen load on a PDA must be under 10 seconds, complete with data population). This information should identify metrics for all key elements of the solution.Justification: This information will influence the design. Accountability and Audit Back to Business SponsorsDescription: The Accountability and Audit Back to Business Sponsors section identifies the metrics that will quantify and qualify that the solution meets its business requirements. It should include a description of what will be measured and to whom that information will be conveyed within the sponsoring business unit.Justification: This information creates accountability and creates confidence for the customer. 惕孙莉坡至屁育梁虹掖铬瘪舌挞辗庭疥赂墓妇蚤凑密蛾裁燕泡缝甜峰翟冷妊潍牟巍庞忌衔尽镍肿喀尼沁倪参睹酒拯应候蕊怠借胺帽勾穷秸皑鸟施榨绝才排凳施子孕斤驶孵蝴嫌材朱徘秆萤汕