Pegasystems Implementation Methodology Overview

! Copyright 2006 Pegasystems Inc., Cambridge, MA

All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and product are protected by copyright and distributed under licenses restricting their use, copying distribution, or transmittal in any form without prior written authorization of Pegasystems Inc. This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services described. This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems service consultant. For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or product names are trademarks of their respective holders. Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors. This document could contain technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in the information described herein at any time.

This document is the property of: Pegasystems Inc. 101 Main Street Cambridge, MA 02142-1590 Phone: (617) 374-9600 Fax: (617) 374-9620 www.pega.com Document Version 2.0 Date Published: October 2006

Implementation Methodology
The objective of this document is to identify and document a high level understanding of the business functions and system components involved in delivering the business and technical benefits outlined in the Business Value Assessment (BVA). The scope of the business functions and components will be leveraged to develop a firm estimate of the requirements phase and a sizing estimate for the overall project. The overall sizing effort will be refined and a firm estimate for the overall project will be delivered after the Requirements Phase.

Summary of Pegasystems Implementation Methodology

Overview
The implementation methodology is derived from the Rational Unified Process Object Oriented implementation method (RUP). The RUP methodology has been modified and simplified to ensure the implementation team meets project scope, time lines, and budget. The approach leverages an iterative delivery approach that accelerates the ability for the business community to participate and have access to key system capabilities early in the construction phase. This enhances the effectiveness of the project to deliver on the Business Value Assessment (BVA) benefit expectations. This process produces the minimal artifacts and follows the optimum scope, requirements, design, and construction process to insure that artifact is completed with the minimum quality required to deliver the expectations defined in the BVA. Pegasystems process has a commitment to Quality Assurance (QA). The methodology initiates QA artifacts early in the initial stages and continually leverages those QA artifacts to insure that construction efforts will produce high quality initial releases. The process assumes a unified project team focused on success. The resource model is flexible and can accommodate any resource strategy made up of client, third party (on shore and off shore), and/or Pegasystems resources. This approach to staffing requires a strict adherence to Project Governance procedures and artifacts to ensure the project meets contracted expectations. The adherence to the Governance model minimizes change control due to project scope creep and project delays due to untimely responses to required information to keep plan on task and schedule. It leverages Critical Path Method (CPM) Scheduling in the design of project plans. That allows the project to leverage forward and backward scheduling to insure the project keeps focused on the true critical path and ensures maximum use of resource slack time to minimize change control items due to project discoveries. This methodology was designed to be flexible and is compatible with Functional Decomposition, Data Driven, Object Oriented, or Hybrid implementation methods that represent clients internal standards.

Methodology Phases, Goals, and Deliverables

Methodology Phases, Goals, and Deliverables

This section describes the: ! ! ! ! ! ! ! Methodology Phases Business Value Assessment Conception Phase Elaboration Phase Construction Phase including the Build Order Transition Phase Project Governance Setup

Methodology Phases

Business Value Assessment (BVA)

! ! ! ! Defines the success factors and expected Return on Investment (ROI) Quantifies the Business Value a customer can gain from a PegaRULES Process Commander solution Develops a framework from which the project(s) can be prioritized Provides a business case that will serve as the foundation for justifying current and future projects

Summary of Pegasystems Implementation Methodology

Conception Phase
Goal Establish a sound understanding of the scope of what is to be delivered. Deliverables: ! ! ! As-Is Business model Business model that represents current process flows and systems interfaces. To-Be Business model Business model that represents Future process flows and systems interfaces required to achieve the business benefit. As-Is Architecture model Technical model that represents current hardware, systems software, application software, and network configurations required to support the scope of the project. To-Be Architecture model Technical model that represents future hardware, systems software, application software, and network configurations required to support the scope of the project. Reporting Requirements Identify reporting requirements for Pega out-of-the-box reports, emulation of existing reports, and the need to develop new reports required to support the business benefit objective. Use Case Model Convert the business view of the To-Be solution into Rational Unified Process (RUP) Format to serve as the foundation for the project scope and sizing process. This model consists of high level Use Case Packages and high level Use Cases. Project Plan Budgetary high level estimate for the entire project and a proposal and firm estimate for the Elaboration Phase.

Phase Roles and Responsibilities:

Deliverable As-Is Business Model To-Be Business Model As-Is Architecture Model To-Be Architecture Model Reporting Use Case Model Project Plan Owner Business Architect Business Architect System Architect System Architect Business Architect Business Architect Project Manager

Methodology Phases, Goals, and Deliverables

Elaboration Phase
Goal Establish the foundation requirements and design definitions that serve as the baseline design for the common components of the solution. Deliverables ! ! Environment Setup Set up the PegaRULES Process Commander environment and establish the class reuse design. Use Case Package Define the detail Use Cases within a Use Case Package that reflects the pre and post conditions of the business process. Identify the Use Case primary and secondary process flows and associated data and interface requirements. Test Strategy and Test Plans Define the project test strategy and test plans required to ensure that the project will move into production. Identify the actual business scenarios and test data to be leveraged for developing test scripts for QA testing.

Phase Roles and Responsibilities:

Deliverable Environment Setup Use Case Package Test Strategy and Testing Plans

Owner System Architect Business Architect Testing Team assisted by Business Architect

Summary of Pegasystems Implementation Methodology

Construction Phase
Goal Deliver the PegaRULES Process Commander solution in three iterations. ! The first iteration is delivered to the user community so they can validate that the end to end process represents the solution that ensures the business benefit is achieved. The second iteration to the user community ensures that the screen views and flows support the ability to achieve the business benefit. The third iteration delivers a solution that completes all requirements defined as necessary to achieve the business benefit. Development Test Cases are created during this phase. These high level test cases are used to illustrate the basic flows of the application, demonstrate that the application is delivering on the requirements and expected benefits outlined in the projects BVA and ROI, obtain incremental buy-in from the users, and eliminate the introduction of cascading errors during construction. These are NOT the same as functional QA test cases developed by the business users to test the applications full functionality prior to deployment.

! ! !

Deliverable A functioning system.

Phase Roles and Responsibilities

Deliverable First Iteration Second Iteration Third Iteration Owner Project Team Project Team Project Team

Methodology Phases, Goals, and Deliverables

Build Order
The recommended order of construction for each iteration is shown below:

Recommended Build Order Iteration 1

Recommended Build Order Iteration 2

10

Summary of Pegasystems Implementation Methodology

Recommended Build Order Iteration 3

Methodology Phases, Goals, and Deliverables

11

Transition Phase
Goals Establish a production environment that is maintainable by IT and useable by the Business community. Deliverables: ! ! ! ! Environment migration process based upon clients standard operating procedures. Quality Assurance testing process based upon clients standard operating procedures. Production acceptance process based upon clients standard operating procedures. End user rollout and support process based upon clients standard operating procedures.

Deliverable Environment Migration Process QA Testing Process Production Acceptance Process End User Support and Roll Out

Owner System Architect Testing Team Business Owners Project Team

Project Governance Set Up

Goal Establish effective project governance to ensure that the business benefit is delivered and the project scope, time, and budget is controlled. Deliverables: ! ! ! Set up an executive project steering committee. Establish the Project dash board. Establish the Project escalation process. Change control Issues