Class 4: SDLC (Software Development Lifecycle) of PEGAPRPC

 

Q) Development Process in PEGA Tool & Other Languages?

As any software tool or languages that we have in the market Pega has the same lifecycle. Here we can see the lifecycle of PEGAPRPC

Traditional approach:-    

SDLC-Planningà Req gatheringà DesignàDevelopmentàtestingàDeployment-à Maintenance/Operations.

PegaPRPCSDLC:-    

Stage1:    Inception-  (BA-Business Analyst/PBA-Pega Business Architect) This Stage is generally executed by BA/PBA. At this stage, he will be interacting with the Client to gather the information of the business requirements and prepares a BRD (Business Requirements Document). He will also design the Agile methodology for the Project. He will share these documents to all other Managers.,

Stage 2:    Elaboration on Use Cases:-    Senior Technical Architects or (PCLSA) Pega Certified Lead System Architects will be involved in this phase. They will develop or give a demo on how the design approach will be. Here they will show some use cases. Usage of Case types or datatype will be done here using the Application or App Studio.

Estimation of Resources required, estimated time for delivery of application, splitting of project into multiple Sprints etc. will be done here.

Template or demo application will be shown to the Client or PO (Product Owner).

Note:- If the Organization is having the Pega Applications for the first time they need to take license from the Pega for the cloud application

Stage 3:    Development, Configure, Unit and Use Cases:-    Here comes the real picture where the PCLSA(Pega Certified Lead System Architect), PCSSA (Pega Certified Senior System Architect) & PCSA(Pega Certified System Architect) will be involved in the development of the project with some unit test cases for the code developed.

In PegaPRPC, here the development, configurations, packaging and deploying, testing etc., will be done by the developer itself. The deployment may be done to QA & UAT based on the code changes for the sprint they have worked.

Stage 4:    Transition System & User Accepting Testing (UAT):-    Users will be testing the code that has been developed by the developers and they see whether it fills their requirements.

Stage 5:    Deployment & live in Production:-    When the Code is successfully tested by the Users, upon confirmation from User the code will be moved to production.

Popular posts from this blog

Class 1: PegaPRPC

Class 2: Introduction to PEGA PRPC