Summary

   

Although requirements will change during project development, change itself need not destabilize the development process. With a comprehensive change control process in place and with requirements artifacts placed under the control of the development team's configuration management system, the team will be well prepared for the key requirements challenge of managing change.

It is important to realize that managing change in a large project is usually too big a job to handle with manual methods . While it can be fairly straightforward to implement a process to control the manner in which each change enters the project, it can still be a formidable task to attempt to understand the ramifications of the change without tools that help us find all the affected elements of the project. Current state-of-the-art tools for managing artifacts and managing code automate and facilitate much of the change management challenge. Use them.

   


Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
EAN: N/A
Year: 2003
Pages: 257

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net