Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

DDCO

Direct Capture of Objectives
by

m00123x r00x

on 7 December 2011

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of DDCO

DCO
Direct Capture of Objectives
Application Profiler
Application Accelerator
Document Wizard
DCO Enablement Wizard
Components of DCO
What is DCO ?
Direct Capture Of Objectives is a set of Application rules and wizards designed to capture and tie the business objectives, project goals, requirements and use cases to actual implementation
Since this is a suite so what are it's
components ?
DCO has 4 main components
Application Profiler
Application Accelerator
Document Wizard
DCO enablement Wizard
Let's Explore them in Detail
Now that we know how to use the tools -
When do we use these them ?
So let's sum up the advantages of the tools ..
The application Profiler
The application accelerator
The Document wizard
Auto-generates a comprehensive requirements artifact, which can act as the basis for subsequent PRPC development
Builds up a repository of use cases so that they can be used in future projects
Integrates with Application Profiler
Provides framework for subsequent application development
Incorporates Pega Best Practices for Application Design
Documents all aspects of the application
Supports the use of custom templates
Saves preferences on previous runs
The DCO Enablement Wizard
Ports existing applications making them DCO compatible
Looking back -- When it all started
DCO was introduced in version 5.4 of pega and has evolved since then

The DCO release versions are:

DCO 3.2 — released November 2009
DCO 3.1 — packaged and released with Process Commander V5.5 and V5.5 SP1
DCO SP2 — released September 2008
Why Use DCO ?
Pega as a BPM tool aims at optimizing the business process

DCO follows the same philosophy and aims at optimizing the development process

Traditional development methods involve several tools all of them outside Pega for Capturing Requirements and converting them rules in Pega this leads to traceability issues which can be minimized by using DCO
Documenting applications take up a chunk of user development time which can also be reduced by using DCO
So what is Application Profiler?
Application profiler is basically a wizard which provides a guided process for users to collect information at the beginning of a project.

So in simple terms what is does is it assists the user in the creation of the Business Requirement Document (BRD) at the initial phase of the project
Information collected by Application Profiler Wizard
Output of the Application Profiler
App Profile Wizard
So what information is collected by the
Application Profiler ?
The profiler collects the following information from the user regarding the project
Overview
Actors
Interfaces
Reporting
Correspondence
Assumptions
and Project Resources
So what is Application Accelerator
Builds the framework of the application based upon the information provided in the Application Profiler

Application accelerator can help in the initial application design and provides a framework for subsequent application development

Builds framework classes, report templates, screen wire fames and flows in draft mode



So what the application profiler actually does is that it takes the use cases which were defined in the profiler and based on that as well as developer inputs it actually generates some rules which can act as the foundation for building the application .
So what rules does the profiler generate ?
Application Rules
Rulesets
Org-Division Rules
Classes
Use Cases
Requirements
Work Parties
Access Groups


Models
User Interfaces
Flows
Correspondence Templates
]
]
These rules are mainly related to
application foundation functions and may
be completely generated by the accelerator
provided the details are available
The accelerator generates these rules
but what it generates is basically just a container with no details
Input from App Profiler
Inputs from the Developer
Rules Generated by Accelerator
A quick Recap of the steps in the Demo
Graphical Overview of App Profiler
Time for a DEMO
Get Started - Describe the org and project name and lists users who can access and change the profile
Overview - Define the type of application you are building and lists the business objectives
Actors - List the actors who perform work in the application
Requirements – Describe the business and operational processing requirements for the application
Work Types - List the types of work processed in the application and associates them with use cases
Interfaces - Describe the connectivity to external systems
Reporting - Describe the reporting requirements
Correspondence - Describe the correspondence requirements
Assumptions - List the working assumptions for the project
Participants - List the number and type of resources needed to complete the project
Sizing - Create and attaches a sizing estimate; displays a graphical timeline for the project
Document - Create and attaches the profile; displays a visual breakdown of application elements
App Accelerator
Time again for a Demo
Summary of the steps in the demo
* Application Background - identifies the profile used to create the application, the type of application, and the business objectives
* Base and RuleSets - specifies and displays the class and organizational structure of the application
* Actors - lists the actors who perform work in the application
* Roles - defines how actors participate in processing work in the application
* Work Types - describes the types of work processed by the application and associates them with use cases
* Class Structure - specifies how the work types fit into the class structure of the application
* Flows - defines flow names for work types and associates them with use cases
* Requirements - lists the business and operational processing requirements
* Reporting - lists the standard and custom reports
* Correspondence - lists the correspondence
* Other Extensions - lists rules that have been flagged for extension; this step appears when creating a new application based on a framework
* Review Application - allows you to review the rules and class structure prior to creating the application
The formal definition of the
Doc Wizard
What are the details needed before starting the Doc Wizard
A graphical Overview of the Process
The Application Document wizard allows you to specify reusable document settings and application data content to create professional looking documentation of application assets throughout a project lifecycle or in support of your day to day maintenance updates.
In simple terms ..
This wizard allows the developer to define a template feed some details* may be at the start of the development life cycle . And then this wizard can be used throughout the dev life cycle to generate up-to-date Application Document (LLD)
Note* -- the details which are needed by the wizard to begin with are outlined in the next slide
First - Obviously the name of the application you want to document
Next the rulesets in the application which you want to document
The work types in the application which will be documented
The Level of detail you want in the document
The flows in the application which has to be documented
Finally the screens for which you want screenshots to be attached to the Document
Application details Entered by User
The generated Document
The Third and Final DEMO
A quick Recap of the DEMO
* Select Application - selects the application you want to document, the template, and whether you want to use a set of previously saved settings
* Select RuleSets - selects the RuleSets
* Select Work Types - selects the work types and use case categories of the individual work types
* Select Criteria - selects the general level of document detail, the chapters and tables, and the rule detail
* to include for the work types Order Flows - sets the display order of flows
* Define Diagrams - sets the criteria for including entity relationship diagrams (ERD); then, creates and displays the diagrams for review and edit
* Define Screenshot Data - sets up work object data for models that are applied to screen shots of flow components
* Capture Screens - captures screen shots of harnesses, flow actions and correspondence based on a selected display style
* Create Document - creates the document in Microsoft Word based on the settings selected; allows you to edit and save the document
The final component is the Enablement Wizard
Another wizard which allows the user to add or update requirements, use cases, actors and work types to an existing application that is either partially DCO enabled or not at all.


The wizard simply guides the developer through a series of input steps that gathers information about the following elements of the application:

* Requirements
* Actors
* Work Types
* Use Cases

and allows the user to leverage the other Direct Capture capabilities - Document Wizard, Application Profiler, and Application Accelerator - as he plans and builds out new functionality and extensions.
To get to know when to use the tools let us explore the SDC of any project
Full transcript