Skip to main content

Defining requirements

Suggest edit Updated on May 4, 2021

To ensure that you stay on target for a successful deployment, use a structured approach for your implementation methodology. You will need to prepare for your implementation and determine key aspects of the design that will affect the behavior of your application. Defining requirements for an implementation includes these tasks:

  • Reviewing extension requirements
  • Refining customizations and determining the availability of required data and integrations
  • Prioritizing, for example, revising the solution backlog, re-estimating effort for extensions and customizations, and confirming the project scope

Defining your requirements also involves DCO sessions and incorporating those requirements into the application design. During these sessions, you review each of the case types and process flows that the application already provides.

Update the Application Specifications with planned changes as described in the Pega Platform help topic Application Specifications.

Follow these steps to define requirements:

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us