Software Project Cost Estimation Using COCOMO Model With Respect To Requirement Mapping

In Analysis Phase we gather requirements and analyse the business requirements to identify the specific activities and resources required to complete the project. The project manager must work with the user, who has given business requirements to define quantifiable criteria such as: Schedule, effort & cost. After all the requirements are identified the project manager needs to document it. The requirements may be divided into six categories: Functional, non-functional, technical, user, business and regulatory requirements. The process of breaking down the work of the project via a work breakdown structure (WBS) begins after the requirements are identified. The dependencies among requirements are worked out to develop the project schedule. The first step in developing the schedule is to develop a sequence diagram from WBS. The sequence diagram provides information about how the tasks are related and how long it will take as currently planned to finish the project. Estimation of effort, schedule and cost can be done using expert review, but rather a planning component like COCOMO 2.0 is used here for estimation. A comparison graph of estimation using mapped requirements and unmapped requirements will be provided using COCOMO 2.0. Using the experimental setup it is concluded that the complete mapped requirements gives low cost than the un mapped requirements.