Software sizing and estimating: Mk II FPA (Function Point Analysis)
Software sizing and estimating: Mk II FPA (Function Point Analysis)
Why is Software Late? An Empirical Study of Reasons for Delay in Software Development
IEEE Transactions on Software Engineering
Software Development Productivity of European Space, Military, and Industrial Applications
IEEE Transactions on Software Engineering
A Validation of Object-Oriented Design Metrics as Quality Indicators
IEEE Transactions on Software Engineering
Software metrics (2nd ed.): a rigorous and practical approach
Software metrics (2nd ed.): a rigorous and practical approach
Improving Speed and Productivity of Software Development: A Global Survey of Software Developers
IEEE Transactions on Software Engineering
Managerial Use of Metrics for Object-Oriented Software: An Exploratory Analysis
IEEE Transactions on Software Engineering
Investigating quality factors in object-oriented designs: an industrial case study
Proceedings of the 21st international conference on Software engineering
IEEE Transactions on Software Engineering - Special section on the seventh international software metrics symposium
Software Engineering Economics
Software Engineering Economics
Migrating to Object Technology
Migrating to Object Technology
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
Predicting weekly defect inflow in large software projects based on project planning and test status
Information and Software Technology
Adopting model driven software development in industry: a case study at two companies
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Predicting short-term defect inflow in large software projects: an initial evaluation
EASE'07 Proceedings of the 11th international conference on Evaluation and Assessment in Software Engineering
International Journal of Open Source Software and Processes
Hi-index | 0.00 |
The high non-functional requirements on mobile telecommunication applications call for new solutions. An example of such a solution can be a software platform that provides high performance and availability. The introduction of such a platform may, however, affect the development productivity. In this study, we present experiences from research carried out at Ericsson. The purpose of the research was productivity improvement and assessment when using the new platform. In this study, we quantify and evaluate the current productivity level by comparing it with UNIX development. The comparison is based on two large, commercially, available systems. We reveal a factor of four differences in productivity. Later, we decompose the problem into two issues: code writing speed and average amount of code necessary to deliver a certain functionality. We assess the impact of both these issues. We describe the nature of the problem by identifying factors that affect productivity and estimating their importance. To the issues identified we suggest a number of remedies. The main methods used in the study are interviews and historical data research.