This event is history, please check out the list of upcoming seminars
Why do we organize this seminar ?
|FREE BOOK with your seminar participation:|
The first session of this seminar (21 September 2006) was completely FULL. This second session on October 4th, 2006, is again completely FULL. Of course, we will organise this seminar again in January or February 2007, and you can ask us to be informed as one of the first to receive the announcement of that seminar.
Requirements are the most crucial part of systems development, and yet the most misunderstood part of it. Requirements must be correct if the rest of the development effort is to succeed. This seminar presents a complete process for eliciting the real requirements, testing them for correctness, and recording them clearly, comprehensibly and unambiguously.
Software development today is more complex and demanding than ever; and there are fewer resources to meet those demands. Getting the software right - the first time - is the most effective way to succeed under these circumstances. Today's requirements process is incremental with quick cycle times. It uses prototypes and scenarios, and it ensures that your developers know precisely what you - and your customer - mean when you write a fit criterion: a concise test case for the requirement.
This seminar shows you how to precisely define the scope of the business problem, to discover and involve the appropriate stakeholders, to use techniques such as apprenticing and use case workshops to learn what the users really need, to write testable requirements, and to phase the requirements to allow incremental delivery of the product.
Why should you attend this seminar ?
During this seminar, you will learn how to:
Who should attend this seminar ?
This seminar is particularly useful for anyone who is involved in delivering the right systems - the ones that get used.
This includes, but is not restricted to business analysts, systems analysts, project leaders or managers, requirements engineers, consultants or similar. It will also be useful for users or software customers who want to ensure the requirements process delivers what they need.