logo

How To Measure The Software

Jan, 26 2021, 12:33 pm [IST]
How To Measure The Software

Software measurement

Measurement in the physical world can be e categories in two ways:

  • Direct measures
  • Indirect measures

Direct measures (internal attributes)

Direct measures of the software engineering process involve cost and effort included. Analysis of the product involves lines of code produced, execution speed, memory size, and defects reported over a period of time.

Indirect measures

Indirect message all the product include functionality, quality, complexity, efficiency, reliability, maintainability, etc. Direct measures can be easily estimated, whereas indirect measures are very hard to estimate.

Size of oriented metrics

Size of the software produced:

  • LOC - Lines of code
  • KLOC - 1000 lines of code
  • SLOC - statement lines of code

LOC metric

A line of code is every line of program text that is not a comment or a blank line, despite the number of statements or fragments of statements on the line. This particularly covers all lines containing program headers, declarations, and executable and non-executable statements.

Function Oriented metrics

Function oriented metrics are indirect measures. It focuses on functionality or e utility and uses the function point method as a productivity measurement. Function points are derived using an empirical relationship based on countable measures of software's information domain and assessments of software complexity.

Feature point matrics

The feature point metrics are an extension of function point metrics. It includes applications in which algorithm complexity is high. To estimate the Future point, information domain values are again counted and weighted. Also, the feature point metric counts new software characteristics algorithms.

The functional point (and its extinction) like the LOC measure, is controversial. Proponents claim that FP is programming language independent but opponents say that it is difficult to collect the fact.

Metrics for software quality

The overloading goal of software engineering is to produce a high-quality system, application, or product. To achieve this goal, software engineering must apply effective methods coupled with modern tools within the context of a mature software process. A good software engineer must measure if high quality is to be realized.

A good software engineer uses measurement to access the quality of the analysis and design models, the source code, and the test cases that have been created as the software is engineered. Metrics used after delivery focus on the number of defects in the system.

The software quality measure is correctness, maintainability, integrity, usability.

Correctness is the degree to which a software its required function. The common measure of correctness is defects per KLOC.

Maintainability is the comfort with which a program can be corrected if an error is found, adapted if its context changes, or improved if the customer Desires a change in demands. Maintainability is measured only through indirect measures like the time it takes to analyze the change request, design a modification, implement and test it and distribute it to all users. Another metrics available for maintainability is cost-oriented metrics the cost to correct defects encounter after the software is reduced to end-users.

Integrity measure the ability to withstand attacks by hackers and viruses both internal and accidental. The attack can be made on all three components of software programs, data, and documents. Related to integrity security also has to be taken care of.

Usability means user-friendliness. If your product is not user friendly then it will be a failure, irrespective of all other factors. Usability is measured through:

  1. The physical and intellectual skills required to learn the system.
  2. The time required to become moderately efficient in the use of the system.
  3. The net increasing productivity, when it is replaced by the old system.
  4. Subjective assessment was obtained through a questionnaire of user attitudes towards the system.

Integrating metrics within the software process

Software developers never thought about measurements or they never realized about measurement. But unless we measure, we will not be able to determine whether we are improving or not. By Requesting and evaluating productivity and quality measures, managers can establish goals for improvement of the software engineering process. So measurement is used to establish a process-based and from which improvement can be calculated. By using these baselines, the project estimates will be made proper, the quality of the product will be increased.

At the time of Data Collection itself, a lot of Investigation should be made, and the data should be reconstructed. This list to proper Analysis of data through LOC or FP metrics and other quality factors. Finally, Matrics must be evaluated and applied during estimation, technical work, project control, and process improvement. This leads to a process set of indicators that guide the project or process.


Share this: FACEBOOK TWITTER WHATSAPP


YOU MAY LIKE

MOST VIEWED

Details About Software Quality Assurance

Dec, 16 2020, 12:02 pm [IST]
Details About Software Quality Assurance

SOFTWARE ENGINEERING

Software quality assurance Software quality is described as conformance to explicitly state functional and performance requirements, explicitly documented standards and implicit features that are anticipated of all professionally developer software ... Read More


Details About Tunnelling and Encapsulation in Mobile IP

Dec, 10 2020, 02:19 pm [IST]
Details About Tunnelling and Encapsulation in Mobile IP

MOBILE COMMUNICATIONS

A tunnel establishes a virtual pipe for data packets between a tunnel entry and a tunnel endpoint. Packets entering a tunnel are forwarded inside the tunnel leave the tunnel unchanged. Tunneling, that is, sending a packet through a tunnel, is achieved by using encapsulation ... Read More


Details About Software Architecture

Dec, 06 2020, 12:17 pm [IST]
Details About Software Architecture

SOFTWARE ENGINEERING

The overall structure of the software components and how the success provides a conceptual integrated file system. In other words, architecture is the hierarchical structure of program components, how these components interact, and the structure of data that are used by the components ... Read More


Details About Real-Time And Distributed System Design

Dec, 04 2020, 01:28 pm [IST]
Details About Real-Time And Distributed System Design

SOFTWARE ENGINEERING

Real-time and distributed system design The real-time system is a software system the correct functioning of the system depends on the results produced by the system the time at which these results are produced ... Read More


Explanation About Software Project Lifecycle Model

Dec, 02 2020, 12:39 pm [IST]
Explanation About Software Project Lifecycle Model

SOFTWARE ENGINEERING

Waterfall Model The waterfall model also called classic life cycle requirements is well defined and stable. It suggests a systematic, sequential approach to software development. It begins with customer specification of requirements and processes through planning, modeling, instruction, and deployment ... Read More


Software Design Concepts in Software Engineering

Dec, 13 2020, 12:01 pm [IST]
Software Design Concepts in Software Engineering

SOFTWARE ENGINEERING

Software Design A software design is an essential engineering description of some software product that is to be established. A design can be determined to the customer's requirements and can be assessed for quality against predefined patterns ... Read More


Go to Top

FOLLOW US: FACEBOOK

About Us | Contact Us | Disclaimer | Privacy Policy | Sitemap | Terms and Conditions

Copyright © 2021 TeluguAsami. All rights reserved.