|
Écrire des spécifications
complètes, sures et testables
- Mastering the Requirements Process
-
(Formation en anglais)
Durée : 3 jours
Lieu : En INTRA-Entreprises uniquement
Audience : Analystes métier, Analystes système,
Ingénieurs Produit, Responsables informatique, Responsables
qualité, Chefs de projet, Ingénieurs développement,
Ingénieurs de test, ...
Langue de présentation : ANGLAIS
Fournitures :
Supports de présentation et le livre 'Mastering the Requirements
Process' de Suzanne et James Robertson. voir aussi "Les plus..."
en fin de page.
Présentation
 |
Requirements are the most misunderstood part of
systems development, and yet the most crucial. Requirements
must be correct if the rest of the development effort is to
succeed. This workshop presents a complete process for eliciting
the real requirements, testing them for correctness, and recording
them clearly, comprehensibly and unambiguously. |
Objectifs
 |
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, |
 |
Get the requirements quickly, and incrementally, |
 |
Use up-to-date techniques such as storyboarding
and e-collaboration. |
Agenda
 |
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.
|
 |
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. |
 |
Functional Requirements |
| |
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 |
| |
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. |
 |
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. |
 |
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. |

 |
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.
|
Etudes de cas
We want you to use this right away. Each of the teaching chapters
is reinforced with a workshop where you apply the concepts presented
in the seminar. Participants work in teams to discover, specify
and evaluate requirements for a significant system by:
 |
Defining the project's scope, its goals and the
relevant stakeholders, |
 |
Identifying business use cases and product use
cases, |
 |
Prototyping the product to find hidden requirements, |
 |
Applying the requirements specification template, |
 |
Defining functional and non-functional requirements, |
 |
Deriving the fit criterion, or measurement, for
the requirements. |
Les "plus"...
 |
Your instructor has real-world experience, and
is able (and willing) to call on years of experience when discussing
your particular requirements issues, |
 |
Your own copy of the acclaimed Mastering
the Requirements Process, Second Edition by Suzanne and
James Robertson, published by Addison Wesley, |
 |
A copy of the Volere Requirements Specification
Template. This complete template provides the foundation for
your own requirements specifications, |
 |
A complete version of the Volere Requirements
Process. This guides you through the intricacies of requirements
gathering, |
 |
Guidance on tools currently available to assist
requirements capture and recording, |
 |
References to books and sources of up-to-date
requirements engineering techniques, |
 |
A final session where, through discussions, interaction
and demonstrations, you can ensure you have a requirements process
suitable for your organization. |
Tarifs
Pour la session, par participant : 2 450 € HT, déjeuner
de midi et pauses incluses.
Bon
de commande (pdf 70KB)
Informations diverses :
La formation se déroule de 9h30 à 12h30 et de 14h
à 17h30.
Le nombre de places est limité à 20.
Voir aussi : informations
pratiques
Pour en savoir plus sur la formation : cliquez
ici
Inscription :
Date limite pour les inscriptions : Mise à jour en cours
...
Par téléphone : 01 39 20 13 55
Par fax : 01 39 20 03 55
Par email : training@precilog.com
Par formulaire : inscription
en ligne
|