Brief Introduction to Direct Capture Of Objectives

Direct Capture Of Objectives can be defined as “a set of Application rules and wizards intended to capture and bind the business objectives, project goals, requirements and use cases to real implementation. Pega sees DCO to be a method of sustaining  requirement, detectable and reduce costs due to rework and fixing bugs produced during the course of fixing a few bugs. It make sure accountability because it can verify if all the requirements/use cases has been met/addressed.

Important  Components of DCO:

(1) Application Profile : Application profile is an Auto-Generated word document developed to help the information congregation phase of the a project life’s cycle. The document is created as division of an automated tool called the Application Profile Wizard. The wizard directs  the user through each step on what data it would require for it to produce the AP document. The data that is input into this wizard lastly creates 3 components.

a) Application Profile document : This document make available a holistic vision of the application with all the business requirements, use cases and other details  of the application.

b) Project Sizing and Estimation Document : This document  is for sizing and estimation purpose.

c) Application Accelerator : This is the wizard that produces  all the rules that describes the application. Depending  on the input to the Application Profile, the accelerator generates all the rules starting from the Org Structure to rule sets to flow etc. Pega be adamant that the effort to fill these information into the application profile would take about ‘2-3’ days of devoted effort. The users can keep the information they confine during the middle of generating the application profile and before the creation of the application. The template for the document is saved as a Pega Accel-Task-ProposeApp. Application Profile. This rule file can be modified to the users standard and have them produce the information.

(2) Application Accelerator : The Application Accelerator is a wizard that mechanize the creation of applications or application frameworks or even expands existing framework

 (3) Application Document Wizard : This wizard generates a set of application precise documents to be used by the business and developers, all throughout the project life cycle. These documents are based on some predefined templates which can be modified for by the clients. To update they use the Pega Accel-Task-Document App. Project Document & Application Document. The wizard also can incarcerate screenshots of the presented application to be used as a indication in the profile document. This screen capture functionality is pretty useful during creating training manuals. The wizard also generates  ER Diagrams based on the classes/class structure within the application. The ERD are saved as a .vdx file.

(4) Requirement Document Rules : This are rules which are used by Pega to describe business requirements. They are division of the Rule-Application-Requirement Class. Requirements are given by the final users/owners of the application, but by meaning it can be defined as an inventory of events, conditions, or functions that require to be fulfilled and tracked in the project. The requirement rules are incarcerated as part of the application profile which is then passed onto the Application accelerator which generates the requirement rules. These rules are then customized and tracked all through the project life-cycle. DCO also offered for a Traceability Matrix that maintains track of changes to the business functionality and the rules that are impacted due to that modification

 (5) Use Case Requirement Rules :These are the rules  permits the business users upload their use cases into the application. The Use Case rule is an example of Rule-Application-UseCase which the uses inputs throughout the application profile data entry stage. Pega anticipates all the use cases to be atomic as that is what is tracked within the system. The application will be waiting for that the use cases should be detailed enough as it make simpler for the developer to code. The rules that reference Use Case Rules include#Application Rules#Flow Rules#Local and Flow Actions#New Harnesses via the starting shape of a flow#Activities.