Many programs face the problem of building a single product that mushrooms into new versions or additional products. Requirements reuse can be a tremendous time and cost saver, but only if other essential information is retained when the original requirements are written.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.