Conventional techniques like observation and interviews typically take significant time to organize. Joint Requirements Planning techniques on the other hand, have the added advantage of saving time because they involve bringing system owners, analysts, users, designers and builders together to identify problems, define requirements and analyse within a Joint Application Development framework. These workshops can run for 3-5 days with the analyst playing the role of a facilitator.Read More
A use case can be defined as an activity performed by the system in response to an event. How can the analyst ensure that all the use cases (system functionalities) are captured? An interesting approach by Alistair Cockburn suggests that analysts identify use cases with the “coffee-break test”. That is, once the user has completed a use case, s/he can take a coffee-break without feeling guilty... Beyond the coffee-break test, there are 3 recommended techniques for identifying use cases. They are discussed below:
*Includes Free Template*
A use case diagram provides a high-level description of what your system should be able to do and who/what will interact with it. It’s a technique for specifying functional requirements.
*Includes Free Template*Read More