Enterprise architecture (EA) is the strategic framework driven by the business of the commonwealth enterprise comprised of business strategies, visions and goals.
The framework establishes a process focused on building and maintaining an enterprise-wide business, information, solutions and technical infrastructure that is adaptable and best enables the service activities of state government in an ever-changing environment.
The goal of EA is to create a common and cohesive vision among business and technology leaders about:
The commonwealth's EA contains four primary component architectures as seen in Figure 1:
For more information about EA and its impact on your technology programs and projects, please see the following EA policy documents:
The enterprise business architecture (EBA) documents the business strategy, governance, organization and business functions of Virginia state government. EBA also establishes a baseline that defines which organizations perform these functions.
EBA provides a holistic view of our state government from a business perspective that defines who we are, what we do and where we want to go. It also provides a common reference model for citizens, businesses, members of the General Assembly, current and future administrations, and other interested parties that helps define the business of state government.
EBA provides primary drivers for developing other EA component architectures. These drivers include:
Enterprise information architecture (EIA) provides the framework, model, and method to enhance each agency's ability to quickly discover, access, and understand data, while creating the information needed to support critical agency business function decisions.
The EIA framework has three components that contain information about the commonwealth's data assets:
In its simplest terms, the EIA Framework has three components that will contain information about the Commonwealth's data assets.
EIA answers questions such as:
Government expectations to deliver more services better and more economically have never ended. These high expectations present understandable challenges for Virginia. Well-engineered, cloud, and/or automated solutions can increase productivity that supports superior service delivery. Commonwealth agencies make significant investments in such solutions to improve the business of state government.
The commonwealth enterprise solutions architecture (ESA) provides the framework, model and method supporting transitions from silo-based, application/agency centric, and on premise IT investments, to an enterprise and cloud approach where solutions are flexible, scalable, and cloud enabled. Agencies are then able to take advantage of shared and reusable components, facilitate the sharing and reuse of their data where practical, appropriate, and lawful, and make best use of available technology infrastructure.
The ESA needs to contain a unified view of solutions to achieve this increase in reuse and reduction of solution complexity. The unified view of solutions includes the business (EBA), information (EIA), and technology (ETA) perspectives. To support this unified view, the ESA method includes inventories, governance, and the relationships between agency applications and other EA component architectures.
An ESA is the collection of information systems supporting or related to the business functions defined in the EBA and the enterprise business model, including applications and components that are purchased or custom-developed.
The unified view of solutions includes the Business (EBA), Information (EIA) and Technology (ETA) perspectives. This view also shows how agency solutions/applications connect to:
The ESA includes:
The word solution as defined by the VITA document, Creation of Solutions' Business Case Process document is as follows:
A solution is a:
In virtually every case, a solution addresses a specific business problem, or other need.
An ETA is a consistent set of IT standards, and models that:
For more information, please contact the VITA EA team at: email@example.com.