Requirements Solicitation Model

Requirements Solicitation Model

Requirements Solicitation Model - Gathering requirements requires more than just talking to people, writing down their ideas and then building a solution.

It is important to have a logical and structured model for gathering requirements as your solution gets more complex and you need input from larger numbers of people.

The following four-step model is used to gather, organize and approve the final requirements.

1. Elicitation. The Elicitation step is where the requirements are first gathered from the client. To elicit accurate requirements, the analyst must ask the right kind of questions and then listen carefully to the answers.

There are a number of techniques for eliciting requirements, and your project may need to use multiple techniques depending on the circumstances.

2. Requirement Specification. Once the Elicitation and Validation steps are completed, proceed to Specification. During this step, the analyst prioritizes and formally documents the requirements in a Requirements Definition Report.

The requirements are also numbered in a way that allows them to be tracked through the rest of the lifecycle. Finally, they are checked to make sure that they can ultimately be tested.

3. Requirement Validation. The Validation step is where the "analyzing" starts. The purpose of validation is to make certain that the information conveyed during elicitation accurately represents the needs and expectations of the clients and stakeholders.

This information is then given back to the people who provided the requirements, possibly in a number of formats, to make sure that the requirements are accurate.

At this point, the analyst is not validating that the requirements are valid. The purpose is to make sure that the analyst is accurately representing the requirements as stated by each stakeholder.

4. Requirement Verification. The final step in the requirements gathering process is verifying that the documented requirements accurately and completely communicate the needs and expectations of the client.

The requirements are reviewed and formally approved, and the project completes whatever else is necessary to gain permission to proceed to the next phase of the project.

During this step, the analyst can also develop acceptance criteria and start to write test cases for the final solution.

Requirements Management Plan


Libro El Director de Proyectos Práctico -

Un Método probado de 28 Pasos para completar tu Proyecto Exitosamente

EL DIRECTOR DE PROYECTOS PRACTICO -

Por fin ─ un libro sencillo con un método paso a paso para completar tu proyecto.

¡Y sin tener conocimiento previo sobre administración de proyectos!

Toda la "paja" de la metodología de dirección de proyectos fue eliminada, dejando solo lo que es absolutamente útil para completar la tarea.

El Director de Proyectos Práctico, Project Management for Small Projects. 

Un libro pensado en el líder de proyectos empírico que salió ganador de la rifa del tigre. Pues ya tiene la responsabilidad de un proyecto, pero que no sabe ni por donde empezar. Necesita una receta ABC para seguir.

Contiene 260 páginas perfectamente detalladas con ejemplos e ilustraciones, que te llevan de la mano hasta completar tu proyecto.

Pruébalo, síguelo, ten éxito. O sigue haciendo lo mismo... :(

Disponible en Amazon

Compra aquí El Director de Proyectos Práctico en su versión electrónica─

Entrega inmediata.

BONO ADICIONAL:  El libro incluye todos los templates─plantillas─que necesitas, listos para ser usadas. No necesitas comprar nada mas.


COPYRIGHT © 2007-2012 por Hector Olvera Padilla 1853071. Reproduction in whole or in part, or translation without written permission is prohibited. "PMP®", "PMBOK®", and "PMI®" are registered marks of the Project Management Institute, Inc.