Pennsylvania Department of HUMAN SERVICES

<System Name>

Technical Architecture

<System Name>

Technical Architecture

<Version #>

Revision History

Date	Version	Description	Author

Table of Contents

1.	Introduction	3

2.	Technology Architecture	3

2.1	Define Baseline Technology Architecture	3

2.2	Define Target Technology Architecture	3

2.3	Perform a Gap Analysis	3

2.4	Define Roadmap Components	3

2.5	Define Impacts to the Enterprise Architecture Landscape	3

3.	System Environments	3

3.1	Environment Support Services	3

4.	Security/User Administration	3

5.	Backups	3

6.	Restoring	3

7.	Archiving	3

8.	Online Processing	3

9.	Monitoring	3

10.	Fault/Problem Management	3

11.	Disaster Recovery	3

Introduction

[In this section, we provide a high level overview of the proposed future state solution architecture and a single integrated view of the system.

The focus is on the major systems in the solution and the channels through which the users may interact and should cover the following:

Motivations behind the architectural decisions so they can be robustly implemented and can guide the development of the resultant system

An overview of the architecture, as well as an understanding of the motivation behind the important technical decisions.

Also, provide a summary of the document highlighting the key points in each section, if applicable.]

Technology Architecture

[In this section, define the technology architecture design and implementation and map the application components, defined in the Application Architecture, into a set of software and hardware components required for that architecture.

The Technology Architecture section covers the following topics:

Define Baseline Technology Architecture

Define Target Technology Architecture

Perform GAP Analysis

Define Roadmap Components

Define Impacts to the Enterprise Architecture Landscape]

Define Baseline Technology Architecture

[Describe the baseline description of the existing Technology Architecture and show the components that are likely to be carried over into the target Technology Architecture. In remaining sections of this document, outlines are provided of the operational environments, network and network intrusion/protection.]

Define Target Technology Architecture

[Describe the target Technology Architecture and include the following components:

Technology components and their relationships to information systems

Technology platforms and their decomposition, showing the combinations of technology required to realize a particular technology "stack"

Expected processing load and distribution of load across technology components

Physical (network) communications

Informational Architectural components (including RDBMS’, ODS, Imaging, Reporting)

Hardware and network specifications]

Perform a Gap Analysis

[In this section, highlight any architecture components from the baseline to target technology architecture that have not yet been defined. These gaps can include:

Business domain gaps

Data domain gaps

Applications impacted, eliminated, or created

Technologies impacted, eliminated, or created

Define Roadmap Components

[This section defines the individual increments of change and lays them out on a timeline to show progression from the Baseline Architecture to the Target Architecture. It should provide a list of the projects impacted by these changes and how projects will migrate to the Target Architecture.]

Define Impacts to the Enterprise Architecture Landscape

[This section describes the impacts to the overall enterprise architecture landscape and identifies the following, if applicable:

How does this Technology Architecture create an impact on any pre-existing architectures?

Have recent changes been made that impact the Technology Architecture?

Are there any opportunities to leverage work from this Technology Architecture in other areas of the enterprise?

Does this Technology Architecture impact other projects (including those planned as well as those currently in progress)?

Will this Technology Architecture be impacted by other projects (including those planned and currently in progress)?]

System Environments

[This section identifies the physical infrastructure supporting the project environments and refers directly to the Enterprise Architecture and Application Blueprint diagram/document. That document depicts the physical servers that comprise each of the applications environments.]

Environment Support Services

[This section outlines the entire process flow of how a team requests environment infrastructure, how the environment is built and tested, and how the environment is maintained. As such, this section may point to a separate external process document that is maintained at an enterprise level.]

Security/User Administration

[This section outlines the security/user administration needed to support the technical architecture and should address the following topics:

Method of Authentication and Authorization (Security Access Policy)

User Profiles/Authorizations

User Account Creation

User Password Maintenance/Resets

Physical Security including transport security protocols

Approach to prevent security attacks such as SQL injection, XSS attacks (cross site scripting)

This section may also point to a separate external process document that is maintained at an enterprise level and outlines these procedures.

This section is outlined at a high level during the GSD phase and then elaborated in full detail during DSD}

Backups

[This section documents the backup procedures to be followed for the system, database, and application. This section may point to an external document that outlines these procedures at an enterprise level.]

Restoring

[This section documents the restoration procedures for the following: files, databases, applications, and system. This section may point to an external document that outlines these procedures at an enterprise level.]

Archiving

[This section document the system requirements for archiving system backups and other documentation, in addition describe the archiving solution is implemented. This section may point to an external document that outlines these procedures at an enterprise level.]

Online Processing

[This section lists the applications that can be accessed online and the user population that accesses those applications.]

Monitoring

[This section describes monitoring and monitoring reporting procedures, event logging and alarm features of an application. It also identifies the system monitoring tools or products used for that application/system.]

Fault/Problem Management

[This section outlines the procedures for resolving faults and problems reported by users, operations issues, system failures and failover. This section may point to an external document that outlines these procedures at an enterprise level.]

Disaster Recovery

[This section describes the Disaster Recovery (DR) procedures for the application or system. This section may point to an external document that outlines these procedures at an enterprise level.]