Presentation on theme: "<<Date>><<SDLC Phase>>"— Presentation transcript:
1<<Date>><<SDLC Phase>> Solution ArchitectureBlueprint and Review Preparation TemplateIN-PROCESS<<Project Name>><<Date>><<SDLC Phase>>
2Draft: Preliminary and Advisory-Not for distribution DirectionsDraft: Preliminary and Advisory-Not for distributionIN-PROCESSThe following template is provided for use during a Solution Architecture (SA) Review. The blue text provides guidance to the author and it should be deleted before publishing the document. When saving this file, save this as [date_projectname_SA_Review.ppt]. Delete this page prior to publishing the document
3Draft: Preliminary and Advisory-Not for distribution Table of ContentsDraft: Preliminary and Advisory-Not for distributionIN-PROCESSProject OverviewBusiness Process ImpactCandidate Solution ArchitectureKey AssumptionsKey Decision Points
4Draft: Preliminary and Advisory-Not for distribution Project OverviewDraft: Preliminary and Advisory-Not for distributionIN-PROCESSProvide a overview of the project to provide context for the reviewers.•If your project completed a project report for Portfolio Planning, you may chose to provide a copy of that document, and proceed with this template addressing only the architecture items requested.•Additionally throughout the preparation of this material, you may provide details for your solution by referencing other supplemental documents from your project workBusiness Background:Describe the business need for this solutionIncluding the goals and objectives of the projectTime Line:Provide high level milestones of the projectIncluding the current SDLC stage this project is in (if applicable), and target date for next stage gate completionScope & Approach:Provide high level description of the scope of this initiative and how it’s being approachedIncluding overview of project team involved and expected costs
5Draft: Preliminary and Advisory-Not for distribution IN-PROCESSRequired - Business Process Model/Blueprint, if applicableDescribe the Business Processes involved.If available, include any business process models or business solution blueprints (e.g. end to end process view, value chain diagrams, etc.), that are pertinent to the project team, to help describe the processes involved
6Draft: Preliminary and Advisory-Not for distribution IN-PROCESSThe following page(s) outlines the possible Architecture Approaches for developing the solution, starting with the recommended architecture followed by alternatives that were consideredRecommended Solution:Architecture Approach and RationaleDescribe the proposed architecture (Architecture Approach and Rationale). Highlight key architecture decisions such as technologies used, changes to the data model, etc.If applicable, include any architecture blueprints that have been developed to help describe the solution. These may include:Application architecture, e.g. an application component blueprintInformation architecture, e.g. a high level data flow modelTechnology Architecture, e.g. a infrastructure landscape diagramSecurity Architecture, e.g. a security modelBriefly describe why this solution was selected.Describe external providers and third-party relationshipsArchitecture TradeoffsDescribe any architecture trade-offs aligned with the architecture approach (e.g. performance, scalability, maintainability, etc.)
7Draft: Preliminary and Advisory-Not for distribution IN-PROCESSThe following page(s) outlines the possible Architecture Approaches for developing the solution, starting with the recommended architecture followed by alternatives that were consideredRisk/Issues and Mitigations:Describe any risks identified or outstanding issues.What is the impact of these and what gaps have been identified?What are the plans to address these?What are the implications beyond the scope of the project?What is the Solution’s lifecycle?What dependencies exist to other EA Assets which may conflict with the life-cycle?What dependencies exist with external providers or third parties (contracts, etc)Solution Alternatives (optional):Describe the alternatives (if any) that were investigated to meet the business requirements
8Draft: Preliminary and Advisory-Not for distribution IN-PROCESSOptional - Define specific concerns that you want the Solution Architecture Review to address
9Draft: Preliminary and Advisory-Not for distribution Key AssumptionsDraft: Preliminary and Advisory-Not for distributionIN-PROCESSProvide a list of key assumptions that were used to base choices around solution alternatives and trade-offs
10Draft: Preliminary and Advisory-Not for distribution IN-PROCESSWhat are the key decision points for the review team to consider and to provide its expert guidance?For each major architectural decision made for this solution so far, please describe:Issue: what is the issue under reviewAssumptions: List assumptions taken to reach decisionMotivation: List reasons why issue is being raisedAlternatives: List other possible solutions that were considered but not chosenDecision: State the Review Team’s decisionRationale: List reasons behind decisionYou may use the solution decision log template to capture these
11Draft: Preliminary and Advisory-Not for distribution IN-PROCESSBe prepared to provide an overview of the recommended solution’s business architecture. During the review, the Mission Domain perspective will be concerned with the following:What Mission Needs are affected?Who are the key stakeholders of the business processes affected?Are there integration points across core processes?What is the business problem that is to be solved and the associated goals?What criteria and metrics are to be used to measure the success of this initiative?Does this project involve changes to the business process?if so, please include as-is and to-be business models
12Draft: Preliminary and Advisory-Not for distribution IN-PROCESSIf applicable, be prepared to provide an overview of the recommended solution’s application architecture.During the review, the Application Domain perspective will be concerned with the following:Describe the impacted application capabilities at a high levelWas a Reference application architecture used, if applicableWas a current/in place application reused or is the application part of U-M’s application footprint?What is the data flow (application communication view) between applications (including legacy and third parties), application components, and external providers?Provide a mapping between application components being currently proposed and the accompanying business processesDoes the application have a current application portfolio risk assessment / category and /or road map?
13Draft: Preliminary and Advisory-Not for distribution IN-PROCESSBe prepared to provide an overview of the recommended solution’s information architecture. During the review, the Information Domain perspective will be concerned with the following:What are the key data entities involved in the solution?What applications are the system of record for each?Are these data entities Master Data objects?if so, is the MDM architecture being followed?What is the data migration plan and conversion process if applicable?Please provide any data models or data flow diagrams if they where created as part of this solution.If applicable to this solution, describe data relationships with other applications, external providers or third-parties.If this solution has a business intelligence or reporting components, is the BI Architecture being followed?Are data definitions and standards being followed for master and reference data?
14Draft: Preliminary and Advisory-Not for distribution IN-PROCESSBe prepared to provide an overview of the recommended solution’s Technology architecture. During the review, the Technology Domain perspective will be concerned with the following:Describe this solutions technical architecture (e.g. component diagram or technical specification)How does this solution fit with U-M’s technology reference architecture?Does this solution complement long term technology roadmaps? Does it vary from those roadmaps?What parts of the solution use shared resources? What parts are independent?What industry standards are being adopted? Where is an industry standard not being adopted?
15Draft: Preliminary and Advisory-Not for distribution IN-PROCESSBe prepared to provide an overview of the recommended solution’s security architecture. During the review, the Information Assurance perspective will be concerned with the following:Describe mechanisms used for Authentication, Authorization, Logging/Monitoring, Availability (e.g. clustering), and Asset Protection (e.g. encryption).Describe information assets, their sensitivity / classification, key regulatory attributes (e.g. privacy, financial reporting), and asset ownership, data retention, etcDescribe the physical, business, and regulatory environments into which the solution is expected to be deployedDescribe the distribution of solution components with a focus on data stores, communication pathways, and system identities (process IDs) used.Describe overall solution ownership, training plans, and support organization.Describe the significant risks in delivery and on-going operations of the solution.