Programma 'Mastering the Requirements Process I'
 

Het programma start om 09.30 uur en duurt tot 17.00 uur. Registratie is mogelijk vanaf 08.30 uur.

Ontvangst, registratie en uitreiking documentatie

1. Project Blastoff
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.

2. 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, and other techniques to discover exactly what the customers need—and want.

3. Functional Requirements
Functional requirements are those things the product must do. You discover them by understanding the real work of the organisation, and determining what part of that work the automated product can best do. The work and its interaction with the product are usually modeled with scenarios, and from these, you can readily derive the functional requirements.

4. Non-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.

5. 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.

6. The Quality Gateway
Testing is most effective when it is done early in the development cycle. Here we demonstrate how to test requirements before they become part of the requirements specification. The Quality Gateway rejects out-of-scope, gold-plated, non-viable, incorrect and incomplete requirements. We show how you can attach an unambiguous fit criterion to a requirement. This makes the requirement testable, as well as ensuring the implemented solution precisely matches the customer’s expectations.

7. Prototyping and Scenarios
Some requirements are not discovered until the user has the opportunity to use the product. Prototyping is a way of discovering requirements by testing mock-up products for the user’s work. Here we look at the merits of both low and high-fidelity prototypes, and how they and scenarios are used to discover previously-hidden requirements.

8. Your Requirements Process
We look at how to make your own requirements process as effective and efficient as possible. For example, accelerating the requirements gathering by establishing the scope then building an early throwaway prototype before moving on to incremental delivery. Each part of the requirements process is examined so that participants can discuss problems and ideas related to their own situation, and how they can use the lessons from this course to improve their existing requirements process.