Browsing by Author "Basavaraj, M.J."

Now showing 1 - 6 of 6

Activity-based software estimation using work break down structure
(2007) Basavaraj, M.J.; Shet, K.C.
Software Cost estimation at activity level is very much accurate than macro estimation with respect to phases of software development life cycle, but the same is very difficult to achieve[1]. Activity based estimation focus on key activities should not be left out and if any effort variance occurs it will be possible to track at particular activity level rather than affecting the entire activities[1]. Activity-based Software estimation based on work break down structure has been explained by collecting and analyzing the data for 12 Enhancements from Application service Maintenance project which were already delivered. This paper explains how to arrive accurate estimation at different micro level activities of Software Development Life Cycle(SDLC). � 2007 Springer.
Activity-based software estimation using work break down structure
(Kluwer Academic Publishers, 2007) Basavaraj, M.J.; Shet, K.C.
Software Cost estimation at activity level is very much accurate than macro estimation with respect to phases of software development life cycle, but the same is very difficult to achieve[1]. Activity based estimation focus on key activities should not be left out and if any effort variance occurs it will be possible to track at particular activity level rather than affecting the entire activities[1]. Activity-based Software estimation based on work break down structure has been explained by collecting and analyzing the data for 12 Enhancements from Application service Maintenance project which were already delivered. This paper explains how to arrive accurate estimation at different micro level activities of Software Development Life Cycle(SDLC). Â© 2007 Springer.
Empirical validation of software development effort multipliers of intermediate COCOMO model
(2008) Basavaraj, M.J.; Shet, K.C.
Intermediate COCOMO Model computes effort as a function of program size and a set of cost drivers. Effort adjustment factor (EAF) is calculated using 15 cost drivers. EAF is an important significant factor in computing software development effort. We have taken one delivered development project of size of 479 function points and planned for 917 Person days of SEI CMM Level 5 "Excellent" Company as a case study to analyze the EAF. We have empirically validated the cost driver model for Intermediate COCOMMO using this projects data. Validation has been done by using other two development projects data of Excellent Company. From our analysis, we have found that cost drivers defined ratings need to be revisited for the projects of size less than 10 Person months. We have come out with ratings for some cost drivers where earlier it was not defined. This approach helps the project managers to anticipate and estimate the efforts for development projects preferably less than 10 Person months. We have achieved approximately 30% improvement in effort variance by following this approach. © 2008 Academy Publisher.
Estimating and prediction of turn around time for incidents in application service maintenance projects
(Academy Publisher, 2008) Basavaraj, M.J.; Shet, K.C.
Application Service Maintenance Projects normally deals with Incidents as First Level support function. Incidents in majority directly link with Production Environment, so Turn around Time for Incidents is a significant factor. Many Companies are having Service Level Agreements with Customer for Turn around Time for Incidents. There is a need to focus on Estimating and Predicting Turn around Time for Incidents. Improvement in Turn around Time helps in improving the Service Level Agreements earlier agreed with the Customer. Saved time can be diverted to other Project Activities like Enhancements or for new requests. This will also helps as one of the paths for Companies to get new business with the Customer. We have used Capability Maturity Model Integration(CMMI)V1.2 Quantitative Project Management(QPM) methodology for Application Service Maintenance(ASM) Projects for estimating and predicting turn around time for incidents. By implementing this best practice in SEI CMMI Level 5 Company we have achieved a significant improvement of approximately 50 percent reduction in Average Turn around Time for incidents. © 2008 Academy Publisher.
Software estimation using function point analysis: Difficulties and research challenges
(2007) Basavaraj, M.J.; Shet, K.C.
Function Point Analysis method serves better efficient way of predicting estimation in beginning phase of software development life cycle(SDLC). Size and complexity of the software can be derived by function point analysis method. Difficulties of estimation using LOC(Lines of Code) can be avoided using Function Point Analysis, since it deals directly with functions or requirements and independent of language or technology. This paper explains how to calculate Function point analysis for the case study Defect Tracking System(DTS) by using function point analysis. Defect tracking system(DTS) case study has been taken from "XYZ" company. In the intention of maintaining confidentiality, authors are not disclosing the company name. Authors also discusses difficulties and challenges by using Function Point Analysis as part of their Research Work. � 2007 Springer.
Software estimation using function point analysis: Difficulties and research challenges
(Kluwer Academic Publishers, 2007) Basavaraj, M.J.; Shet, K.C.
Function Point Analysis method serves better efficient way of predicting estimation in beginning phase of software development life cycle(SDLC). Size and complexity of the software can be derived by function point analysis method. Difficulties of estimation using LOC(Lines of Code) can be avoided using Function Point Analysis, since it deals directly with functions or requirements and independent of language or technology. This paper explains how to calculate Function point analysis for the case study Defect Tracking System(DTS) by using function point analysis. Defect tracking system(DTS) case study has been taken from "XYZ" company. In the intention of maintaining confidentiality, authors are not disclosing the company name. Authors also discusses difficulties and challenges by using Function Point Analysis as part of their Research Work. Â© 2007 Springer.