PMM Orientation - Final Version 1.0_6/5/2006 Architecture Review Board <Enter Type of Review (Pre-Development, Pre-Deployment, COTS> Presentation <Enter Project Name and System ID> <Enter Date> Version <Enter Version #> Add project name and version number to master slide then delete this text box. Commonwealth of Pennsylvania

PMM Orientation - Final Version 1.0_6/5/2006 Agenda Project Overview Project Timeline High-Level Business Requirements Architecture Overview Use Case View Logical View Implementation View Deployment View Data View (optional) Capacity Requirements Compliance Issues and Mitigation Strategy Next Steps When you leave here, you’ll walk a little more easilyyou won’t be ready to run but you’ll have a better idea of your direction. Demystify the PMM

Project Overview <Provide an overview of the purpose, objective, deliverables, exclusions, stakeholders and interdependencies>

PMM Orientation - Final Version 1.0_6/5/2006 Project Timeline <Provide a high level schedule for the project including key milestones> What makes a project a “project”? How is the word “project defined? How is a project different from a process? What unique characteristics does a project have? 4

High-Level Business Requirements <Provide a description of the major business requirements>

Architecture Overview <Provide high level description of the relevant architecture component>

PMM Orientation - Final Version 1.0_6/5/2006 Use Case View <Provide a graphical overview of the use case architecture>

PMM Orientation - Final Version 1.0_6/5/2006 Logical View <Provide a graphical overview of the logical data model>

PMM Orientation - Final Version 1.0_6/5/2006 Process View <Provide a graphical overview of the process architecture> [This section describes the system's decomposition into lightweight processes (single threads of control) and heavyweight processes (groupings of lightweight processes). Organize the section by groups of processes that communicate or interact. Describe the main modes of communication between processes, such as message passing, interrupts, and rendezvous.]

PMM Orientation - Final Version 1.0_6/5/2006 Implementation View <Provide a graphical overview of the implementation architecture> [This section describes the overall structure of the implementation model, the decomposition of the software into layers and subsystems in the implementation model, and any architecturally significant components.]

PMM Orientation - Final Version 1.0_6/5/2006 Deployment View <Provide a graphical overview of the deployment architecture> [This section describes one or more physical network (hardware) configurations on which the software is deployed and run. It is a view of the Deployment Model. At a minimum for each configuration it should indicate the physical nodes (computers, CPUs) that execute the software and their interconnections (bus, LAN, point-to-point, and so on.) Also include a mapping of the processes of the Process View onto the physical nodes.]

PMM Orientation - Final Version 1.0_6/5/2006 Data View <Provide a graphical overview of the database architecture> [A description of the persistent data storage perspective of the system. This section is optional if there is little or no persistent data, or the translation between the Design Model and the Data Model is trivial.]

Compliance Issues and Mitigation Strategy PMM Orientation - Final Version 1.0_6/5/2006 Compliance Issues and Mitigation Strategy <For each section/category of the Architecture Review Checklist, describe any area that is not in compliance (I.E. anything with a “N” compliance indicator). Provide a summary of the variance and a strategy to mitigate the non-compliant issue. Repeat this slide as necessary to address all currently known architecture issues. Delete this instruction> <Enter Category – ex. Business, Access, Application, Security, etc.> Issue Mitigation Strategy

PMM Orientation - Final Version 1.0_6/5/2006 Next Steps <Summarize the next steps required to move this project forward>

Questions?