Before attempting to model a business process, you should first define its scope so you know how it starts, how it ends and whether it is really one process or many.
Before attempting to model a business process, you should first define its scope so you know how it starts, how it ends and whether it is really one process or many. There’s a film from 1985 called The Journey of Natty Gann. “In the 1930s, a tomboyish girl runs away from her guardian to join her single father who is 2,000 miles away, because there was work there.” Judging by the title, I think it’s reasonable to expect Natty Gann to be the protagonist and for […] There is a perception that Pegasystems PRPC can be used to create BPMN-compliant process models. However, I consider this perception to be incorrect. This slide show takes you through my reasoning, but I can sum up my conclusion with a golf analogy: No matter how good your 3-iron is, you can’t turn it into an […] Many analysts have a grounding in grounding in one main area of business analysis, such as process modelling. However, a company’s business architecture cannot stand on a single leg. In fact, three legs are required: Process model Data model Decision model I have seen many software development projects where […] I was taken aback recently when someone told me they didn’t understand the concept of re-use. You see, when I started out in software development, I was taught this concept, so I cannot imagine a world without it. Of course, I am not insensitive to other people’s situations, so I understand […] Case Types are a key element in Pega BPM development and it is important for Pega Business Architects to have an understanding of them. Case Type is what Pega used to call a Work Type prior to Pega 7. Although the Type is a Pega implementation device, the concept also has […] Since my blog post on Pegasystems DCO, several people have asked me to expand upon what I said about Discovery Maps. The expansion is in the slide deck below. In summary, although Pega Discovery Maps are intended as a mechanism for Pega Business Architects to model business processes in business terms, […] Activity Diagram tutorial part 3 View more PowerPoint from Declan Chellar Related posts: System Use Case or Screen Flow? Using activity diagrams to model use cases What NOT to put in your Activity Diagram […] Here is a re-cap of my approach to modelling a To Be process: Part 1: we modelled the As Is change control process in order to understand the current business model. Part 2: we reminded ourselves to be sensitive to the fact that the customer owns the process.
In Part 4 we drew both high level and low level versions of the To Be model of our customer’s change control process, based on the information we noted in Part 3. We are now ready to drive out and document high level system requirements (HLSRs). It is […] |