|FREE BRANDNEW BOOK with your seminar participation:|
This programme is spread over 3 days, from 10h00 (but the workshop leader will already be present from 9h30 to answer your questions) till 18h00, with a dinner around 13h00:
This builds a foundation for the requirements project by establishing its Scope-Stakeholder-Goals. This gives you the precise scope of the business area to be studied; a testable goal for the project; and using stakeholder maps, you can identify all the sources of requirements. Additionally, the blastoff ensures the project is viable and worthwhile.
Trawling for Requirements
At the core of any requirements process is the ability to get people to tell you what they really need, rather than their perceived solution, or what they think you might be able to deliver. We show you how to use apprenticing, use case workshops, interviewing, brainstorming, mind maps and other techniques to discover exactly what the customers need - and want.
This section introduces the brown cow model that gives the business analyst different ways of thinking about the problem, and allows the real problem to emerge. We also look at innovation - fresh thinking about the problem - and how it is a necessary component of any requirements process.
Functional requirements are those things the product must do. You discover them by understanding the work the user does, and determining what part of that work the automated product can best do. The resulting interaction between user and product is usually modeled with scenarios, and from these, you can readily derive the functional requirements.
Non-functional requirements are properties the product must have, such as the desired look and feel, usability, performance, cultural aspects and so on. This section discusses the types of non-functional requirements, and shows you how to use the template, and other methods, to find the all-important qualitative requirements for your product.
Managing Your Requirements
Requirements are the lynchpin of any development effort, and so have to be written correctly and managed effectively. This section demonstrates the use of a template to help you write requirements. It looks at requirements management issues like traceability, prioritization and conflicting requirements. We also look at tools to help manage requirements specifications.
These related seminars and workshops may also be of interest to you: