|
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, […] I’m bumping this post because of some updates, as highlighted in green below. Note that this post relates to Pega 6.1 and was originally drafted in 2009. Some of you Pega Business Architects were wondering how the modelling techniques I use relate to Pegasystems’ Direct Capture of Objectives approach, so […] As an analyst, it’s not enough to know what your customer wants. It is essential to unearth what the customer needs and how the customer’s business will benefit by fulfilling that need. Customers are often the last to understand what their business truly needs, even when they have a clear idea […] 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 […] Just as functional requirements are traced from business need to implementation, data requirements should be traced to eliminate redundancy and ensure coverage. The following slideshow lays out my procedure for tracing data requirements. Tracing Data Requirements View more presentations from Declan Chellar Related posts: The Importance of Data […] Whenever I mention data modelling on a project, everyone seems to assume I am talking about database design. In my experience, on the vast majority of projects, both the Business and the service provider leave data modelling until they are at the screen design stage. At best, they might start modelling […] Junior requirements analysts sometimes have difficulty with how to document business rules for information systems, or indeed, with recognising them in the first place. I hope this short article helps. Some Definitions “A rule under which an organization operates. A policy or decision that influences a process step.” (Data […] It continues to amaze me how many projects proceed against a poorly-written scope document or no scope document at all. It also makes me wonder on what basis tenders are made. If I am ever asked to provide input input work estimation, I insist on seeing a baselined statement of scope […] |