SOFTWARE PROCESS & PROJECT METRICS

MEASURES

  • Quantitive indication of the Extent, Amount, Dimension, Capacity, or Size of some attributes of a product or process.
  • Measurement can be defined as the process of determining the measure.
  • All measures are composed of a value (a number) and a unit of measure.
  • The number provides magnitude for the measure (how much), while the unit gives the number meaning (what is measured).

METRICS (a given attribute to how many degrees)

  • Metrics can be defined as quantitative measures that allow software engineers to identify the efficiency and improve the quality of software processes, projects, and products.
  • IEEE defines a metric as “a quantitative measure of the degree to which a system, component, or process possesses a given attribute.”
  • Metrics represent the different methods we apply to understand change over time across a number of dimensions or criteria.
  • The goal of software metrics is to identify and control essential parameters that affect software development.

example, Mesure -> 1200 pageviews

Metrics -> Views on per page

INDICATORS

  • An indicator is a qualitative or quantitative factor or variable that provides a simple and reliable mean to express achievement, the attainment of a goal.
  • They are also called Key Performance Indicators (KPIs).
  • It often aggregates or combines multiple measures in an explicit formula.
  • examples are- 1M weekly active users, 1:2 users completing the story, 23% homepage bounce rate.
  • They work as a clue as to whether everything is going well and whether the desired goals have been achieved.
  • KPIs evaluate organizational performance, assist in trend analysis, and promote continuous improvements and proactive performance, besides transparent management of processes and staff.
  • They are usually expressed in percent rate of frequency formats.

SOFTWARE QUALITY

Quality software is reasonable bug or defect-free, delivered on time and within budget, and meets requirements and/or expectations.

Key aspects of quality for the customer include:

  • GOOD DESIGN- look and style.
  • GOOD FUNCTIONALITY- it does the job well.
  • RELIABLE- acceptable level of breakdowns or failure.
  • CONSISTENCY- should work consistently.
  • DURABLE- lasts as long as it should.
  • GOOD AFTER-SALES SERVICE
  • VALUE FOR MONEY

SOFTWARE QUALITY METRICS

Software Measurement is alone based on some software metrics where the software quality metrics are referred to as the measure of various characteristics of software.

  • CODE QUALITY
  • RELIABILITY
  • PERFORMANCE
  • USABILITY
  • CORRECTNESS
  • MAINTAINABILITY
  • INTEGRITY
  • SECURITY

SOFTWARE MEASUREMENT

A measurement is a manifestation of the size, quality, amount, or dimension of a particular, attribute 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. The software measurement process is defined and governed by ISO standards.

CLASSIFICATION OF SOFTWARE MEASUREMENT

  1. DIRECT MEASUREMENT: the product, process, or thing is measured directly using a standard scale.
  2. INDIRECT MEASUREMENT: the quantity or quality is measured using a related parameter i.e, by use of reference.

METRICS IN THE SOFTWARE PROCESS AND PROJECT DOMAIN

  • CORRECTNESS
  • MAINTAINABILITY
  • INTEGRITY
  • USABILITY

Comments

Post a Comment

Popular posts from this blog

DESIGN PRINCIPLES

PROBLEM PARTITIONING: Divide the problem and conquer the problem it means to divide the problem into smaller pieces so that each can be captured separately. ABSTRACTION: The process of hiding certain details and showing only essential information to the user. MODULARITY: It specifies the division of software into separate modules which are differently named, addressed, and integrated later on in to obtain completely functional software. STRATEGY OF DESIGN: To design a system, there are two possible approaches- Top-Down Approach: main components and then sub-components designed Bottom-Up Approach: sub-components and then integrate them to obtain the main component.
Read more

COMPONENT ASSEMBLY MODEL

This model follows an object-oriented methodology where the whole system is divided into components, if they are already available in the library then we import them else we have to build them and at last, we construct the system by integrating them. CHARACTERISTICS: Use of object-oriented technology. Component-class that encapsulates both data and algorithm. Component delivered to be reusable. Paradigm similar to spiral model, but engineering activity involves components. The system is produced by assembling the correct components. ADVANTAGES: Time and resource conservative. Having object-oriented methodology. Components are built once and then they can be reused further. Suitable for small to large object-oriented projects. Very low cost in the construction of the system. DISADVANTAGES: Can’t use it for pioneering projects. Needs good planning and design. Needs a clear and complete definition of the whole system before dividing it into components. Need experts to divide the syst...
Read more

SOFTWARE TESTING

Image
It is a process of verifying and validating that software or application is bug-free, meets the technical requirements as guided by its design and development, and meets the user requirements effectively and efficiently with handling all the exceptional and boundary cases. SOFTWARE TESTING STRATEGIES VERIFICATION: It refers to the set of tasks that ensure that software correctly implements a specific function. VALIDATION: It refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements. Verification -> “Are we building the product right?” Validation -> “Are we building the right product?” TYPES OF SOFTWARE TESTING MANUAL TESTING: Manual testing includes testing software manually which means without using any automated tool or any script. The tester takes over the role of an end-user and tests the software to identify any unexpected behavior or bug. There are different stages for manual testing suc...
Read more