EPLC_Architecture_Doc_v . .doc

SUBJECT \* MERGEFORMAT System Architecture

Version: 1.0 Error! Unknown document property name.

Food and Drug Administration

<Project Name & Release Version #> Enterprise Performance LifeCycle

SYSTEM ARCHITECTURE

Document Version Number: <1.0> Document Version Date: <mm/dd/yyyy> Notes to the Author

[This document is a template of a System Architecture document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.

· Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

· Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.

· Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

When using this template, the following steps are recommended:

1. Replace all text enclosed in angle brackets (e.g., <Project Name>) with the correct field document values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected) select File->Properties->Summary and fill in the appropriate fields within the Summary and Custom tabs.

After clicking OK to close the dialog box, update all fields throughout the document selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update each field individually by clicking on it and pressing F9.

These actions must be done separately for any fields contained with the document’s Header and Footer.

2. Modify boilerplate text as appropriate for the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click on it and select “Update field” and choose the option - “Update entire table”.

5. Before submission of the first draft of this document, delete this instruction section “Notes to the Author” and all instructions to the author throughout the entire document.

VERSION HISTORY

[Provide information on how the development and distribution of the System Architecture document will be controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.] Version Number Implemented

By Revision

Date Approved

By Approval

Date Description of Change

Table of Contents 41.0 Executive Summary

42.0 Purpose of a System architecture

43.0 As-Is Characterization

43.1 Performance

43.2 Processes

53.3 Process Enablement & Automation

54.0 To-Be ARCHITECTURE

54.1 Performance

54.2 Processes

64.3 Data

64.4 IT Systems and Services

74.5 Technologies

75.0 transition description

75.1 Process Improvements

75.2 Data Improvements

75.3 IT System and Services Improvements

85.4 Technology Improvements

85.5 Timeline / Release Schedule

9APPENDIX A: SYSTEM ARCHITECTURE APPROVAL

10APPENDIX B: REFERENCES

11APPENDIX C: KEY TERMS

1.0 Executive Summary

[In one paragraph, describe the major changes to performance, processes, data, applications, services and technology that this system will provide. Highlight not only the changes, but also the reason for the change. Be sure that all changes are further detailed in the below sections.]

2.0 Purpose of a System architecture

The purpose of the System Architecture is to document and understand the motivations and impacts of all system improvements, and modifications proposed by the project. Understanding the motivations will help the project team focus on delivering intended business value while understanding the impacts will ensure the solution is will not negatively effect the existing environment. This general understanding of the reasons for and impacts of change will help guide the project and ultimately improve the project success rate.

The intended audience of the <Project Name> System Architecture is all project stakeholders including the project sponsor, senior leadership and the project team.

3.0 As-Is Characterization

3.1 Performance

[In the table below, document the current business performance measures that are or will be enabled by this system and their current values. List from one to five the most relevant measures.]

3.2 Processes

[Document the current key project business processes. If available, list the processes described in the Business Process Model Artifact.]

· <Major Process A>

· <Sub-Process>

· <Sub-Process>

· <Major Process B>

· <Major Process C>

· <Sub-Process>

3.3 Process Enablement & Automation

[Describe how each process is currently automated. Explain how IT is supporting the relevant business processes and performance measures.]

4.0 To-Be ARCHITECTURE

4.1 Performance

[In the table below, document the target key system performance measures and their target values. List from one to five the most relevant measures. Each measure should clearly state the timeframe in which the qualitative target measure should be achieved. Focus on what this project is trying to accomplish.]

4.2 Processes

[Document the target key project business processes. These processes should be the same as the as is processes, with some potential adjustment for scope increases or decreases. If available, list the processes described in the Business Process Model Artifact.]

· <Major Process A>

· <Sub-Process>

· <Sub-Process>

· <Major Process B>

· <Major Process C>

· <Sub-Process>

[Describe any changes to the process and how each process will be automated.]

4.3 Data

[In the table below, describe the data objects used or exchanged by the above processes. If available, list the data described in the Business Process Model Artifact.]

4.4 IT Systems and Services

[In the table below, describe the IT systems that will automate the above business processes. If available, use the list of IT systems within the Project Characterization Section of the Project Management Plan.]

[Refer to the list of Applications/IT Systems in the HHS Enterprise Architecture Repository (HEAR) for reference.]

[Refer to the OMB Service Reference Model (SRM) for reference.]

[In the table below, describe new services to be developed by the project. These should include only service-oriented services, those that are published and usable by other FDA IT systems.]

4.5 Technologies

[In the table below, describe the technologies to be used by the above IT systems.]

5.0 transition description

[This section should highlight the major differences between the as-is characterization and the to-be characterization. This section should clearly show what the project intends to change or improve and a high level timeline / release schedule.]

5.1 Process Improvements

[Briefly describe what new process will be supported or automated. Describe any changes to the existing process.]

5.2 Data Improvements

[Briefly describe new data and data standards used.]

5.3 IT System and Services Improvements

[Briefly describe new IT systems, enhancements to existing systems, and all new service offerings.]

5.4 Technology Improvements

[Briefly describe new technologies to be implemented by this project.]

5.5 Timeline / Release Schedule

[Develop a release schedule providing the IT system, version, and date of the release.]

APPENDIX A: SYSTEM ARCHITECTURE APPROVAL

The undersigned acknowledge that they have reviewed the <Project Name> System Architecture and agree with the information presented within this document. Changes to this System Architecture will be coordinated with, and approved by, the undersigned, or their designated representatives.

Signature:

Date:

Print Name:

Title:

APPENDIX B: REFERENCES

[Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.]

The following table summarizes the documents referenced in this document.

APPENDIX C: KEY TERMS

The following table provides definitions and explanations for terms and acronyms relevant to the content presented within this document.

Template Version 2.0 (Last Modified on Mar 30, 2009)

PAGE

Revision Date: Error! Unknown document property name.

EPLC_System_Architecture_Template.doc