Measurement of Telecommunication Software and Their Human Perspective

Abstract

Software development is the most expensive element of any information technology project these days. Still, many software projects fail due to budget overruns, late delivery, incorrect forecasts or demotivated colleagues. It is important to estimate the costs of and the effort to be invested in necessary software development before starting to develop a software product. The estimation of software costs - the so-called software cost estimation model - is intended to predict the effort that is essential for building a software system. Over the past 40 years, many estimation models have been created for budgeting, risk analysis, project planning and control, and investment analysis for software improvements. There are numerous ways to measure software productivity. Function Point Analysis (FPA) and COCOMO are, for example, based on the implementability, flexibility and traceability of parameters, software cost estimation techniques, and personal and organizational factors. Still, it remains a challenge to find out how the management can be absolutely satisfied and enthusiastic about development teams when the findings show massive numbers of hours of work without real development. Under such circumstances, it is quite obvious that the management wants to find out what personal factors influence employees and what managers can do about them.