Software Measurement: A measurement is an manifestation of the size, quantity, amount or dimension of a particular attributes of a product or process. Software measurement is a titrate impute of a characteristic of a software product or the software process. It is an authority within software engineering. Software measurement process is defined and governed by ISO Standard.
Need of Software Measurement:
Software is measured to:
- Create the quality of the current product or process.
- Anticipate future qualities of the product or process.
- Enhance the quality of a product or process.
- Regulate the state of the project in relation to budget and schedule.
Classification of Software Measurement:
There are 2 types of software measurement:
- Direct Measurement:
In direct measurement the product, process or thing is measured directly using standard scale.
- Indirect Measurement:
In indirect measurement the quantity or quality to be measured is measured using related parameter i.e. by use of reference.
A metrics is a measurement of the level that any impute belongs to a system product or process. There are 4 functions related to software metrics:
Classification of Software Metrics:
There are 2 types of software metrics:
- Product Metrics:
Product metrics are used to evaluate the state of the product, tracing risks and undercovering prospective problem areas. The ability of team to control quality is evaluated.
- Process Metrics:
Process metrics pay particular attention on enhancing the long term process of the team or organisation.
- Project Metrics:
Project matrix is describes the project characteristic and execution process.
- Number of software developer
- Staffing pattern over the life cycle of software
- Cost and schedule
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.
Improved By : Rumor