Software sizing and estimating: Mk II FPA (Function Point Analysis)
Software sizing and estimating: Mk II FPA (Function Point Analysis)
Object-oriented modeling and design
Object-oriented modeling and design
Reliability of function points measurement: a field experiment
Communications of the ACM
Role model based framework design and integration
Proceedings of the 13th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Object-oriented framework-based software development: problems and experiences
ACM Computing Surveys (CSUR)
Quality, Productivity, and Learning in Framework-Based Development: An Exploratory Case Study
IEEE Transactions on Software Engineering
The cost of errors in software development: evidence from industry
Journal of Systems and Software
Identifying High Performance ERP Projects
IEEE Transactions on Software Engineering
Framework Composition: Problems, Causes and Solutions
TOOLS '97 Proceedings of the Tools-23: Technology of Object-Oriented Languages and Systems
Integrating diverse paradigms in evolution and maintenance by an XML-based unified model
Journal of Software Maintenance: Research and Practice
Software Productivity Measurement Using Multiple Size Measures
IEEE Transactions on Software Engineering
Framework specialization aspects
Proceedings of the 6th international conference on Aspect-oriented software development
A model-driven approach to variability management in product-line engineering
Nordic Journal of Computing - Selected papers of the fourth nordic workshop on UML and software modelling (NWUML'06), June 12-14, 2006
Identifying and addressing problems in object-oriented framework reuse
Empirical Software Engineering
Evaluating ERP projects using DEA and regression analysis
International Journal of Business Information Systems
A case study of pattern-based software framework to improve the quality of software development
Proceedings of the 2009 ACM symposium on Applied Computing
An empirical examination of application frameworks success based on technology acceptance model
Journal of Systems and Software
Automating the construction of domain-specific modeling languages for object-oriented frameworks
Journal of Systems and Software
Pattern-based framework for modularized software development and evolution robustness
Information and Software Technology
Feature-oriented language families: a case study
Proceedings of the Seventh International Workshop on Variability Modelling of Software-intensive Systems
Information and Software Technology
Hi-index | 4.10 |
How much will it cost?" "How long will it take?" These questions are notoriously difficult to answer accurately and early in software development. Software metrics tackle this problem by assuming a statistical correlation between the size of a software project and the amount of effort typically required to realize it. To be useful in estimating cost, a size metric must take into account the inherent complexity of the system. Such metrics have been applied with varying degrees of success, but the nature of software development has been changing, and some of the assumptions behind the established cost-estimation techniques are slowly being invalidated. The System Meter (SM) is a new software sizing approach based on the notion of system description. System descriptions encompass all kinds of software artifacts, from requirement documents to final code. For each kind or level of artifacts, there is a corresponding flavor of SM. In our studies we used the first operational flavor, the SM at the preliminary analysis level, or Pre-SM. In contrast to the well-known Function Point (FP) metric, which is measurable after the more detailed but costly phase of domain analysis only, the SM explicitly takes OO concepts into account. It also distinguishes between components to be developed and those to be reused, thus reflecting the idea of incremental functionality. In this article we present results of a field study of 36 projects developed using object technology. We measured both FP and the Pre-SM method in all 36 projects and compared their correlation to the development effort.