还剩40页未读，继续阅读
本资源只提供10页预览，全部文档请下载后查看！喜欢就下载吧，查找使用更方便
文本内容:
苏州工业园区SaaS管理平台项目-E-Commer__IF00Confidential\*MERGEFOR__TFunctionalSpecificationSandboxPreparedfor江苏风云网络服务有限公司Wednesday25June2008Version
1.0DraftPreparedbyTangYanjunarchitecturev-yatan@microsoft.comContributorsZhaoFeiRevisionandSignoffSheetChangeRecordDateAuthorVersionChangereferen__2008-6-24TangYanjun
1.0Initialdraftforreview/discussionReviewersNameVersionapprovedPositionDateTableofContentsTOC\o1-3\h\z\tHeading99HeadingPart91ExecutiveSum__ry
21.1DocumentPurpose
21.2DocumentScope
21.3CustomerandReaderProfiles
21.4Referen__Document
21.5Termsandabbreviations22ProjectVision/ScopeSum__ry
32.1ScopeofProject
32.2VisionStatement
32.
2.1BusinessO__ectives
32.
2.2TechnicalO__ectives33ProjectHistory44ProjectJustificationandDesignGoals
54.1BusinessRequirementsSum__ry
54.
1.1Scalability
54.2UserRequirementsSum__ry
54.
2.1UserExperien__
54.
2.2__ailability
54.
2.3Reliability
54.3SystemRequirementsSum__ry
64.
3.1SystemsandServi__sDependencies
64.
3.2Interoperability
64.
3.3Location
64.4OperationsRequirementsSum__ry
64.
4.1Installation/SetupRequirementsSum__ry
64.
4.2UninstallationRequirementsSum__ry
64.
4.3IntegrationRequirementsSum__ry
64.
4.4SupportabilitySum__ry
64.5Legaland/orRegulatoryRequirementsSum__ry65SolutionDesign
75.1Con__ptualDesignSum__ry
75.2LogicalDesignSum__ry
75.3PhysicalDesignSum__ry
75.4SecurityStrategySum__ry76PlannedFeaturesandCapabilities
86.1TotalFunctionModules
86.2沙箱管理
96.
2.1功能模块
96.
2.2用户角色
106.
2.3功能用例
106.
2.4业务场景
106.3___模板管理
186.
3.1功能模块
186.
3.2用户角色
186.
3.3功能用例
186.4测试人员模板管理
216.
4.1功能模块
216.
4.2用户角色
216.
4.3功能用例
226.5测试人员CRM测试管理
276.
5.1功能模块
276.6__人员模板管理
276.
6.1功能模块
276.
6.2用户角色
276.
6.3功能用例
276.7__人员CRM__管理
316.
7.1功能模块
316.
7.2用户角色317FeatureCutsandUnsupportedS__narios328AssumptionsandDependencies339Referen__s34Note: Alltemplatesh__ehiddentextthatguidesyouthroughcompletingthetemplate.IfyoudonotalreadyviewhiddentextyoucanclicktheShow/Hidebuttonparagraph__rkertoshowallhiddenfor__ttingelements.MS@Workalsoprovidesaseparatebuttontoviewjusthiddentext.OntheAdd-InstabclickMicrosoft@Work:ShowHideHiddenText.TemplateGuidan__Description:TheFunctionalSpecificationistherepositoryforasetofdeeptechnicaldrill-downdocumentsthatdetailseveryelementofthesolutiondeliverablesexplaininginexactandspecifictermswhattheteamisbuildinganddeploying.TheFunctionalSpecificationisthefinaltechnicaldocumentagainstwhicheverydevelopmentteammemberwillbuild.TheFunctionalSpecificationisbuiltuponthefoundationofeightseparatefoundationdocuments.You__ychoosetoprovidecustomerswithalldocumentsfourrequirementsdocumentoneUsageS__nariosdocumentthreedesigndocumentsplustheparentFunctionalSpecificationdocumentoryou__ysimplychoosetocombinetherequirementsdocumentsusages__nariosanddesigndocumentsintoasingleFunctionalSpecificationwithsub-topics.Theeightfoundationaldocumentsare:UsageS__nariosUserRequirementsBusinessRequirementsOperationsRequirementsSystemRequirementsCon__ptualDesignLogicalDesignPhysicalDesignTemplatesprovidedforallfoundationdocuments.Justification:TheFunctionalSpecificationisinessen__acontractbetweenthecustomerandtheteamdescribingfromatechnicalviewwhatthecustomerexpects.ThequalityoftheFunctionalSpecificationcompletenessandcorrectnesshasasignificantimpactonthequalityofthedevelopmentactivitiesandallfollowonphases.TeamRolePri__ry:Program__nagementisresponsibleforensuringthattheFunctionalSpecificationiscompletedbyitsesti__tedcompletiondate.Program__nagementmustalsoensurethatthedesignelementsoftheFunctionalSpecificationareconsistentwiththeVision/Scopedocumentandallrelevantplansfromthe__sterProjectPlanandOperationalPlan.Developmentwillh__ethepri__ryresponsibilityforcreatingthecontentofthedesigndocumentswithintheFunctionalSpecification.Release__nagementwillparticipatewithDevelopmentbothincontentcreationandreviewtoensureoperationaldeploymentmigrationinteroperabilityandsupportneedsareaddressedwithinthedesigns.TeamRoleSecondary:Product__nagementwillreviewandunderstandthedesigndocumentswithintheFunctionalSpecificationinordertoconveysolutiondesigntopartiesexternaltotheteamandtoensurethatproductfeaturesarerepresentedinthedesignaccordingtoinitialprojectsponsorrequirements.TestwillreviewtheFunctionalSpecificationtoensuretestplansareinpla__tovalidatethedesigns.UserExperien__mustreviewthedesigndocumentstoensureuserrequirementsaremet.1ExecutiveSum__ry
1.1DocumentPurpose本文档的目的是从技术的角度清晰的刻画Sandbox子系统的需求和特性，包括功能性的和非功能性的本文档是__客户和项目团队的桥梁，将清晰地刻画出客户的期望，对项目的__活动的质量起着决定性的作用
1.2DocumentScope文档将包含VersionScope所包含的全部范围，包括项目目标、范围和需求概要描述本文档不包含系统实施方案的具体描述
1.3CustomerandReaderProfiles本说明书的预期读者为项目风险承担人、最终用户、项目管理人员、业务或需求分析人员、测试人员、用户文档编写者
1.4Referen__DocumentVisionScopeSandbx.doc系统界面原型
1.5TermsandabbreviationsSaaS管理平台SaaS__nagementPlatform，__P基于SaaS模式的软件的管理平台EC注册在SaaS平台上能使用Saas平台功能的中小企业客户，最终CRMtemplate的__者和使用者OP SaaS管理平台的运营商，Sandbox的管理者和template的管理者及template的测试者ISV__软件提供商，template的创建者SandBox沙箱，隔离于真实环境的一种生产环境UsethissectiontoprovideastrategicstatementofthecontentsoftheFunctionalSpecification.Thissectionshouldidentifywhichfoundationaldocumentsrequirementsusages__nariosanddesignscomprisetheFunctionalSpecificationandprovideabriefstatementaboutthecontentofeach.Justification:Thisinfor__tionprovidesthereaderaguidelineofthestructureofthisdocumentandthestrategiccontextforreadingitsdetail.2ProjectVision/ScopeSum__ry
2.1ScopeofProject作为苏州工业园区的基础性平台，Saas将成为中小企业信息化综合应用与服务平台作为Saas的战略组成部分，Sandbox系统将起到为加入Saas平台的中小企业提高中小企业更廉价的使用功能强劲的CRM，为中小企业拓宽发展空间，降低企业的生产成本，改变中小企业的营销方式，改变中小企业的生产方式的重要作用隶属于Saas平台的Sandbox系统将借着SaaS平台扩大影响力的契机提高CRM的影响力反过来，Sandbox系统的成功，带动着Saas平台的发展
2.2VisionStatement建成为EC服务的Sandbox管理平台，实现CRMtemplate的产供销的_____
2.
2.1BusinessO__ectivesO__ectiveRationalCategory__nagementDevSandbox__nagementTestingSandbox__nagementDevUser__nagementDevSandbox__nagementTestingUser__nagementTestingSandbox__nagementTemplate__nagementTemplateTestingTemplateImportTemplateExport
2.
2.2TechnicalO__ectivesO__ectiveRationalExtendableSecurelyMultiRoleMultiUserCapabilityPerfor__n__strong更多信息，请参见VisionScopeSandbox.docProvideanoverviewoftheproject’svisionandscope.Thisshouldincludeasum__ryofthebusinessopportunitysolutioncon__ptandscopesectionsoftheVision/Scopedocument.Justification:Thisinfor__tionprovidesessentialcontextforthereader.Thevision/scopeinfor__tionisthestrategicstatementofthesolutionwhichmustbeunderstoodbeforethereaderapproachestheFunctionalSpecificationdetails.Byincludingthisinfor__tionbothinternalandexternalprojectmembersshareacommonunderstandingoftheprojectthussettingacommonsetofexpectations.3ProjectHistoryUsethissectiontodescribetheimportanteventsanddecisionsthath__ebeen__detodatetodelivertheprojecttothispoint.Thishistory__ybeassociatedwiththepro__ssofunderstandingthecustomer’scircumstan__sandbusinessneedsoranypriorattemptsatdeliveringasimilarsolution.Ifthisisthefirstimplementationthissection__ybeomitted.Justification:Allteammembersinternalandexternalshouldsharethesameunderstandingoftheprojectandthishistoricalinfor__tionensuresthatthiscanoccur.Providingthisinfor__tionwillcloseanygapsordiscrepanciesintheteams’historicalknowledgebase.Pleaserefer苏州工业园区SaaS管理平台_工作说明SOW.docformoredetail4ProjectJustificationandDesignGoalsUsethissectiontosum__rizetherequirementsdocumentsbystatingtheircontentsintermsofbusinessuserandtechnicalneeds.Theseneedsjustifytheproject.Thissectionshouldalsoconvertthoseneedsintoastatementofthesolutiondesigngoalsthatguidedthedevelopmentofthedesigndocuments.Justification:Thisinfor__tionprovidesanunderstandingoftherequirements____ysisthatwascompletedandfurtherclarificationofprojectgoalsinadditiontothosealreadysum__rizedintheVision/Scopesectionabove.
4.1BusinessRequirementsSum__ryProvideasum__ryofthecontentsoftheBusinessRequirementsdocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsoftherequirementsdocumentCostBenefit____ysisScalabilityandsoon.Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsofthebusinessrequirementsifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoonelarge__ntraldocument.WeneedaMicrosoftDynamicsCRMSandbox__nagementSystem.ByusingthissystemtheDevelopercancreateMicrosoftDynamicsCRMtemplateandextendMicrosoftDynamicsCRMmoreeasilyandquicklyandmeanwhiledon’tcarehowtointegrateitwithSAASPlatform.ThisMISSystemalsosupporttheadministratorto__nageDevelopmentSandboxandTestingSandboxto__nagetheCRMtemplatelifecycleandsupporttemplatepublishedasaproduct.TheCRMsandboxprovidesaseparatedCRMapplicationdevelopmentplatformthatisolatesvariousCRMISVandwithintegratedtestingenviro__entsandboxtesterverifiesISV’sCRMappunderaunifiedsystem.AsasubprojectofSaaS__nagementplatformSandboxMIS__nagesSandbox/TestingenvISVuseraswellassandboxrelatedresour__s.SandboxadministratorcreatessandboxforISVandpublishestestedsolutionto__rketpla__Sandboxsystemalsoimplementsseriesofexternalpro__sstosupportaintact__Ppro__ss.Aproducton-shelfpro__sspublishesCRMapplicationfromSandboxto__rketpla__anditcoordinatewith“chargingpolicy”and“Productdefinitionpro__ss”to__kea“product”orderablein__P__rketpla__.SandboxsystemispartiallybasedonMicrosoftDynamicsCRM
4.0withalterationofdefaultdeploymentISVandtestercouldexports/importsCRMAppwithoutusingother3dr_____toolsoutsideSandbox.
4.
1.1ScalabilitySandboxMISSystemanticipatesan__erageloadof10developerand500concurrentusersafterthesystemisfullyoperationalandexpectsthattogrowby5per__nteachyearforthenextfiveyears.
4.2UserRequirementsSum__ryProvideasum__ryofthecontentsoftheUserRequirementsdocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsoftherequirementsdocumentUserExperien__ReliabilityAc__ssibilityandsoon.Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsoftheuserrequirementsifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoonelarge__ntraldocument.
4.
2.1UserExperien__DevandTestingSandboxquickly__nage，Aneasywayto__nagetemplate，CreateMicrosoftDynamicsCRMtemplate，pleasereferSandbox的UIprototype
4.
2.2__ailabilityBecausetheWebsiteisac__ssedbycustomersacrosstheworlditneedstobe__ailable24hoursaday7daysaweek.
4.
2.3ReliabilityBecauseoftheneedfor24*7__ailabilityauto__ticfailoverwillberequired.Inadditionexistingdisasterrecoveryandbackupplansandpro__duresmustberevisedtoincorporatetheSandboxMsanagementApplication.
4.3SystemRequirementsSum__ryProvideasum__ryofthecontentsoftheSystemRequirementsdocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsoftherequirementsdocumentSystemsandServi__sDependenciesInteroperabilityandsoon.Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsofthesystemrequirementsifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoonelarge__ntraldocument.
4.
3.1SystemsandServi__sDependencies__PPlatformHostingMicrosoftCRMADServi__
4.
3.2InteroperabilityIntegratedSAASPlatformSingleSignOnCRMTemplatepublishandProductreleasetoSAASSolutionSuper__rket
4.
3.3LocationTheWebSiteEnhan__mentapplicationwillbeusedbycustomersusingarangeofbrowserclientsinavarietyoflocationsaroundtheworld
4.4OperationsRequirementsSum__ryProvideasum__ryofthecontentsoftheOperationsRequirementsdocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsoftherequirementsdocumentSecurity__nageabilitySupportabilityetc..Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsoftheoperationsrequirementsifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoonelarge__ntraldocument.
4.
4.1Installation/SetupRequirementsSum__ryUsethissectiontosum__rizetheenviro__entalrequirementsforsolutioninstallation.Thisinfor__tion__ybederivedfromtheDeploymentPlan’sinstallationsections.ThePhysicalDesigndocumentcontainsthedetailonhowtheserequirementswillbesatisfied.NeedIIS.netframeworkSQLServer2005HostingCRMSaaSPlatform.PleaserefertoSaaSDeployDocument.docformoredetail.Setupandinstallationmustnotinterrupttheuser’sdailytasksandworkflow.
4.
4.2UninstallationRequirementsSum__ryUsethissectiontodescribehowthesolutionisremovedfromitsenviro__ent.Thisshouldincludeadefinitionofwhatmustbeconsideredpriortoremovingthesolutionandwhatmustbeconsideredinabackup/restorecapacitypriortoun-installingtoensuresaferecovery/rebuildatalatertime.
4.
4.3IntegrationRequirementsSum__ryUsethissectiontosum__rizeintegrationandinteroperabilityrequirementsandtheprojectgoalsrelatedtotheserequirements.TheMigrationPlan__ybereferen__dorsum__rizedhereasitcontainsintegrationandinteroperabilityspecifications.ThePhysicalDesigndocumentcontainsthedetailonhowintegrationwillbedelivered.Pleasereferto
4.
3.2InteroperabilityPleaserefertoVersionScopeSandbox.docformoredetail
4.
4.4SupportabilitySum__ryUsethissectiontosum__rizethesupportabilityrequirementsandtheprojectgoalsrelatedtotheserequirements.TheOperationsPlanandSupportPlan__ybereferen__dorsum__rizedhereastheycontainsupportabilityspecifications.ThePhysicalDesigndocumentcontainsthedetailonhowsupportabilitywillbedelivered.PleaserefertoVersionScopeSandbox.docformoredetail
4.5Legaland/orRegulatoryRequirementsSum__ryUsethissectiontosum__rizeanylegaland/orregulatoryrequirementstowhichtheprojectmustadhere.Legalrequirements__ycomefromthecustomer’scorporatepoliciesorfromregulatoryagenciesgoverningthecustomer’sindustry.FollowtheMicrosoftDynamicsCRMpoli__.Followthe__PDevelopmentGuid.5SolutionDesignUsethissectiontoidentifythedesigndocumentsthath__ebeendevelopedandsum__rizestheoverallsolutiondesigninasuccinctstatement.Alsodefinewhyeachofthesedesigndocumentsisne__ssaryfortheproject.Justification:Thisinfor__tionprovidesthereaderwithstrategiccontextforthefollowonreading.Itexplainsthedifferen__sbetweenthedesigndocumentsandexplainshoweachprovidesauniquepictureofthesolution.
5.1Con__ptualDesignSum__ryProvideasum__ryofthecontentsoftheCon__ptualDesigndocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsofthedocumentSolutionOverviewSolutionArchitectureandsoon.Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsofthedesigndocumentifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoonelarge__ntraldocument.概念设计针对系统的背景和目标，设计详细的用户和系统交互场景针对SandboxMIS的概念设计请参见本文档的第六部分系统规划特征
5.2LogicalDesignSum__ryProvideasum__ryofthecontentsoftheLogicalDesigndocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsofthedocumentUsersO__ectsAttributesandsoon.Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsofthedesigndocumentifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoalarge__ntraldocument.逻辑设计将针对每个场景详细描述系统各个分层架构的传递和对象之间的交互系统顺序图和通信图，类库的设计将是这个设计的主要产物详细信息请参见SandboxLogicalDesign.doc
5.3PhysicalDesignSum__ryProvideasum__ryofthecontentsofthePhysicalDesigndocument.ThisshouldincludeasuccinctstatementofthecontentsofeachofthekeysectionsofthedocumentApplicationInfrastructureandsoon.Forsomeprojectsit__ybeappropriatetoincludetheentirecontentsofthedesigndocumentifachoi__hasbeen__detoconsolidatealltechnicaldocumentationintoonelarge__ntraldocument.物理设计文档__系统的结构和宏观架构分层模式和系统结构将是这个设计的主要产物详细信息请参见SandboxPhysicalDesign.doc
5.4SecurityStrategySum__ryUsethissectiontodescribethesolutionsecuritystrategythatwillinfluen__thedesign.Thefollowingquestionswillassistindevelopingthisstrategy:Whataretheprincipalo__ectivestoprovidingasecureenviro__entWhatcompromisesinsecurityarene__ssaryforuserconvenien__usabilityandperfor__n__WhatspecificsecuritytoolsandtechnologieswillbeimplementedwithinthesolutionThePhysicalDesigndocumentcontainsthespecificsecuritydetailsinaper-feature/per-componentfor__t.Thisstrategysectionshouldbeabriefsynopsisofauniformsecuritystrategyalongwithreferen__stotheSecurityPlan.Sandbox的安全策略关键是要保证商务活动过程中系统的安全性在用户登陆的时候采用SSL加密系统输入的客户端和服务器段检查显得必要，SQL语句注入检查对于电子商务的安全性是必须的系统设立健全的认证和授权机制针对每个页面都需要做身份验证，防止用户的URL攻击统一出错页面，防止系统的任何技术信息和技术细节外漏建议用户采用__度的__策略内网__和外网__分开部署其他系统级的安全策略，这种安全策略应包括规定的网络访问、服务访问、本地和远地的用户认证、拨入和拨出、磁盘和数据加密、病毒防护措施，以及管理制度等6PlannedFeaturesandCapabilitiesUsethissectiontoidentifyunambiguouslywhichfeaturesareinscopeforthisreleaseofthesolution.Eachfeatureorcapabilityshouldbedescribedinsufficientdetailthatallrolescanworkoutwhattheywillneedtocreate/testforthesolutiontoworkasdesigned.Justification:ThisistheheartoftheFunctionalSpecificationandprovidesthetoolthattheprojectteamwillusetocontrolchangestoscopeastheprojectprogresses..Itwillclarifythecurrentprojectemphasisanddeliverablesandpreventpossiblemisunderstandingorconfusion.
6.1TotalFunctionModules系统划分为沙箱管理，___模板管理，测试人员模板管理，测试人员CRM测试，__人员模板管理，__人员CRM__系统的用例图如下SBAdminSBTesterISVDevManagetemplates****ManagecategoryinlistISVpublishtemplatesandPendingfortestextendsProductMgrSearchcategoryAddcategoryDelcategoryModfiycategoryViewcategoryinlistextendsextendsextendsViewcategorydetailsusesusesusesManageISVownedtemplatelistViewtemplatedetailsDeletetemplateExporttemplatetoSBextendsextendsModifytemplateinfoextendsusesSearchtempateusestestassignedtemplatesfromlistusesPublishtestedtemplateextendsModfiyISVtemplatestestingstatusextendsusesViewtestedtemplatesusesextendsAssignacategorytoatemplateextendsusesPublishISVstemplatestoMPextends系统顺序图如下AdminObject1SandBoxMISDeveloperObject3TesterObject4ManagerSandboxAPreparedSanboxAssignedSanboxAssignResultCreateTemplateBySandboxExportTemplateCRMTemplateImportTemplateEditTemplateInSandboxExportTemplateAgainCRMTemplateSubmitTemplateAssigneTemplateTestorAssignResultImportTemplateToTestingEnvTestTemplateLogTemplateTesingResultLogResultMessagePublishTemplateAsaProductProductHasReleased
6.2沙箱管理
6.
2.1功能模块此模块包含如下功能新增沙箱、编辑沙箱、删除沙箱，分配沙箱到ISVDev或Tester以及收回沙箱在页面设计上，可以采用向导式设计将这些功能模块有机的结合在一起
6.
2.2用户角色此模块涉及的系统用户角色包括企业用户___
6.
2.3功能用例企业管理员新增沙箱编辑沙箱删除沙箱分配沙箱收回沙箱usesusesusesusesusesFigure1沙箱管理用例在页面设计上，可以体现几个用例的关联性但逻辑上，用例并不做任何关联，任何时候都可以让用户运行其中任何一个用例
6.
2.4业务场景
6.
2.
4.1新增沙箱场景名称新增沙箱场景用户企业用户___主场景情景描述用户__左边菜单栏的“沙箱管理”菜单；系统在右边主题框架里显示沙箱管理页面包括沙箱列表和功能按钮；用户单击其中的“新增”按钮；系统弹出新增沙箱的页面；用户填写沙箱的详细信息，完成后__“保存”按钮；系统提示保存成功并关闭弹出窗口；子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息沙箱管理页面显示查询、新增、编辑、删除、分配沙箱、收回沙箱、分页按钮和沙箱列表；新增沙箱页面显示保存、返回按钮输入信息查询条件、沙箱属___输出信息沙箱列表保存成功或者保存失败信息业务规则无参考界面备注
6.
2.
4.2编辑沙箱场景名称编辑沙箱场景用户企业用户___主场景情景描述用户__“编辑”按钮系统弹出编辑沙箱页面；用户修改沙箱的详细信息，完成后__“保存”按钮；系统提示保存成功并关闭页面；子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息沙箱管理页面显示新增、编辑、删除、分配沙箱、收回沙箱、分页按钮和沙箱列表编辑页面显示保存和返回按钮输入信息沙箱的详细信息输出信息保存成功或者失败信息业务规则无参考界面备注
6.
2.
4.3删除沙箱场景名称删除沙箱场景用户企业用户___主场景情景描述用户__沙箱管理页面上的“删除”按钮系统提示删除成功并刷新沙箱列表子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息（页面不可编辑，保留的目的为了__P的EC管理）沙箱管理页面显示新增、编辑、删除、分配沙箱、收回沙箱、分页按钮和沙箱列表输入信息（页面不可编辑，保留的目的为了__P的EC管理）无输出信息删除成功或者失败信息业务规则无参考界面备注
6.
2.
4.4分配沙箱场景名称分配沙箱场景用户企业用户___主场景情景描述用户__沙箱管理页面的“分配沙箱”按钮；系统弹出ISV列表页面；用户选择一个ISV，__右上方的“下一步”按钮；系统显示该ISV的所有帐户；用户选择一个帐户，__“完成”按钮；系统提示操作成功；若用户在5__“上一步”按钮，系统转到3子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息沙箱管理页面显示新增、编辑、删除、分配沙箱、收回沙箱、分页按钮和沙箱列表；分配沙箱页面显示上一步、下一步、完成、查询按钮和ISV以及其帐号的列表输入信息无输出信息成功或者失败信息业务规则无参考界面备注
6.
2.
4.5收回沙箱场景名称收回沙箱场景用户企业用户___主场景情景描述用户__沙箱管理页面的“收回沙箱”按钮；系统提示操作成功子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息沙箱管理页面显示新增、编辑、删除、分配沙箱、收回沙箱、分页按钮和沙箱列表输入信息无输出信息操作成功或者失败信息业务规则无参考界面备注
6.3___模板管理
6.
3.1功能模块此模块包含如下功能派遣测试和发布
6.
3.2用户角色此模块涉及的系统用户角色包括企业用户___
6.
3.3功能用例顶层包::企业管理员派遣测试发布usesusesFigure2___模板管理用例在逻辑上应该将增删改都可以归为一个用例，这里将用例细分，是为了说明方便场景诉述中突出不同的重点
6.
3.
3.1派遣测试场景名称派遣测试场景用户企业用户___主场景情景描述用户__左边菜单中的“模板管理”菜单；系统在右边主框架显示模板管理页面，页面上显示模板的列表；用户选择一个模板，__“派遣测试”按钮；系统弹出模板派遣测试页面，页面上显示Tester列表；用户选择一个Tester，__“保存”按钮；系统提示操作成功子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息模板管理页面显示派遣测试、发布、查询、分页按钮和模板列表；派遣测试页面显示保存、返回、查询、分页按钮和Tester列表输入信息查询模板或Tester的条件输出信息成功或者失败信息业务规则无参考界面备注
6.
3.
3.2发布场景名称发布场景用户企业用户___主场景情景描述子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息输入信息输出信息成功或者失败信息业务规则参考界面备注
6.4测试人员模板管理
6.
4.1功能模块此模块包含如下功能模板导入沙箱，导出沙箱、模板测试结果记录
6.
4.2用户角色此模块涉及的系统用户角色包括测试人员
6.
4.3功能用例测试人员导入沙箱uses测试结果uses导出沙箱usesFigure3测试人员模板管理
6.
4.
3.1导入沙箱测试人员将某个模板导入指定沙箱场景名称导入沙箱场景用户测试人员主场景情景描述用户__左边菜单栏SandBox测试的“模板管理”菜单；系统在右边主框架显示模板管理页面；用户__“导入”按钮；系统弹出模板导入页面，页面上显示该测试人员的所有沙箱列表；用户选择一个沙箱，__“保存”按钮；系统提示保存成功子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息模板管理页面显示查询、导入、导出、测试结果、分页按钮和模板列表；模板导入页面显示查询、保存、返回、分页按钮和沙箱列表输入信息查询条件输出信息成功或者失败信息业务规则无参考界面备注
6.
4.
3.2导出沙箱测试人员将模板从沙箱中导出场景名称测试结果场景用户测试人员主场景情景描述用户__模板管理页面的“导出”按钮；系统提示导出成功子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息模板管理页面显示查询、导入、导出、测试结果、分页按钮和模板列表；输入信息无输出信息成功或者失败信息业务规则无参考界面备注
6.
4.
3.3测试结果测试人员填写测试后的结果和反馈场景名称测试结果场景用户测试人员主场景情景描述用户__模板管理页面的“测试结果”按钮；系统弹出测试结果记录的页面；用户填写测试的结果和反馈信息，__保存按钮；系统提示保存成功子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息模板管理页面显示查询、导入、导出、测试结果、分页按钮和模板列表；日志页面显示保存、返回按钮和日志信息的输入框输入信息测试结果的详细信息输出信息成功或者失败信息业务规则无参考界面备注
6.5测试人员CRM测试管理
6.
5.1功能模块此模块包含如下功能测试人员CRM测试管理
6.
5.2用户角色此模块涉及的系统用户角色包括Sandbox的测试人员
6.
5.3功能用例场景名称测试人员CRM测试管理场景用户Sandbox的测试人员主场景情景描述测试人员__登录CRM链接；系统显示该测试人员所有的沙箱；测试人员选择一个沙箱登陆，系统单点登录到沙箱中测试人员开始测试子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息测试人员所有的沙箱；输入信息无输出信息成功或者失败信息业务规则无参考界面备注
6.6__人员模板管理
6.
6.1功能模块此模块包含如下功能模板导入、模板导出、编辑模板、删除模板、发布模板等待测试
6.
6.2用户角色此模块涉及的系统用户角色包括ISV__人员
6.
6.3功能用例#0;Tester:UserImportTemplateManageISVTemplateextendsExportTemplateusesEditTemplateextendsextendsDeleteTemplateextendsSubmitTemplateextendsFigure4ISV模板管理在页面设计上，可以体现几个用例的关联性但逻辑上，用例并不做任何关联，任何时候都可以让用户运行其中任何一个用例
6.
6.
3.1ISV模板管理场景名称ISV模板管理场景用户ISV__人员主场景情景描述用户可以“导入”模板
1.1用户查询并选择模板，__“导入”按钮；
1.2系统提示“导入”操作结果用户可以“编辑”模板；
2.1用户查询并选择选择模板，__“编辑”按钮；
2.2系统弹出模板编辑页面
2.3用户修改模板的详细信息，完成后__“保存”按钮；用户可以__“删除”按钮；
3.1用户查询并选择选择模板，__“删除”按钮；
3.2系统提示用户确认是否删除
3.2a用户选择“是”，系统删除用户选择的模板，并提示操作结果
3.2b用户选择“否”，系统不做任何操作用户可以“导出”模板；
4.1用户查询并选择选择模板，__“导出”按钮；
4.2系统弹出模板导出页面
4.3用户修改导出模板的详细信息，完成后__“保存”按钮；用户可以“提交”模板；
5.1用户查询并选择选择模板，__“提交”按钮；
5.2系统弹出模板提交编辑页面
5.3用户修改提交模板的详细信息，完成后__“保存”按钮；子场景描述异常描述出现任何异常，转到统一出错页面页面元素模板管理页面显示查询、导入、导出、提交、编辑、删除、分页按钮和模板列表；“模板提交”和“模板编辑”“模板导出”页面显示保存、返回按钮输入信息查询条件、模板属___输出信息模板列表保存成功或者保存失败信息模板管理页面显示查询、导入、导出、提交、编辑、删除、分页按钮和模板列表；“模板提交”和“模板编辑”“模板导出”页面显示保存、返回按钮输入信息查询条件、模板属___参考界面备注
6.7__人员CRM__管理
6.
7.1功能模块ISV用户通过成功登录CRM系统后，可以进行CRM的__管理
6.
7.2用户角色此模块涉及的系统用户角色包括ISV__人员
6.
7.3功能模块此模块包含如下功能__人员CRM登陆
6.
7.4用户角色此模块涉及的系统用户角色包括Sandbox的__人员
6.
7.5功能用例场景名称__人员CRM登陆场景用户Sandbox的__人员主场景情景描述__人员__登录CRM链接；系统单点登录到沙箱中__人员开始进入__子场景描述无异常描述出现任何异常，转到统一出错页面页面元素显示信息无输入信息无输出信息无业务规则无参考界面无备注7FeatureCutsandUnsupportedS__nariosUsethissectiontoidentifyanyfeaturesthath__ebeenspecificallyexcludedfromthisreleaseofthesolution..Thisshouldalsoidentifyanyrequirementbusinessusersystemoperationalusages__nariothatcannotbemetandanexplanationofwhyitcannotbemet.Thissection__yalsoidentifyfuturesolutionreleasesthatwillsatisfytheserequirements.Justification:Justasitisimportanttoprovidedetaileddescriptionsofwhattheprojectwilldeliveritisequallyimportanttodescribefeaturesands__nariosthatarebeingomittedfromthesolutionscope.Thiswillfurtherclarifythecurrentprojectemphasisanddeliverablesandpreventpossiblemisunderstandingorconfusion.Nofeaturecut.8AssumptionsandDependenciesUsethissectiontolistanddefinetheproject-orientedassumptionsanddependenciesasopposedtofeaturedependenciesorenviro__entaldependenciesthath__ebeenidentifiedthroughthepro__ssofdevelopingtheFunctionalSpecification.Anexampleofadependencyisthis:adelivery__yrequireadvan__dskillsinvariousproducttechnologiesorbusinesspro__sses.Listassumptionsanddependenciesseparately.Justification:Assumptionsshouldbeidentifiedwhereactualdatadoesnotexistandwillidentifytheactionsrequiredtoverifythoseassumptions.Dependencieswillidentifyanyactionsthatmustbetakentoensurethosedependenciesareincorporatedintotheprojectplans.9Referen__sUsethissectiontoidentifyanyinternalorexternalresour__sthatwouldprovidesupplementaryinfor__tiontotheFunctionalSpecification.VisionScopeSandbox.doc系统界面原型Saas平台FunctionalSpecification.doc苏州工业园区SaaS管理平台_工作说明SOW.docTheinfor__tioncontainedinthisdocumentrepresentsthecurrentviewofMicrosoftCorporationontheissuesdiscussedasofthedateofpublication.BecauseMicrosoftmustrespondtochanging__rketconditionsitshouldnotbeinterpretedtobeacommitmentonthepartofMicrosoftandMicrosoftcannotguaranteetheaccuracyofanyinfor__tionpresentedafterthedateofpublication.MICROSOFT__KESNOWARRANTIESEXPRESSIMPLIEDORSTATUTORYASTOTHEINFOR__TIONINTHISDOCUMENT.Complyingwithallapplicablecopyrightlawsistheresponsibilityoftheuser.Withoutlimitingtherightsundercopyrightnopartofthisdocument__ybereprodu__dstoredinorintrodu__dintoaretrievalsystemortran__ittedinanyformorbyanymeanselectronicmechanicalphotocopyingrecordingorotherwiseorforanypurposewithouttheexpresswrittenpermissionofMicrosoftCorporation.Microsoft__yh__epatentspatentapplicationstrade__rkscopyrightsorotherin____ectualpropertyrightscoveringsu__ect__tterinthisdocument.Ex__ptasexpresslyprovidedinanywrittenli__nseagreementfromMicrosoftthefurnishingofthisdocumentdoesnotgiveyouanyli__nsetothesepatentstrade__rkscopyrightsorotherin____ectualproperty.Thedescriptionsofothercompanies’productsinthisdocumentifanyareprovidedonlyasaconvenien__toyou.Anysuchreferen__sshouldnotbeconsideredanendorsementorsupportbyMicrosoft.Microsoftcannotguaranteetheiraccuracyandtheproducts__ychangeovertime.Alsothedescriptionsareintendedasbriefhighlightstoaidunderstandingratherthanasthoroughcoverage.Forauthoritativedescriptionsoftheseproductspleaseconsulttheirrespective__nufacturers.©2007MicrosoftCorporation.Allrightsreserved.MicrosoftandWindowsareeitherregisteredtrade__rksofMicrosoftCorporationintheUnitedStatesand/orothercountries.Thenamesofactualcompaniesandproductsmentionedherein__ybethetrade__rksoftheirrespectiveowners.PageiiFunctionalSpecificationDocumentSu__ectVersion.1DraftPreparedbyTangYanjunDocument27lastmodifiedon25Jun.08Rev1。
个人认证
优秀文档
获得点赞 0
