Pega 7.2: business objectives, requirements and specifications

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 […]

Business Process Model versus Pega Case Life Cycle Model

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 […]

Complexity versus Difficulty

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, […]

Data modelling as a BA technique is in decline

In my experience, very few business analysts produce models of the things a business cares about.

Of course my experience is that of one person across the whole IT industry, so my view is a thin slice through a very big cake. What’s more, my experience is limited to process-driven projects. […]

KYC is primarily about decision making

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 […]

Logical ERD for Pega’s Financial Services Industry Foundation 7.21

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.

[…]

Things aren’t the same just because you treat them the same

Several years ago a major software consultancy built a Pega solution for a client and within two years of deploying it, the client was having to rebuild it themselves. It’s not an uncommon scenario.

The client brought me in, because of my background as a Pega Business Architect, to take […]

Pegasystem’s BA Certification

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 […]

Pega 7 DCO: a business analyst’s perspective

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 […]

Use Cases in PRPC – Part 4

Continuing on from Use Cases in PRPC – Part 3, the following tables will give Pega Business Architects an idea of how to use PRPC’s “Use Case Rule” to capture details about your Atomic Use Case.

[…]