Comprehensive Requirements Traceability
Requirements capture and maintaining change those requirements have been proven to matter in I.T. projects. CoRT provides a simple colaborative environment for Comprehensive Requirements
Traceability.
Capturing requirements into the system is straight forward but only a single part of what CoRT offers, once in the system requirments can be assessed and risk managed. Project artifacts such as Requirements Specifications can be automatically generated. Change Control can be utilised with the systems ability to analyse the changes effect. Finally Release management support helps define what will be offered and provide projects managers insight to where run overs could occur.
Capturing requirements into the system is straight forward but only a single part of what CoRT offers, once in the system requirments can be assessed and risk managed. Project artifacts such as Requirements Specifications can be automatically generated. Change Control can be utilised with the systems ability to analyse the changes effect. Finally Release management support helps define what will be offered and provide projects managers insight to where run overs could occur.
Capturing Change |
Management Support |
| Through-Life Requirements Management: Beyond inputting or importing requirements into the system, CoRT offers the capability to keep track of requirements as the project progresses, ensuring requirements at a lowerer level are traceable through to the next stage. Project Activity: CoRT provides detailed information on the changes taking place at both the requirement and project level. If a project member updated a requirement on Tuesday then everyone on the project can see this. If the project manager assigned staff to a team this is there too, keeping all the staff up to date with the developments of the project. Risk Management CoRT integrates a simple Risk Management process to track risks against both the project and individual requirements allowing visibility of potential problems to all staff as well as summerising risk areas for project managers. |
Change Affect Analysis When a change is requested against an existing requirement, CoRT uses the relationships to suggest what might be affected if the change was accepted. Release Planning Being able to specify what requirements are going to be complete for the next release CoRT is capable of finding problems where for example the estimate delivery of a requirement is beyond the release date or where a single member of staff has more days work then available. Enhanced Awareness Changes in Requirements, Risks and Change Requests and many more of the items tracked by CoRT rely these changes back to the project summary, making it easy to see what has been done. Comments on a requirement for example aren't just lost into a system never to be seen again, much more benifital in keeping everyone not just management up to date. |
Why Manage Requirements? |
What Do I Need? |
| Use of a Requirements Management tool
and importantly a central repository for
requirements, has been shown to have
positive correlation with project success. Change control is important to reduce Requirements creep a major problem that will affect one or more of the cost, time or quality factors in a project. Requirements traceability helps ensure the system built is consistent with the system’s user’s requirements. |
A Javascript enabled browser
|
Requirements engineering and software project success - Verner, J. et al.
|
