A metrics paradigm for object-oriented analysis and design.
1994
- 43Usage
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage43
- Downloads40
- Abstract Views3
Thesis / Dissertation Description
For several years, the software industry has been affected by a problem called the software crisis. Many software developers have worked hard to determine remedies for this crisis. The crisis deals with products being produced over costs, behind schedule, with low quality, and not meeting customer satisfaction. Processes are being used which waste resources and build low quality products. In dealing with the software crisis, software practitioners have used many tools, methodologies, and metrics to help produce better products, save resources, and increase productivity. Metrics are meaningful measures used to determine how well software is being produced, where weaknesses are in products, processes, or resources, and indicate where to make improvements. Today, the most popular methodology is the Object-Oriented (00) methodology. Users of this methodology want to prove that it helps resolve the software crisis. There is a belief that 00 systems are developed earlier, easier to understand and maintain, and contain reusable components. However, without metrics, the effectiveness of the 00 approach cannot be proven. Metrics must be used to show if the process or resources being used is responsible for the success or failure of software development, if management of the process is responsible, if the complexity or size of the product being produced is responsible, or if a lack of communication or misunderstandings of requirements is responsible. There are many, many reasons why metrics are used and can be seen in this Thesis. Many metrics are being used for traditional software development methodologies that deal with processes, products, and resources. However, there is no metric paradigm for the 00 development methodology. But, there is a small set of metrics proposed for 00 programming. We provide a 00 metric paradigm that contains metrics grouped into nine categories. We grouped the metrics into categories to make the selection of a particular· metric easier. These nine metrics fit nicely into the 00 methodology. The metrics can be used to measure processes, products, and resources. We provide a size estimation method that helps determine progress, costs, quality, effort, complexity, and schedule. The metrics can be used to prove the effectiveness of the 00 methodology and indicate areas for further improvement.
Bibliographic Details
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know