Requirements-Based Cost Models (ROBUST - Requirements Ordered Budget Using Scheduling Tools)

Project cost is a primary factor in determining which projects to implement. Projects always have an explicit or implicit set of requirements between client and developer. Requirements are usually specified using an outline metaphor where key project functionality is continuously broken down into sub-requirements using sub-paragraphs to clarify the detail. Unfortunately, this metaphor makes it difficult to accurately estimate project costs because it does not: >> Uniquely identify each requirement. >> Link each requirement to one or more of the project's tasks. >> Associate percentage of cost for each project task with the relevant requirements. >> Automatically adjust for new, deleted or changed requirements in a timely manner. What is needed is a new metaphor for specifying requirements that is conducive to establishing the one-to-one or one-to-many linkage between requirements and project tasks. IPM is proposing a system that will provide the ability to assure that each requirement is: >>> Understandable same by all stakeholders. >>> Uniquely identifiable. >>> Linkable to one or more scheduled tasks. >>> Able to link each scheduled task to one or more requirements. >>> Readily able to provide an accurate estimate of project cost at anytime.