A program manager's guide for software cost estimating
Dobbs, Andrew L.
MetadataShow full item record
This thesis will assist current and future program managers by outlining a process to ensure the software cost estimates developed for a system will be credible and supportable throughout the life of the program. This thesis also identifies many of the problems associated with software cost estimating and recommends potential solutions. One of the critical parameters for estimating software cost is the quantity of source lines of code (SLOC) required in the program. Therefore, this thesis examines the software cost implications of improperly estimating SLOC and function points. Some of the other parameters required to estimate the software cost include language, functionality, application, software processes maturity, programmer skill level, design and reuse, productivity factors, complexity, utilization and schedules. Many of these parameters overlap. For example, both the complexity of the code and skill level of the programmer directly impacts the productivity and schedule of the program. This thesis provides a broad view of the software cost estimating process. In the reference and appendix section, a list of valuable resources including commercial estimating models is provided for further assistance.
Approved for public release, distribution is unlimited
Showing items related by title, author, creator and subject.
Naegel, Brad R. (Monterey, California. Naval Postgraduate School, 2017-04-19); NPS-CE-17-042Department of Defense (DoD) software-intensive systems and the software content in other systems will continue to grow and may dominate total ownership costs (TOC) in the future. These costs are exacerbated by the fact ...
Naegle, Brad R. (Monterey, California. Naval Postgraduate School, 2017-04); NPS-CE-17-042Department of Defense (DoD) software-intensive systems and the software content in other systems will continue to grow and may dominate total ownership costs (TOC) in the future. These costs are exacerbated by the fact ...
Sams, Bradley J. (2011-08-29); NPS-CE-11-160Throughout software''s lifetime, changes are introduced to the code in order to maintain the desired performance. These changes often create side effects, which cause other cascading effects elsewhere in the software or ...