|
In Part 2, we compared how a Case life cycle might look in Pega’s Case Life Cycle Designer versus BPMN. Here, in Part 3, we’ll consider when you should and should not use Pega’s Case Life Cycle Design tool to model the business process. As we have seen, if you are […] In Part 1, we went through some of the key terms Pega terms in Case Life Cycle modelling. Here, in Part 2, we’ll compare modelling a Case life cycle using Pega 7’s modelling tool with BPMN 2.0. The life cycle view of a Case in Pega 7 is similar to the […] In this blog post I aim to provide an appraisal of the Pega Developer Network articles “What is the SmartBPM Methodology?” and “Using Pega BPM with PRPC“, based on my experiences working on Pega projects in the field. I am a Certified Pega Business Architect (7.2) and Pega Methodology Black Belt, […] If you are a Pega Business Architect, you will be familiar with Pega’s feature that lets you connect Business Objectives, Requirements and Specifications. This feature is excellent for traceability but it may surprise you to know that I don’t use it exactly the way Pega tells you to. Business […] Pega 7’s case life cycle modelling tools enable you to quickly model and demonstrate a high-level process design within Pega in front of your customer. The tools I’m talking about are the life cycle view of a case type and the flow view of a process within a case type. While […] On software development projects people have to estimate the effort involved. In doing so, one of the things analysts are asked to consider is the complexity of a process, but it surprises me how often analysts confuse complexity with difficulty. The two concepts are mutually exclusive. A process can be simple, […] Know Your Customer (KYC) is primarily about the decisions a financial institution needs to make about a (potential) customer. However, I have yet to find a definition online that focuses on decisions. Wikipedia’s definition focuses on the process1, while Investopedia2 and The Free Dictionary3 place emphasis on the form that has […] In principle, any physical model should have a corresponding logical model that represents a business’s own view of its needs in a technology-agnostic way. When it comes to data, that ideally consists of a business glossary and some sort of visual representation of the relationships between the business concepts defined in the glossary. […] I am recognised by Pegasystems as a Certified Business Architect. But what does that mean? As you may know, Pega has Direct Capture of Objectives (DCO), a useful set of tools which can be used by experienced requirements analysts during the Inception and Elaboration phases of a Pega development to directly […] Direct Capture of Objectives has a revamped the look and feel in Pega 7 but little has changed. What is the same? Business Objectives Actors Requirements What has changed? Work Types are now called Case Types but the underlying thing seems to be the same. Use Cases are now […] |