This event is history, please check out the List of Upcoming Seminars, or send us an email

Check out our related in-house workshops:

 Learning Objectives

Why do we organize this 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, personas 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:

• Determine your client's needs - exactly
• Write requirements that are complete, traceable, and testable
• Precisely define the scope of the project
• Discover the stakeholders and keep them involved
• Use up-to-date techniques such as storyboarding and e-collaboration
• Get the requirements quickly, and incrementally

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.

 Full Programme

Because of the increasing organizational and technological complexity, we need clearer, more understandable, and less ambiguous requirements. But how do we find these requirements and how do we communicate and manage them ? This presentation addresses these questions by looking at:

• What are requirements?
• The requirements knowledge model
• The requirements process
• Stakeholders, Goals and Scope
• Trawling techniques
• Product Use-cases
• Prototyping
• Quality Gateway

Best practices in

• organising,
• structuring and
• performing

an interview about requirements.

The user-centered design (UCD) methodology for software development incorporates very interesting techniques to enhance the quality of requirements gathering and requirements management. But what is this UCD methodology and how can it deliver added value to the requirements management process ?

• What is the user-centered design methodology ?
• How can UCD help you during the requirements management process ?
• User, Task and Environment Analysis: Hands-on techniques to get to know your users, the tasks they perform and the environment in which they work and live.
• Some case studies to illustrate this methodology

This customer testimonial will explain how requirements management is performed in a practical case study:

• The specific challenges of De Lijn, the Flemish public transport company
• Techniques used for finding and collecting requirements
• Lessons learned: what works and what doesn't ?

This customer testimonial will explain how requirements management is performed at SD Worx:

• The specific challenges of SD Worx
• Techniques used for finding and collecting requirements
• Lessons learned: what works and what doesn't ?
• Introducing and using the Volere requirements method
• Benefits for SD Worx from doing requirements management in a structured way

This customer testimonial will explain how requirements management is performed at UZ Leuven, the Leuven University Hospital:

• UZ Leuven's mix of techniques to gather requirements and to document and steer projects
• how to reconcile changing and hard-to-get requirements in an agile development environment

 Speakers

Questions about this ? Interested but you can't attend ? Send us an email !