Requirements Gathering and Management Methodology
•Télécharger en tant que PPT, PDF•
22 j'aime•6,875 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Requirements Gathering and Management Methodology
Similaire à Requirements Gathering and Management Methodology (20)
Plus de Alan McSweeney
Plus de Alan McSweeney (20)
Dernier
Dernier (20)
Requirements Gathering and Management Methodology
- 1. Requirements Gathering and Management Alan McSweeney
- 2. Method for IT Strategy and Architecture - Requirements “ What do Customers Really Want?”
- 10. V Lifecycle Approach V Project Initiation Project Closure System Requirements System Testing High-Level Design Integration Testing Low-Level Design Component Testing Install and Implement Define Requirements and Solution Deliver Solution and Fulfil Requirements
Notes de l'éditeur
- SD have defined the architecture of methodologies. All development work is based upon this architecture. Key components of this architecture are : Process Structure : Stages-Activities-Tasks Roles: who does what Techniques: Best practice ways of doing things Deliverables: what gets produced Tools: Checklists, templates, etc.
- Requirements methodology is one on the methods within the IT Strategy & Architecture process group. Its not a large complex methodology, but it is extremely important, so stands on its own. It is tightly integrated to the Project Management methodology.
- The management stage is iterative in nature, being able to be performed many times. This is because changes cannot be predicted. Note that the development stage can start very early on in the project lifecycle.
- Having a standard approach to specifying requirements gives us the opportunity to fine engineer the process and so keep making it better. The nirvana is always to get all the requirements perfectly specified and agreed, first time.
- Who has ever heard of a project where there are no customer requirements? But the methodology is flexible, and bits can be changed or taken out to suit.