Links may not function; however, this content may be relevant to outdated versions of the product.
DCO 6.1 - About the Direct Capture of Objectives
Direct Capture of Objectives (DCO) is a suite of features that enable project team members to directly capture, organize and manage business specifications inside of Process Commander and associate them with the specific parts of the application that are implementing them.
Designed as an enabling technology suite, it can be used collaboratively and productively by project teams that include members of the business analyst, user, developer, quality assurance and IT communities of your organization. By removing redundancies and disconnects, it helps close gaps in the development process; and fosters a Build for Change mindset that encourages reuse of application assets, automates common project activities, and generates on-demand, up to date, accurate project documents.
DCO is not a methodology in and of itself. It is an agile process that is adaptable to any size project and can be used in conjunction with any implementation methodology. When applied consistently, DCO saves you time, effort, and budget dollars while improving and maintaining project and application quality.
The end result and benefit of using DCO is a clear 360 degree view of your Process Commander application through a project life-cycle.
Direct Capture tools include:
- Application Profiler — captures objectives, use cases, requirements, processes, interfaces, reports, correspondence, and case type relationships; estimates project sizings; documents the collected information as an application profile document; jump starts application development by providing the information as input to the Application Accelerator.
- Application Accelerator — jump starts the creation and extension of your application and automates best practices for application design; consuming information from an application profile, it creates organization and class structures, case type relationships, and draft processes and user interface elements so you can see the working application based on the captured information.
- Application Document wizard — supports rapid and iterative documentation of the application as development progresses using your predefined templates and content settings.
- Application Use Case — allows business users to describe at an atomic, granular level the steps required to build an application in business language; stored as business rules and linked to processes and other application components to provide development and testing detail and traceability as development progresses.
- Application Requirement — allows business users to describe capabilities that the application must fulfill and define success criteria; stored as business rules and linked to other rules to provide development and testing detail and traceability.
Note: Releases prior to Version 6.2 include the DCO Application Enablement wizard which creates DCO assets for existing applications that are not yet, or only partially, DCO-enabled. Starting in Version 6.2, the Discover Work Types feature of the Application rule is used.
The following table lists articles about DCO features and functionality published for:
- Process Commander Versions 6.2 and 6.1
- DCO Versions 3.1 and 3.2, available for Process Commander Versions 5.4 SP2, 5.4 SP3 and 5.5 SP1
Select a version number in the table to display the article based on the capabilities available in that release.
|Topic||Process Commander Release||DCO Release|
|About this release||6.2||6.1||3.2||3.1|
|Upgrading from Older DCO Versions||6.2||6.1||–||–|
|Enabling DCO Access||6.2||6.1||3.2||3.1|
|Creating Application Profiles and Discovery Maps||6.2||–||–||–|
|Creating an Application Profile||–||6.1||3.2||3.1|
|Creating Discovery Maps||–||6.1||–||–|
|Sharing and Merging Application Profiles||6.2||6.1||–||–|
|Using the Application Accelerator||6.2||6.1||3.2||3.1|
|Using the DCO Enablement Wizard||6.2||6.1||3.2||–|
|Using the Application Document Wizard||6.2||6.1||3.2||3.1|
|How to customize Application Document templates||–||6.1||–||–|
|Extending the Document wizard||–||6.1||3.2||3.1|
|Working with Application Use Cases and Requirements||6.2||–||–||–|
|Working with Application Use Cases||–||6.1||3.2||3.1|
|Working with Application Requirements||–||6.1||3.2||3.1|
- Prior to PRPC 6.1, DCO was made available as a separate release, with its own version numbers.
- Generally speaking, the availability of an article for a particular release directly corresponds to whether a feature or capability is present in that release. For example, the Application Document wizard in Version 6.2 allows you to substitute custom images and include custom content using features in the wizard itself. As a result, the "Using the Application Document Wizard" article for PRPC 6.2 includes that information.
- For recent releases, some information originally in multiple articles is consolidated into one article (for example, the information about use cases and requirements for Version 6.2).
Previous topic Adding a work type to a framework and its implementation layer Next topic DCO 6.1 - What's New