Solutions Architecture Framework - California

1 Office of Systems Integration (OSI) OSI Solution Architecture Framework z z z z z z z z Enterprise Service Center April 2008 California Health and Human Services Agency California Health and Human Services Agency Office of Systems Integration (OSI) Revision History REVISION HISTORY REVISION/WORKSITE # DATE OF RELEASE OWNER SUMMARY OF CHANGES Version April 24, 2008 EAO Initial Release Approvals Name Position Date Crystal M. Cooper Chief Information Officer, OSI 4/24/2008 OSI Solution Architecture Framework ( ) i California Health and Human Services Agency Office of Systems Integration (OSI) Table of Contents 1 INTRODUCTION .. 1 2 SOLUTION Architecture Framework (SAF).

2 1 3 VISION AND 2 4 SAF 2 5 PROGRAM CONSTRAINTS AND DEPENDENCIES .. 5 6 Solutions Architecture Framework 6 Framework 7 Architecture 7 REFERENCE 8 SOLUTION/ENTERPRISE Architecture 8 Architecture AND LIFE CYCLE 9 SAF ROLES AND 10 7 THE OSI SOLUTION Architecture DEVELOPMENT 11 11 11 UTILIZING THE TEMPLATES TO SUPPORT A 12 ENTERPRISE Architecture OFFICE SUPPORT 12 Architecture 12 Architecture RESEARCH AND 12 EA KNOWLEDGE 13 8 SOLUTION Architecture QUALITY 13 VALIDATION AND VERIFICATION PROCESS FOR NEW DEVELOPMENT 14 VALIDATION AND VERIFICATION PROCESS FOR MAINTENANCE & 14 9 REFERENCES .. 15 Appendices APPENDIX A - SAF TOOLKIT .. A-1 APPENDIX B - ACRONYMS AND B-1 OSI Solution Architecture Framework ( ) iiCalifornia Health and Human Services Agency Office of Systems Integration (OSI) OSI Solution Architecture Framework ( ) iii List of Tables TABLE 1: EA AND PROJECT RESPONSIBILITIES.

3 10 TABLE 2: IV&V TASK/ROLE 14 List of Figures FIGURE 1: THE SOLUTION Architecture Framework ..6 FIGURE 2: SOLUTION Architecture AREAS ..7 FIGURE 3: ENTERPRISE Architecture SEGMENTED FIGURE 4: SOLUTION Architecture INTERFACES WITH THE SDLC AND PLC ..9 FIGURE 5: SAF AREAS OF 10 FIGURE 6: Architecture DELIVERABLE 12 FIGURE 7: VERIFICATION AND VALIDATION California Health and Human Services Agency Office of Systems Integration (OSI) 1 INTRODUCTION The Enterprise Architecture Office (EAO) within the Enterprise Services Center (ESC) was created to establish an Enterprise Architecture (EA) program that will provide a consistent Architecture development approach and methodology for use within Office of Systems Integration (OSI).

4 The EA program seeks to help Project Offices position themselves to produce Solutions that maximize the value of project outcomes for the Sponsor and the customers they serve. OSI s primary mission is to help the sponsor achieve their business strategy by enabling successful project delivery. The Solution Architecture Framework (SAF) expands OSI s support to these Project Offices by providing a set of EA best practices to be used during the Project, Procurement, and System Development Lifecycles. Project Office solution architects use the guidance and tools that the SAF provides to implement EA best practices and produce a project solution along with a standard set of Architecture deliverables. These deliverables are blueprints that guide the project team s development activities to insure delivery of a solution that meets the sponsor s business needs and produces value to the enterprise (State, Agency, or Department) by delivering common Solutions and standardized components that can be reused where possible.

5 This Framework offers an end-to-end process to initiate, plan, and sustain a project s procurement and development activities. Establishing this Framework is not a one-time event but it must be continuously improved and maintained to insure the Framework remains relevant and useful. 2 SOLUTION Architecture Framework (SAF) A Solution Architecture Framework establishes a systematic approach for creating a roadmap to achieve a project s mission and to attain a solution with optimal performance of its core business processes delivered within an efficient Information Technology (IT) environment. Solution Architecture development is driven by the business needs that require the delivery of services. The result is the creation of business views from different perspectives that generate information required by decision makers.

6 A Solution Architecture defines the business-technology alignment and statewide service delivery, security, data sharing, and integration. Solution Architecture best practices help identify opportunities to lower costs, by effectively using existing State and project resources. A Solution Architecture draws a subset of information from the sponsors and the State s Enterprise Architecture Program to furnish information about the organization s business, data, service (application), and technology to create a discrete solution for a project. Using these four areas, project Solutions are created that: 1) Define the business services, functional requirements, and processes; 2) Identify the information (data) necessary to implement business services; 3) Establish the service (application) Architecture required to provide business services and information; 4) Determine the technologies necessary to deliver the business services and information.

7 The Framework offers processes, checklists, and templates to be used during lifecycle activities to generate a set of architectural deliverables. These deliverables guide development efforts and deliver a viable business solution to meet the sponsor s stated requirements. This Framework leverages existing work performed by other groups and is compatible with existing Architecture programs such as the California Enterprise Architecture Program (CEAP) and the Federal Enterprise Architecture Program (FEAP). The Framework provides a set of principles to help make supportable and consistent decisions. The following Architecture Principals are used to consider potential investment and architectural decisions. OSI Solution Architecture Framework ( ) 1 California Health and Human Services Agency Office of Systems Integration (OSI) Business Drives Information Technology Just Enough Architecture , Just in Time Common Business Solutions Data is an Enterprise Asset Secure Enterprise Information Compliance with Statewide Standards Compliance with Law Use of the SAF generates a standardized and consistent set of Architecture deliverables for each project that EAO will merge into an overall OSI EA repository.

8 Repository information will provide a knowledge base that allows future projects the ability to reuse EA information and identify potential shared services. Additionally, those Architecture deliverables are provided to project sponsors for use in their respective EA Programs. 3 VISION AND BENEFITS Vision To focus and improve EA support to further enable project decision making regarding business needs and IT service delivery in the context of a discrete service solution. Benefits Leverages existing documentation being developed to satisfy Federal, State, and Agency Architecture Requirements. Improves alignment of IT with the project sponsor s missions, goals, and objectives. Improves statewide service delivery and business operations.

9 Lowers costs and improves security, reliability and performance of the OSI customer s IT infrastructure. Improves statewide data sharing and systems interoperability. Furnishes more effective use of State resources to effective delivery of services to the citizens of California . Helps reduce the occurrence of unnecessary duplication of business service Solutions , infrastructure, and information silos. 4 SAF PRINCIPLES Business Drives Information Technology Rationale IT direction will be driven by what the business needs to serve their customers. Business events represent the essential activities that define the boundaries of a good information technology environment. Without knowing the business, the IT infrastructure may be over or under built which can result in excessive technical complexity, cost and delays.

10 This principle will foster an atmosphere where the information environment changes in response to the business needs, rather than having the business change in response to IT changes. Technology changes provide an opportunity to improve the business process and hence, change business needs. OSI Solution Architecture Framework ( ) 2 California Health and Human Services Agency Office of Systems Integration (OSI) Implications Minimize unintended effects on business due to IT changes Build what we need, not what we want Easier to identify technical impacts when business events change Must include the business and its perspective in the Solutions development process Just Enough Architecture , Just in Time Rationale This approach allows development of enterprise Architecture where it is needed most instead of systematically developing Architecture information in all areas of the enterprise (business, data, service (application), and technology).