Tools collaboration for deployment of a requirements engineering process
Résumé
The first steps of the system and requirements engineering phases of any project are to define the management aspects (management plan, requirements engineering process, schedule management) and the project specifications, in the widest sense: collection, analysis and synthesis of the need expressions from all stakeholders, and definition of requirements to express this need. Then requirements will be allocated, changed, reorganized , and tracked during all the project lifecycle. So the first priority is to have a process, even a simple one, then it's helpful to have this process supported by tools. A good process, even manual, is better than tools used without any process. As there is often a confusion there, it seems important to distinguish 2 steps in a requirements management process : • Requirements elicitation, identification and allocation : For this step there are a lot of publications, feedbacks and studies. These requirements are usually formalized in 'Specifications' documents for the development teams or the subcontractors, • Once formalized, the requirements have to be implemented and tested by the hardware and software development teams. This is the 'requirements traceability'. Requirements and implementation artefacts often change, and the impact of each change must be analyzed.
Origine : Fichiers produits par l'(les) auteur(s)