Studio interoperability

App Studio provides a more simplified, collaborative, and inclusive authoring experience which allows a wide range of low-code practitioners to understand, interpret, and author processes and applications. It hides complexity and increases the Case Type literacy of many stakeholders, which helps to better express requirements, feedback, and needs.

Dev Studio provides more robust low-code development features for more experienced Pega architects to configure integrations, complex decisions, security, and advanced features. Think of Dev Studio as a curated authoring environment to create reusable modules and to mark Rules as relevant Records to make them accessible for assembly in the App Studio Case Designer.

Using Dev Studio in conjunction with App Studio can maximize and extend the power of Pega Platform for all low-code project team members so that everyone can work more effectively and collaboratively in App Studio.

In the following image, click the + icons to learn more about the interoperability of App Studio and Dev Studio:

In the Prepare phase, business and IT teams collaborate on the enterprise solution design and create a refined and prioritized backlog for the low-code build teams. Focus is on the following areas to maximize enterprise reuse and ensure teams downstream have a solid foundation:

• Reuseable Components
• Feature Map
• Interfaces
• Guidelines
• Enterprise Class Design

In the Build phase, activities focus on the following areas:

• Detail features
• Integration
• Reports
• Channels
• Configuration
• Testing
   

Low-code teams can fall on different points of the low-code development continuum: Citizen development, Fusion team development, and IT-led development.

Citizen development

The outcome of citizen development is a low-risk departmental application that makers and citizen development squads build. The Community of Practice establishes governance with automated guardrail compliance through Pega App Factory. Most of the build work occurs in App Studio. IT might also build reusable enterprise assets, which the Community of Practice orchestrates.

Fusion team development

Fusion team development involves a distributed application development capacity within and as a service to the business unit by using citizen development squads in collaboration with IT. Fusion teams collaborate on the build in App Studio and Dev Studio in an interoperable fashion. The Fusion team members might work on shared functionality or discreet functionality as solution requirements dictate. In a Fusion team development model, you can expect about 60 percent of the build work to occur in Dev Studio and 40 percent of the build work to occur in App Studio.

Over time, your Fusion teams perform a greater percentage of build work in App Studio as a result of the availability of reusable application features built in previous iterations. Fusion teams should have a target of completing approximately 60-80 percent of their build work in App Studio, with the remainder 20-40 percent of the build work completed in Dev Studio.

IT-led development

The IT team, guided by the business, built applications that require traditional Software Delivery Life Cycles because of business criticality or complexity. IT teams, or a COE team, also build and deliver reusable features to be used by the Citizen Development squads. IT, or a COE team, typically builds 80 percent of the reusable features in Dev Studio, and 20 percent of the build work can take place in App Studio.