How to extract requirements, test them for correctness, and record them
4 October 2006 (14-21)
Location: Sofitel Diegem
(Diegem near Brussels (Belgium))
Presented in English
Price: 540 EUR
(excl. 21% VAT)
This event is history,
please check out the List of Upcoming Seminars, or send us an email
Check out these related open workshops:
Check out our related in-house workshops:
Why do we organize this seminar ?
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:
- 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.
13.30h - 14.00h
Registration, coffee/tea and croissants
Keynote Presentation: Mastering the Requirements Process
(Suzanne Robertson, Atlantic Systems Guild)
Increases in organizational and technological complexity have raised awareness of the need for clear, understandable, unambiguous 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
- Quality Gateway
Coffee/Tea and Refreshments
Interviewing Techniques for Requirements Gathering
(Suzanne Robertson, Atlantic Systems Guild)
Best practices in
- structuring and
an interview about requirements.
Requirements Typology, illustrated by a case study
(Eric Callebaut, Method Consulting)
The main intent of this presentation is to outline a typology/classification of requirements with different capturing techniques, and to illustrate this by a case study. The case study is taken from a major offshore development project with an Indian company, because 'requirements management' is even more critical in an offshoring context.
- Requirements Levels
- Overview of requirements stakeholders and deliverables (e.g. business case, product vision, requirements specs, functional specs, test specs,...)
- Requirements Types
- Project requirements/constraints: overview
- Functional requirements: overview, methods for capturing and structuring (e.g. use case modeling), examples
- Non-functional requirements: overview, documentation templates (e.g. Volere) , examples
- Case study
- Requirements web from offshore development project with India (Patni Computer Systems)
Case Study: Requirements Management at Vanderlande Industries
(Noud van Mullekom, Engineering Manager Major Projects, Vanderlande Industries)
During this customer testimonial, we will learn how requirements management is performed in a real-life situation.
How tools can support the requirements management process
(Vicky Bunyard, Telelogic)
To illustrate how tools can support the requirements gathering and management process, we have selected a speaker from one of the leading tools for requirements management, who will give a non-commercial overview of how tools like this can help and support you:
- Structuring a requirements document
- Managing attributes
- Managing Change
- Protecting data, managing security
Final Q & A, Conclusions and Summary
End of this seminar
Suzanne Robertson is a principal and founder of the Atlantic Systems
Guild. Suzanne is co-author of "Mastering the Requirements Process"
(Addison-Wesley Edition 3, 2012), a guide for practitioners on finding requirements and writing them so that all stakeholders can understand them. Her other requirements book, "Requirements-Led Project Management" (Addison-Wesley 2005) addresses how to use requirements as input to planning and management. Current work includes research and consulting on the management,
sociological and innovative aspects of requirements. The product of this
research is Volere, a requirements process, template and techniques for
assessing requirements quality, and for specifying requirements.
Suzanne works with organisations to apply innovative techniques and
fresh thinking in all of their systems development activities. She is
author of many papers on systems engineering. Some of these papers
are on her web site www.systemsguild.com and www.volere.co.uk. She
also speaks at numerous conferences and universities. She is a member
of IEEE and BCS and on the board of the British Computer Society's
Requirements Groups. She was the founding editor of the Requirements
Column in IEEE Software. Other interests include a passion for the
opera, cooking, skiing and finding out about curious things.
James and Suzanne Robertson are principals and co-founders of The Atlantic Systems Guild.
Eric Callebaut is independent IT consultant and member of Inno.com.
For more than 15 years now, Eric has been helping organizations to improve their software project management and software development processes in order to build software faster, cheaper and better.
Eric contributed as process coach and trainer to various international corporations and leading-edge projects. Clients include: ING, Toyota Europe, De Post, IBM US, BP UK, Patni (India), Euroclear, IBS, British Steel.
His experience is focused on management and IT-consulting with special emphasis on IT organisation & processes, IT offshore development, requirements management- and project estimation methodologies.
Eric holds a master degree in economic science and computer science from the Catholic University of Leuven and has also studied International Management at the Boston University.
Questions about this ? Interested but you can't attend ? Send us an email !