技術(shù)電子商務(wù)建筑法

1、Technical e-business Architecture MethodTEAMPractice StepsTheIBM SignatureSelling MethodandTeAMethod arebasedupon alignmentwith thecustomerbuyingprocessSignatureSellingMethod:OutcomesSellCycleVerifiable OutcomesCustomerandIBM agreementtothevalueofarelationship.Customer-demonstratedinterestinworkingw

2、ith IBM.Customer-statedbusinessneed,buyingvision andagreementtosupport IBMaccesstoPowerSponsor.CustomerPowerSponsor andIBMagreement to go forwardwithapreliminarysolution.CustomerPowerSponsorsconditionalapprovalofproposedsolution.CustomerandIBM signacontract.Customeracknowledgesthe value of theIBMsol

3、ution.ldentifiedValidatedQualifiedProposedWonCompletedTEAM:WorkProductFormatTitlePurposeSIMethodwork productenabledDescriptionCreatingtheworkproductSampleworkproductTEAM:WorkproductDependency DiagramTEAM:TaskFormatTitlePurposeSIMethodtask enabledDescriptionAssociated workproducts/technique papersPha

4、se/Activity/Task(GSMethod Task)/WorkProducts(GSMethodWorkProducts)PlanEvaluateCustomers Business EnvironmentDefineBusinessContext,ValidateBusinessIssues andGoals(DefineBusinessContext &ValidateBusinessIssues andGoals)BusinessContext Diagram(Samename)Envisioned Goals andIssues(EnvisionedTO-BeBusiness

5、Goals)DescribeCurrent Organization(DescribeCurrent Organization)Current Organization(none)Develop PlanLinked to CustomersBusinessInitiativesDocumentI/TStandards(Document I/TStandards)InformationTechnology Standards(Same name)Analyze CurrentITInfrastructure(AnalyzeCurrent IT Infrastructure)Current IT

6、 Environment(CurrentITInfrastructure, moredetailed)Execute(part1)Develop Customer Interest,EstablishBuyingVisionObtainorDevelopBusinessRoadmap(Business ProcessModel)BusinessProcess Roadmap(Usesdifferentnotation)Gain Sponsorship(none)Project Description(ProjectGoals, ProjectEstimates andRisk Assessme

7、nt)DemonstrateBusinessBenefits,Capabilities,QualifyOpportunityOutline Solution Requirements(Defineand categorizerequirements,Developarchitecture overview,Establishsystemcontext,IdentifyKey usecases)Non-FunctionalRequirement(Same name)SystemContextDiagram(Samename)Architectural Decisions(Same name)Us

8、eCaseModel(Same name)AssessInitialViability(Assess InitialViability)ViabilityAssessment(Same name)Phase/Activity/Task(GSMethod Task)/WorkProducts(GSMethodWorkProducts)Execute(part2)Develop Solution withCustomerDevelop ArchitectureOverview(Same name)ArchitectureaLDecisions(Samename)ArchitectureOvervi

9、ewDiagram(Same name)SurveyAvailable Assets(Same name)AvailableAssetList(CandidateAssetList)Develop HighLevelComponent Model(Samename)ComponentModel(Samename)Develop Operational ModelOperationalModel(Same name)RefineViability Assessment(Refine ViabilityAssessment)Updated ViabilityAssessment(Samename)

10、RefineSolution, ResolveConcerns, Close SaleAssessBusinessImpact(Samename)Updated ViabilityAssessment(Samename)EnsureClient Commitment(Samename)Updated ProjectDescription&Updated ViabilityAssessment(ProjectGoals,ProjectEstimatesand RiskAssessment)EvaluateIntegrated Solution(Evaluate IntegratedSolutio

11、n,Create TechnicalPrototype)Updated ProjectDescription&Updated ViabilityAssessment by theSolutionReviewrecommendations,andthe resultsfroma prototype,POC,orperformancetestPhase/Activity/Task(GSMethod Task)/WorkProducts(GSMethodWorkProducts)ImplementMonitor Solution Implementation,EnsureExpectations A

12、reMetMonitor Pilot(None)Updated ViabilityAssessment(Samename)Evaluatesuccess(None)Updated ViabilityAssessment(Samename)Harvest Assets(None)Phase/Activity/Task(GSMethod Task)/WorkProducts(GSMethodWorkProducts)ValueofTeAMethodWorkProductsforSWITAsTheValueofTeAMethodHelpsyoubreakalargeproject intomanag

13、eablechunksGivesyoutimetothinkHelpstransition to other SWITAs,IGS,ITS,AIM Services &SolutionAssuranceHelpsyourememberwhereyou leftoff withacustomer!BUSINESSCONTEXT DIAGRAM:Helpsdefinethe scope of theprojectHelpsyouunderstandthecustomersbusinessprocesses, leadingtoabettersolutionHelpsyouunderstandthe

14、relationshipsbetween thetargetbusinessentitiesand processesandotherentities/processesIdentifies potentialsysteminterfacesCURRENT ORGANIZATION:Helpsqualify theopportunity:areweinatthe right level of theorganization?Identifies(potential)sponsors,powersponsors,andenemiesIdentifies personswho shouldbein

15、volvedinthesalesprocessandwhattheirrolesshouldbeIdentifies additionalopportunitiesHelpsidentifysysteminterfacesBUSINESSPROCESS ROADMAP:Helpsyouunderstandthecustomerscurrent andproposedbusinessprocesses, leadingtoabettersolutionHelpsyoubuildcredibilitywiththecustomerbydemonstratinganunderstanding of

16、their keybusinessprocessesHelpsyoumoreeffectivelycommunicatewith thecustomerandthe clientteam regardingthecustomersbusinessobjectivesENVISIONED GOALS &SSUES:Documentsyou agreementwith thecustomerontheirgoals,issues,andCSFsProvidesa basis forassessingthe successofthe projectProvideshigh-level functio

17、nalrequirements foryour useindesigningthe solutionHelpsItseethe bigpicture (theyre usuallyfocusedonimmediatedeliverables)ITSTANDARDS:Provides“givens” to be consideredinyoursolutionHelpsyoueliminate unfeasibleoptionsupfrontIdentifies competitors andopportunities forcompetitive“replacements”(e.g.Oracl

18、e-DB2UDB)HelpsIDskillsand educationrequirementsHelpsIDcurrent assetsCURRENT IT ENVIRONMENT:Guidesyou architecturedecisionsIdentifies candidatesfor re-useProvidesa starting point fortheto-bearchitecture pictureIdentifies systemintegrationrequirementsHelpsdefinetransition/release strategy to minimize

19、riskHelpsdeterminethe sophistication of environmentPROJECT DESCRIPTION:Communicatesthe projectsgoalstoallparties;answersthequestion:“whatare we doing on thisprojectandwhy?”Helpsensureagreement to theproject goalsIdentifies issuesearlyonintheprojectProvidesa basis fordevelopmentofthearchitecturabas s

20、olutionSYSTEMCONTEXTDIAGRAM:Identifies scope boundariesDefines interfacerequirementsHelpsidentifypotentialinterface solutionsUSECASEMODEL:Providesfunctional requirementsfordevelopmentofyoursolutionProvidesa processfor validatingaproposedsolutionHelpsinplanninga PoCPrioritizes/categorizessystemcapabi

21、litiesHelpsdefinereleasestrategyIdentifies userand systeminterfacesUseCaseDescriptionhelpsdescribe(intext)thesystemsresponsibilities.NON-FUNCTIONALREQUIREMENTS:Documentscriticalrequirements likeperformance, security,andavailability thatmustbemetbythe proposed solutionHelpsvalidatetheproposedsolution

22、Providesa basis forestimating thesize andcost of theproposedsystemFirstsign of potentialsoftwareproduct requirementsVIABILITYASSESSMENT:Helpsyoudetermine theprobabilityofsuccess fora proposed solutionHighlights issuesandrisksearlyon, whentheyaremoreeasilyresolvedARCHITECTURAL DECISIONS:Providesyour

23、rationaleforincluding IBMcontent in thesolutionLets youpositionIBMcontenttocustomerswithin an architecturalcontextCommunicatesthe foundationfor yourchoicestotheimplementors suchasIGSARCHITECTUREOVERVIEWDIAGRAM:Communicatesthe architecturesolution“vision”toall partiesIdentifies theIBMand third-party elements of theproposedsolutionProvidesinputtofollow-ondesign andimplementationworkThis is where themagichappensUseseveralviewsdependingonthe audienceAVAILABLEASSETLIST:Hel