In Traditional development methodology a project team creates multiple documents to meet specific project deliverable. Starting from the Project Charter to Project plan to Project closure many documents are created and updated by the project team.
If we talk about the Requirement Phase, many versions of requirement documents are created by the project manager or business analyst such BRD (Business Requirement document), SRS (System Requirement Specification), and FRD (Functional requirement document).
During Design phase many form of design documents such as System Design Document (SDD), Architecture design document (ADD), Functional Design Document etc. are created and maintain by the project team.
- What is BPM?
In PEGA the story is different. PEGA uses one single module to capture project or business objective, project requirements and use cases. This module is called DCO (Direct Capture of Objectives)
In DCO module there are three tools that are primarily used.
- Application Profiler
- Application Accelerator
- Application Documentation
Application Profiler: This tool is used to capture business objective and business requirement. The business analyst uses this tool to write down the business objectives, business requirement and use cases. In the Application Profiler following items are defined.
- Discovery Map
- External System which will interact with the application
- What kind of correspondence (email, text, SMS, letters etc) our application will generate
- All Project assumptions
- No of users and their role.
Application Accelerator: This is the tool which uses the information defined in the Application Profiler to setup foundation for the applications. Here we define the Classes and Rulesets that will be used in our Application. Typically, a Senior System Architect works with the Application Accelerator.
Application Documentation: This tool uses Application Document Wizard to generate customized documentation about the application.
