Scribd
Upload
70 views4 pages

SCET NC Overview and Analysis

The document discusses the scope of software metrics in software engineering. It covers several topics including cost and effort estimation, productivity measures and models, data collection, quality models and measurement. Specifically, it discusses techniques for software cost estimation, defines productivity and productivity models, outlines the process of data collection, and describes three categories of quality models - overall, segmented, and dynamic models.

Uploaded by

more_sitaram
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
70 views4 pages

SCET NC Overview and Analysis

The document discusses the scope of software metrics in software engineering. It covers several topics including cost and effort estimation, productivity measures and models, data collection, quality models and measurement. Specifically, it discusses techniques for software cost estimation, defines productivity and productivity models, outlines the process of data collection, and describes three categories of quality models - overall, segmented, and dynamic models.

Uploaded by

more_sitaram
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

SCOPE OF SOFTWARE METRICS IN SOFTWARE ENGINEERING

Software metrics is a term that embraces many activities , all of which involve some degree of software measurement  Cost and effort and estimation  Productivity measures and models  Data collection  Quality models and measurement  Reliability models  Performance Evaluation and models  Structural and complexity metrics  Capability-maturity assessment  Management by metrics  Evaluation of methods and tools

 Cost and effort and estimation

Project Costs
Software project managers are responsible for controlling project budgets so, they must be able to make estimates of how much a software development is going to cost. Software cost estimation is a continuing activity which starts at the proposal stage and continues throughout the lifetime of a project. Projects normally have a budget, and continual cost estimation is necessary to ensure that spending is in line with the budget. Effort can be measured in staff-hours or staff-months (Used to be known as man-hours or manmonths). Boehm (1981) discusses seven techniques of software cost estimation: (1) Algorithmic cost modeling (2) Expert judgement (3) Estimation by analogy (4) Parkinson's Law (5) Pricing to win (6) Top- down estimation (7) Bottom- up estimation

 Productivity measures and models


Productivity in economics is the ratio of what is produced to what is required to produce. Productivity is the measure on production efficiency. Productivity model is a measurement method which is used in practice for measuring productivity. Productivity model must be able to solve the formula Output / Input when there are many different outputs and inputs.

 Data collection
Data collection is a term used to describe a process of preparing and collecting data, for example, as part of a process improvement or similar project. The purpose of data collection is to obtain information to keep on record, to make decisions about important issues, to pass information on to others. Primarily, data are collected to provide information regarding a specific topic.[1] Data collection usually takes place early on in an improvement project, and is often formalised through a data collection plan[2] which often contains the following activity. 1. Pre collection activity agree on goals, target data, definitions, methods 2. Collection data collection 3. Present Findings usually involves some form of sorting[3] analysis and/or presentation.

4.

Quality models and measurement


- There are three subcategories of generalized models: Overall models: provides a single estimate of product quality, for instance using the defect density. Segmented models: provides different quality estimates for different industrial segments, for instance, by providing different defect density estimates according to market segments or products groups (e.g., safety critical software, commercial software, auxiliary software) Dynamic models: provides quality trend or distribution over time or development phases (e.g., the Putnam model, that generalizes empirical effort and defect profiles over time into a Rayleigh curve).

You might also like