Vision Scope.docx

Vision Scope.docx

《Vision Scope.docx》由会员分享，可在线阅读，更多相关《Vision Scope.docx（8页珍藏版）》请在冰豆网上搜索。

VisionScope

<>

Vision/Scope

CustomerName

Directionsforusingtemplate:

ReadtheGuidance（Arialbluefontinbrackets）tounderstandtheinformationthatshouldbeplacedineachsectionofthistemplate.ThendeletetheGuidanceandreplacetheplaceholderwithin<>withyourresponse.TheremaybeadditionalGuidanceintheAppendixofsomedocuments,whichshouldalsobedeletedonceithasbeenused.

Sometemplateshavefourlevelsofheadings.Theyarenotindented,butcanbedifferentiatedbyfonttypeandsize:

∙Heading1–ArialBold16font

∙Heading2–ArialBoldItalic14font

∙Heading3–ArialBold13font

∙Heading3–ArialBoldItalic12font

Youmayelecttoindentsectionsforreadability.

Author

AuthorPosition

Date

Version:

1.0

Ó2002MicrosoftCorporation.Allrightsreserved.

TheinformationcontainedinthisdocumentrepresentsthecurrentviewofMicrosoftCorporationontheissuesdiscussedasofthedateofpublication.BecauseMicrosoftmustrespondtochangingmarketconditions,itshouldnotbeinterpretedtobeacommitmentonthepartofMicrosoft,andMicrosoftcannotguaranteetheaccuracyofanyinformationpresentedafterthedateofpublication.

Thisdocumentisforinformationalpurposesonly.MICROSOFTMAKESNOWARRANTIES,EXPRESSORIMPLIED,INTHISDOCUMENT.

MicrosoftandVisualBasicareeitherregisteredtrademarksortrademarksofMicrosoftintheUnitedStatesand/orothercountries.

Revision&Sign-offSheet

ChangeRecord

Date

Author

Version

ChangeReference

Reviewers

Name

VersionApproved

Position

Date

Distribution

Name

Position

DocumentProperties

Item

Details

DocumentTitle

Vision/Scope

Author

CreationDate

LastUpdated

TableofContents

[IntroductiontotheTemplate

Description:

TheVision/Scopedocumentrepresentstheideasanddecisionsdevelopedduringtheenvisioningphase.Thegoalofthephase,representedbythecontentofthedocumentation,istoachieveteamandcustomeragreementonthedesiredsolutionandoverallprojectdirection.

TheVision/Scopedocumentisorganizedintofourmainsections:

∙BusinessOpportunity:

adescriptionofthecustomer’ssituationandneeds

∙SolutionsConcept:

theapproachtheprojectteamwilltaketomeetthecustomer’sneeds

∙Scope:

theboundaryofthesolutiondefinedthoughtherangeoffeaturesandfunctions,whatisoutofscope,areleasestrategy,andthecriteriabywhichthesolutionwillbeacceptedbyusersandoperations

∙SolutionDesignStrategies:

thearchitecturalandtechnicaldesignsusedtocreatethecustomer’ssolution

Justification:

Vision/Scopedocumentationisusuallywrittenatthestrategiclevelofdetailandisusedduringtheplanningphaseasthecontextfordevelopingmoredetailedtechnicalspecificationsandprojectmanagementplans.Itprovidescleardirectionfortheprojectteam;outlinesexplicit,up-frontdiscussionofprojectgoals,priorities,andconstraints;andsetscustomerexpectations.

TeamRolePrimary:

ProductManagementisthekeydriveroftheenvisioningphaseandresponsibleforfacilitatingtheteamtotheVision/Scopeapprovedmilestone.ProductManagementdefinesthecustomerneedsandbusinessopportunityorproblemaddressedbythesolution.

TeamRoleSecondary:

ProgramManagementisresponsibleforarticulatingtheSolutionConcept,Goals,Objectives,Assumptions,Constraints,Scope,andSolutionDesignStrategiessectionsofthisdocument.}]

BusinessOpportunity

[Description:

TheBusinessOpportunitysectioncontainsthestatementofthecustomer’ssituation.Itisexpressedinbusinesslanguage,nottechnicalterms.ThissectionshoulddemonstrateMicrosoft’sunderstandingofthecustomer’scurrentenvironmentanditsdesiredfuturestate.Thisinformationistheoverallcontextfortheproject.]

OpportunityStatement

[Description:

TheOpportunityStatementsectiondescribesthecustomer’scurrentsituationthatcreatestheneedfortheproject.Itmaycontainastatementofthecustomer’sopportunityandtheimpactofcapitalizingonthatopportunity（productinnovation,revenueenhancement,costavoidance,operationalstreamlining,leveragingknowledge）.Itmaycontainastatementofthecustomer’sproblemandtheimpactofsolvingtheproblem（revenueprotection,costreduction,regulatorycompliance,alignmentofstrategyandtechnology）.Itshouldincludeastatementthatconnectsthecustomer’sopportunity/problemtotherelevantbusinessstrategyanddrivers.TheOpportunityStatementiswrittenconciselyusingabusinessexecutive’svoice.

Justification:

TheOpportunityStatementdemonstratesthatMicrosoftunderstandsthecustomer’ssituationfromthebusinesspointofviewandprovidestheprojectteamandotherreaderswiththestrategiccontextfortheremainingsections.]

<>

VisionStatement

[Description:

TheVisionStatementsectionclearlyandconciselydescribesthefuturedesiredstateofthecustomer’senvironmentoncetheprojectiscomplete.Thiscanbearestatementoftheopportunity;however,itiswrittenasifthefuturestatehasalreadybeenachieved.Thisstatementprovidesacontextfordecision-making.Itshouldbemotivationaltotheprojectteamandthecustomer.

Justification:

AsharedVisionStatementamongallteammembershelpsensurethatthesolutionmeetstheintendedgoals.Asolidvisionbuildstrustandcohesionamongteammembers,clarifiesperspective,improvesfocus,andfacilitatesdecision-making.]

<>

BenefitsAnalysis

[Description:

TheBenefitsAnalysissectiondescribeshowthecustomerwillderivevaluefromtheproposedsolution.Itconnectsthebusinessgoalsandobjectivestothespecificperformanceexpectationsrealizedfromtheproject.Theseperformanceexpectationsshouldbeexpressednumerically.Thissectioncouldbepresentedusingthefollowingsubsections:

∙BusinessGoalsandObjectives

∙BusinessMetrics

∙BusinessAssumptionsandConstraints

∙BenefitsStatement

Justification:

BenefitsAnalysisdemonstratesthatMicrosoftsufficientlyunderstandsthecustomer’ssituation.Italsodefinesthecustomer’sbusinessneeds,whichmayprovidevitalinformationformakingsolution/technologyrecommendations.]

<>

SolutionsConcept

[Description:

ASolutionsConceptprovidesageneraldescriptionofthetechnicalapproachtheprojectteamwilltaketomeetthecustomer’sneeds.Thisincludesanunderstandingoftheusersandtheirneeds,thesolution’sfeaturesandfunctions,acceptancecriteria,andthearchitecturalandtechnicaldesignapproaches.

Justification:

TheSolutionConceptprovidesteamswithlimitedbutsufficientdetailtoprovethesolutiontobecompleteandcorrect;toperformseveraltypesofanalysesincludingfeasibilitystudies,riskanalysis,usabilitystudies,andperformanceanalysis;andtocommunicatetheproposedsolutiontothecustomerandotherkeystakeholders.]

Goals,Objectives,Assumptions,andConstraints

[Description:

TheGoals,Objectives,Assumptions,andConstraintssectioncontainsthefollowingcomponentsthatdefinetheproduct’sparameters:

∙Goals（theproduct’sfinalpurposeoraim）

∙Objectives（thegoalsbrokenintomeasurablecomponents）

∙Assumptions（factorsconsideredtrue,real,orcertainthatareawaitingvalidation）

∙Constraints（anonfunctionalrequirementthatwilllimittheproduct）.

ThesolutionGoalsandObjectivesareinitiallyderivedfromthebusinessandtechnicalgoalsandobjectivesthataredevelopedduringtheopportunityphaseandconfirmedduringtheenvisioningphase.

AssumptionsandConstraintsmaybederivedfromtheproduct’sfunctionality,aswellasresearchregardingthecustomer’senvironment.

Justification:

TheGoalsandObjectivesarticulateboththecustomer’sandteam’sexpectationsofthesolutionandcanbeconvertedintoperformancemeasurements.Assumptionsattempttocreateexplicitinformationfromimplicitissuesandtopointoutwherefactualdataisunavailable.Constraintsplacelimitsonthecreationofboundariesanddecision-making.]

<>

UsageAnalysis

[Description:

TheUsageAnalysissectionlistsanddefinesthesolution’susersandtheirimportantcharacteristics.Italsodescribeshowtheuserswillinteractwiththesolution.Thisinformationformsthebasisfordevelopingrequirements.]

UserProfiles

[Description:

TheUserProfiledescribestheproposedsolution’susersandtheirimportantcharacteristics.Theusersareidentifiedingroups — usuallystatedintermsoftheirfunctionalareas.OftenusersarefromboththeIT（helpdesk,databaseadministration,etc.）andbusiness（accounting,warehouse,procurement,etc.）areasofthecustomer’sorganization.Theimportantcharacteristicsidentifywhattheusersaredoingthatthesolutionwillfacilitate.Thesecharacteristicscanbeexpressedintermsofactivities:

forexample,theaccountinguserreceivesinvoicesandmakespaymentstosuppliers.

Thissectionshouldcontainalevelofuserprofileinformationthatenablestheidentificationofuniquerequirements.

Justification:

Initially,UserProfilesenablethedevelopmentofusagescenarios（nextsection）.Beyondthat,UserProfilesprovidetheprojectteamswithvitalrequirementsinformation.AcompletesetofUserProfilesensuresthatallhigh-levelrequirementscanbeidentified.TheproductteamusestheseprofilesasinputwhendevelopingtheFeature/FunctionList.Thedevelopmentteamusestheseprofilesasinputtoitsarchitectureandtechnologydesignstrategies.Theusereducationteamusestheseprofilestoestablishthebreadthoftheirwork.]

<