Software metrics: establishing a company-wide program
Software metrics: establishing a company-wide program
Measuring software design quality
Measuring software design quality
Practical software metrics for project management and process improvement
Practical software metrics for project management and process improvement
Prototyping vs. specifying: A multi-project experiment
ICSE '84 Proceedings of the 7th international conference on Software engineering
Software quality &equil; test accuracy × test coverage
ICSE '82 Proceedings of the 6th international conference on Software engineering
Experiences of software quality management using metrics through the life-cycle
Proceedings of the 18th international conference on Software engineering
Conceptual simplicity meets organizational complexity: case study of a corporate metrics program
Proceedings of the 20th international conference on Software engineering
Software quality analysis and measurement service activity in the company
Proceedings of the 20th international conference on Software engineering
Metrics in the software engineering curriculum
Annals of Software Engineering - Special issue on software engineering education
Validation of an Approach for Improving Existing Measurement Frameworks
IEEE Transactions on Software Engineering
The measurement of software design quality
Annals of Software Engineering
Test and evaluation of distributed information system networks
Annals of Software Engineering
The Usability Problem Taxonomy: A Framework for Classificationand Analysis
Empirical Software Engineering
Software Metrics Knowledge and Databases for Project Management
IEEE Transactions on Knowledge and Data Engineering
IT measurement
Complexity and Performance in Parallel Programming Languages
HIPS '97 Proceedings of the 1997 Workshop on High-Level Programming Models and Supportive Environments (HIPS '97)
Aspect-oriented implementation method: progressive or non-progressive approach?
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Subjective evaluation of software evolvability using code smells: An empirical study
Empirical Software Engineering
Embedded agents: a paradigm for mobile services
International Journal of Web and Grid Services
Formulation of Clamshell Diagram and Its Application to Source Code Reading
Proceedings of the 2008 conference on Knowledge-Based Software Engineering: Proceedings of the Eighth Joint Conference on Knowledge-Based Software Engineering
Goals, questions and metrics for architectural decision models
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
ACM SIGSOFT Software Engineering Notes
Hi-index | 4.10 |
The word success is very powerful. It creates strong, but widely varied, images that may range from the final seconds of an athletic contest to a graduation ceremony to the loss of 10 pounds. Success makes us feel good; it's cause for celebration. All these examples of success are marked by a measurable end point, whether externally or self-created. Most of us who create software approach projects with some similar idea of success. Our feelings from project start to end are often strongly influenced by whether we spent any early time describing this success and how we might measure progress. Software metrics measure specific attributes of a software product or a software development process. In other words, they are measures of success. It's convenient to group the ways that we apply metrics to measure success into four areas. What do you need to measure and analyze to make your project a success? We show examples from many projects and Hewlett Packard divisions which may help you chart your course.