|
Many requirements analysis specialists have little or no development or testing experience and this can lead them to forget what the real deliverable is. The purpose of requirements analysis is to provide a robust and unambiguous requirement so that architects and developers know what to build and testers know what to […] 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 […] I am fond of System Use Cases as a tool for documenting functional requirements, but I am not a big fan of use case specifications. I find the textual specifications result in the kind of weighty documents that everyone hates reviewing and I continue to be amazed that so many analysts […] 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 […] I have found that people, from business SMEs to software developers, often confuse triggers and pre-conditions. Whether you are producing a business activity model, a process model (business use case) or a software use case, both concepts are relevant and the distinction is important. It is also important to be able […] A visitor to my blog commented on the post “No favourites” saying that her solution to the problem of being asked multiple security questions (none of which might apply) is to use a single word as the answer to all such questions. So no matter whether they ask what your favourite […] |