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.
[…]
|
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. […] Continuing on from Use Cases in PRPC – Part 2, the following tables will give Pega Business Architects an idea of how to use PRPC’s “Use Case Rule” to capture details about your Software Use Case. […] In Part 1, we took a look at Pega’s definition of a Use Case and what the Application Profile Wizard allows Pega Business Architects to capture. In Part 2, we shall now take a look at four different types of Use Case and how they relate to PRPC. Business Use Case […] Use Cases are a key concept Pega Business Architects should understand if they are planning to use PRPC’s Application Profile Wizard. If you are familiar with UML, Pega’s notion of a Use Case might confuse you at first. It is important to distinguish between a “Use Case Rule” (which is a […] As a result of some recent conversations with colleagues who are learning to use activity diagrams to model use cases, I have updated my slideshow on the topic. If the front slide below does not say “Part 1: The Basics”, then please click through to SlideShare to see the updated version. […] Activity diagram tutorial part 2 View more presentations from Declan Chellar Related posts: Using activity diagrams to model use cases […] In Lean Use Cases: Part 2, I promised I would talk about documenting business rules and data items relevant to a use case. Here I am, fulfilling that promise. Imagine a holiday company requires a system that allows it to, among other things, take bookings for holidays. I have modelled a […] As a follow-on from Lean Use Cases: Part 2, please click on the link below to see a short tutorial on modelling use cases as activity diagrams. It is best viewed in full-screen mode. Activity diagram tutorial View more presentations from Declan Chellar See Lean Use Cases: Part 4 for documenting business rules […] Recently I was asked to take a look at some Software Use Case (SUC) specifications. What I found was actually a description of a screen flow crowbarred into a SUC specification template. There are two questions you might be asking. What’s wrong with that? How does it come about? April 22nd, 2010 | Tags: analysis, requirements, techniques | Category: Use Cases | Leave a comment I have had discussions with colleagues about use cases (and seen discussions on LinkedIn) where it is clear that some people do not understand that there are different types of use case, so I hope the following definitions help. Business Use Case A technique for describing (in technology-agnostic terms) a repeatable […] |