Some Requirements Management (Rational Requisite Pro) Best Practices

Here are some of my key suggestions for using Rational ReqPro management tool well - apply to most other comparable requirements management (RM) tools.

Favor physical integration and logical separation for enterprise requirements work. There is effort and cost to deploying consolidated RM repositories but this is almost always overwhelmingly overcome by the benefits in terms of impact on the enterprise system development capability. Physical separation should be reserved for the situations that demand it - when handling classified information, preserving client confidentiality, when working as a custom developer for many legally distinct clients. Otherwise, consolidate the requirements physically (same server, same database engine, etc.) as much as possible and use logical mechanisms (requirements types, values in the requirements attributes, etc.) to sort out your requirements.
Read more »

No comments: