DEADONS

Friday, December 9, 2005 xxx

Agenda

DEADONS Definition DEADONS Future State

Development Execution Application Data Operations Network Security

EDMS

Page 2

The DEADONS framework is used to segment the company architectures..

DEADONS is a framework developed by DEADONS is a means to organize all the characteristics of an organization architecture DEADONS spans both software and infrastructure architectures DEADONS is a framework to describe a specific static condition of the organization architecture Current State or As Is - critical condition of all architectures Future State architecture

Development

Data Execution Network

EDMS

Operations
Page 3

Application Security

DEADONS
DEADONS is XXXXXXXXs framework to assess technology architectures using a standard, repeatable process and to develop technology architectures making sure design dominates the entire process. DEADONS focuses on seven components of an organizations technology architecture:
Definition, specification and location of business processes and the supporting infrastructure components

Tools, services, and strategy to address data definition and layout, data location and redundancy decisions, data update/refresh approach, data security, data backup and recovery, and DBMS performance Tools, support services, controls and procedures to manage the operation of the production, execution and development environments

Development

Unified collection of tools, techniques and methodologies to build and integrate applications

Data Execution Network

Operations

Application Security

Standards that define the roles, rules and mechanisms governing access to resources

Reliable network services to support the implementation of solutions

Structured environment and services for executing application and business processes

EDMS

Page 4

The DEADONS based architectural analysis has several key goals

Identify common services across the company Identify key architectural elements(Interface, Data) of applications Identify key infrastructure systems and their location Identify the run time environment and the key interfaces with external partners Identify the major tools utilized across the company Identify the development policies and methodologies across the company

EDMS

Page 5

Application Data

t ne m o ev e D pl

Network

Definition: The development architecture defines the software, tools, and facilities to support rapid prototyping and development of software within the company A best practice development architecture should: Establish a Program and a Project management process for development programs incorporating both version control and release management Provide a framework that allows the same development and testing methodology to be used for custom and package application development Define an outline for the identification, prioritization, evaluation, and selection of development tools required to support the framework Identify the requirements for lab environments to support testing of hardware, software, and network solutions and facilitate partnering with vendors Create an environment to support controlled development of applications with automated change control and configuration management tools Provide guidelines to support benchmarking of all custom and package applications Define a standard testing process to minimize the functional, performance, and production risks Define a standard process to ensure a controlled, high quality release of new features and capabilities

EDMS

Page 6

s not a ep O i r

Development Architecture

yi r uc e S t

Execution

 Insert Development Architecture

Sub Category
Testing Capabilities Change and Configuration Management Integration/ Staging Environment Construction Tools Development Management Development Methodology

EDMS

Page 7

Application Data

t ne m o ev e D pl

Network

Definition: The execution architecture defines a structured operating environment, hardware platforms, operating system software, and system services for executing application and business processes A best practice execution architecture should: Provide for integrated processing across the company and the capability to scale platforms to support business growth and service expansions Combine complementary, scaleable and integrated platforms to support company-wide application processing Provide an open platform as defined by current industry standards Provide system level security to prevent unauthorized access to computing resources Allow consolidation of current server platforms Facilitate management of both implementation and operational costs

EDMS

Page 8

s not a ep O i r

Execution Architecture

yi r uc e S t

Execution

 Insert Execution Architecture

Sub Category
Hardware Platforms Operating Systems

Presentation Services Network Operating System File, Print and Storage Services

Application Services Messaging/ Integration Services

EDMS

Page 9

Application Data

t ne m o ev e D pl

Network

Definition: The application architecture defines the standards, services, and components to support the development of custom and package software solutions A best practice application architecture should: Utilize a layered, component-based architecture Re-use business concepts across multiple applications and platforms Require consistency in the definition of business concepts and rules Allow for greater consistency to our customers and greater speed to market with new products and services Create application flexibility and adaptability Develop new business components to run in the environments as specified by the Execution Architecture Enable data warehouse capabilities to be built using purchased software toolkits consistent with the execution, application, and data architecture Provide a framework to facilitate the identification, prioritization, evaluation, and selection of components, products, and techniques for applications
EDMS Page 10

s not a ep O i r

Application Architecture

yi r uc e S t

Execution

 Insert Application Architecture

Sub Category
Integration Openness Platform Interoperability Reliability and Recoverability

Security Distribution of Processing Processing Separation Functional Decomposition Application Structure

EDMS

Page 11

Application Data

t ne m o ev e D pl

Network

Definition: The data architecture defines the tools, strategy, and services to address data definition and layout, data location and redundancy decisions, data update/refresh approach, data security, DBMS performance, and data backup and recovery of information assets. A best practice data architecture should: Define the distribution of data across the company to satisfy the processing demands and information requirements at all locations Ensure data ownership (create, read, update, and delete) across the applications in the company is understood Provide an company data model to support both OLTP and OLAP processing Define a processing environment that ensures data integrity Provide appropriate security and confidentiality of all data assets Define tools to support data manipulation and definition using meta-data Cost effectively scale databases to support users demands Separate transaction data from analytical data
EDMS Page 12

s not a ep O i r

Data Architecture

yi r uc e S t

Execution

 Insert Data Architecture

Sub Category
Business Rules Data Definitions Meta-data Management Distribution & Redundancy

Integrity Ownership Database Design Data Distribution

EDMS

Page 13

Application Data

t ne m o ev e D pl

Network

Definition: The operations architecture consists of a combination of tools, support services, controls, and procedures required to manage the operation of the production environment and development environments across the company A best practice operations architecture should: Provide the ability to manage operational platforms throughout the company Provide secured access to resources based upon established security policies with centralized administration Provide platform availability and performance consistent with established service level agreements Protect information assets in the event of a disaster Create a framework defining the technical environment, tools, and procedures to support the management of distributed platforms Provide the ability to manage operational platforms throughout the company Define attributes and functionality of the tools used to proactively manage production application systems
EDMS Page 14

s not a ep O i r

Operations Architecture

yi r uc e S t

Execution

 Insert Operations Architecture

Sub Category
Production Scheduling Monitoring and Event Management Software Distribution and Management Service Level Management Disaster Recovery Help Desk and Escalation Ops Documentation & Training for Ops Personnel Other Operational Processes

EDMS

Page 15

Application Data

t ne m o ev e D pl

Network

Definition: The network architecture defines the strategy and components to provide reliable local area networks (LAN), wide area networks (WAN), mobile access, and Internet access that supports the implementation of an n-tier architecture A best practice network architecture should: Provide reliable access to information assets based upon processing requirements and established service level agreements Enable scaleable networking components with the flexibility to expand as the business need grows Allow disaster recovery operations to be more easily implemented Ensure redundancy to minimize downtime or network failure Establish a single standard network protocol TCP/IP Facilitate upgrades to higher bandwidth for faster delivery of data Integrate network system diagnostics, event management, and alert capabilities Isolate infrastructure components from business processing components Require standard hardware, OS, and toolsets Create a framework to implement Service Level Agreements between business units and production control

EDMS

Page 16

s not a ep O i r

Network Architecture

yi r uc e S t

Execution

 Insert Network Architecture

Sub Category
Infrastructure Management Services Change and Configuration Management Performance Management

Platform Interoperability

Security Management Fault Tolerance and Resiliency

EDMS

Page 17

Application Data

t ne m o ev e D pl

Network

Definition: The Security Architecture consists of the combination of services, framework, access controls, and policies required to support the application and network architecture A best practice security architecture should: Provide secured access to resources based upon established security policies with centralized administration Define an audit and control policy Log all access attempts and extraordinary events across the company Prevent unauthorized access, vandalism, and destruction of mission critical data Protect company assets including intellectual capital, source codes, trade secrets Establish a security policy to regulate how the organization manages and protects computing resources to achieve security objectives Create a framework defining the security environment, tools, and procedures to tier protection of entire network Establish an intrusion detection system to proactively monitor and detect the malicious network activities
EDMS Page 18

s not a ep O i r

Security Architecture

yi r uc e S t

Execution

 Insert Security Architecture

Sub Category
Administration

Physical

Application

Network

Data Regular Risk Analysis and Threat Assessmt

EDMS

Page 19