The craft of software engineering
The craft of software engineering
Cost estimation for software development
Cost estimation for software development
Function Points in the Estimation and Evaluation of the Software Process
IEEE Transactions on Software Engineering
Managing Software Projects
Software Engineering Economics
Software Engineering Economics
A Guide to the Successful Management of Computer Projects
A Guide to the Successful Management of Computer Projects
Allow Plenty of Time for Large-Scale Software
IEEE Software
An analysis of the resources used in the SAFEGUARD system software development
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Controlling Software Projects: Management, Measurement, and Estimates
Controlling Software Projects: Management, Measurement, and Estimates
Combination of software development effort prediction intervals: why, when and how?
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Group Processes in Software Effort Estimation
Empirical Software Engineering
Evidence-Based Guidelines for Assessment of Software Development Cost Uncertainty
IEEE Transactions on Software Engineering
Inconsistency of expert judgment-based estimates of software development effort
Journal of Systems and Software
Software effort estimation terminology: The tower of Babel
Information and Software Technology
Representing the behaviour of software projects using multi-dimensional timelines
Information and Software Technology
Information and Software Technology
A review of studies on expert estimation of software development effort
Journal of Systems and Software
Hi-index | 0.00 |
A method for estimating software development effort in the early phases of a large software-intensive project and a front-end process incorporating this method are presented. The application of this methodology to the domestic US 5ESS Switch project (a large multiyear continuing effort, with new features incorporated into yearly releases) is described. For each feature to be estimated, a feature team generates a detailed feature definition with high-level functionality requirements and a high-level design proposal. These are used in a formal working meeting of estimators from affected parts of the project. The meeting produces a development estimate for use in deciding which features to include in the next release. The benefits of this methodology include well-defined milestones (high-level features requirements, high-level designs and estimates), and less tangible benefits like better working relationships between parts of the project, interorganizational synergy and increased confidence in the front-end process.