introduction - rutgers university architectur… · web viewpmo architecture design, ver 8.0 ...

<Project Name>Architecture Design

Table of Contents

1 Introduction............................................................................................................................21.1 Purpose...........................................................................................................................2

1.1.1 Intended use............................................................................................................21.2 Assumption.....................................................................................................................21.3 Intended Audience..........................................................................................................2

2 Version Control......................................................................................................................33 System Architecture...............................................................................................................4

3.1 Network Architecture.......................................................................................................43.1.1 Current Process.......................................................................................................43.1.2 Proposed Process...................................................................................................5

3.2 Server Architecture.........................................................................................................53.2.1 Current Process.......................................................................................................53.2.2 Proposed Process...................................................................................................6

3.3 Interface Architecture......................................................................................................63.3.1 Current Process.......................................................................................................63.3.2 Proposed Process...................................................................................................7

4 Connectivity Matrix.................................................................................................................85 Aliases....................................................................................................................................96 Load Balancing....................................................................................................................107 Security................................................................................................................................118 Server Requirements...........................................................................................................129 Approvals.............................................................................................................................13

1

PMO Architecture Design, ver 8.0

1 Introduction

1.1 Purpose

The purpose of this document is to outline the project architecture, installation, and configuration procedures with the following goals:

Provide a general description of the system Describes the logical architecture of the application/software Describes the physical architecture of the environment(s) on which the software runs Provide proof of alignment between the architecture and systems requirements

1.1.1 Intended use

Documenting architecture facilitates communication between stakeholders, documents early decisions about high-level design, and allows reused of design components and patterns between projects.

1.2 Assumption

There are no assumptions being made for this document.

1.3 Intended Audience

This document is intended to be reviewed and understood by all participants and resources for the project, including but not limited to roles identified in the project charter.

2


2 Version Control

Version Date Person Change1.0 MM/DD/YYYY Initial Document Creation

3


3 System Architecture

Descriptions of the system are provided in this section using diagram(s), storyboard(s), flowchart(s), and/or any other visually descriptive documents with corresponding narrative that depicts the flowing aspects of the application and/or system.

The following parameters should be considered and provided for in Architecture Design:

Performance: Localize operations Security: Use of layered architecture with critical assets in inner layers Safety: Isolate safety-critical components Availability: Included redundant components in the architecture Maintainability: Use of self-contained components Requirements Mapping: Provide partitioning and algorithms/processes and allocate all

present/foreseeable requirements into discreet partitions so that the communication between components and between the user/systems is optimized.

System Partitioning: Partition large systems into (successive layers of) subsystems and components each of which can be handled by an individual or team of subordinate architects.

Database Schemas: Detail the structure of the database. Solution Alternatives: Identify alternative system concepts, configuration items, and

system elements.

3.1 Network Architecture

A high level architecture of system components.

3.1.1 Current Process

Provide diagram(s), storyboard(s), flowchart(s), and/or any other visually descriptive documents with corresponding narrative of the current network architecture if available.

4


Note: The diagram below has been provided for illustrative purposes only and should be replaced with a diagram specific to the project.

3.1.2 Proposed Process

Provide the same as above for the proposed network architecture.

3.2 Server Architecture

Describe the hardware/VMware components and workflow.


Provide a diagram and narrative of the current server architecture if available.

5




Provide the same as above for the proposed server architecture.

3.3 Interface Architecture

Provide software component relationships and data flow.


Provide diagram(s), storyboard(s), flowchart(s), and/or any other visually descriptive documents with corresponding narrative of the current network architecture if available.

6




Provide the same as above for the proposed server architecture.

7


4 Connectivity Matrix

Note: Once IPs for instances are known, this table must be updated

Source Source IP Destination

Destination IP

Destination Port Type Comments

8


5 Aliases

Component CNAME (alias)

9


6 Load Balancing

Document load balancing requirements

Provide a diagram and narrative if available.

10


7 Security

Please document any additional security needed due to any of the architecture identified in the above steps.

11


8 Server Requirements

Server Name Size OS Managed by

VLAN(If using single

VLAN leave blank)

Notes (network, sw versions, accts,

permissions)

12


9 Approvals

The individuals below agree that they have reviewed and approved the plan outlined in this Support Documentation.

APPROVED BY:Project Role Name and Title Approval Date

13


introduction - rutgers university architectur… · web viewpmo architecture design, ver 8.0 ...

Documents