Defining requirements
To ensure that you stay on target for a successful deployment of Pega Foundation for financial Services, 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.
Pega Foundation for Financial Services
- 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.
For information on defining requirements for an implementation, see Application specifications and requirements.
- Step 1: Defining the case type modifications and attributes
- Step 2: Defining the data model
- Step 3: Defining your access groups
- Step 4: Mapping the application data
- Step 5: Defining common codes management requirements
- Step 6: Defining integration
- Step 7: Defining the security model and organization structure
- Step 8: Customizing the user experience
Previous topic Delivery stage Next topic Step 1: Defining the case type modifications and attributes