Software Engineering Report: Software Metrics

Palestine Polytechnic University

Graduate Studies

Master of Informatics

Software Engineering

Report: Software Metrics

Name: Labib F. Khamayseh

Supervisor:

DR. Sami Taha.

This report is submitted in partial fulfillment of the requirements of Software Engineering course

April 24

1. Introduction

Software metrics are important metric in the entire software life cycle. as well The software metric is a quantitative measure of the degree to which the system software or process owns some property It provides a measure of the development of software, including software documentation requirements, designs, programs and tests. Rapid developments of the software has been developed on a large scale of complexity that makes it

The inference, of course, is that the quality of the field in the absence of software bugs, Software quality metrics are a subset of metrics programs that focus on aspects of product quality, process, and project, For example, the use of density measurements error per thousand lines of code discovered in the year or in the release. This is less than the measures imposed values higher build quality or release, In general, software quality metrics are closely associated with the process and product metrics of the project metrics. However, the project parameters such as the number of developers and their skill levels, schedule, size, organizational structure certainly affect the quality of the product, Software quality is a multidimensional concept, Multiple views of the professional quality of the product may be very different from the views of a popular or non-specialist, Software quality metrics can be further divided into the final product quality standards and quality standards in the

10. Weaknesses of function metrics:

1- Counting function requires a great deal of experience.

2- counting function can be lengthy and expensive.

3- automation function count is accurate indefinitely.

4- charges function cannot be relied upon for those projects that are less than 15 function in size.

5- function variant do not have the conversion rules to IFPUG function

11. Limitations

As software development is a complex process, with large variation both methodologies and goals, it is difficult to identify or measure the qualities and quantities of software and specify a valid measurement and simultaneous measure, especially when making such a prediction by the detail design. Another source of difficulty and the discussion is to identify metrics that matter, and what it means (1,2) tool practical assistance measurements software has therefore been limited to the following areas:

• Scheduling

• sizing software

• complexity of programming

• Software development effort estimation

• Software Quality

And specific measurement may target one or more of the above-mentioned aspects, or the balance between them, for example, as an indicator of the motives of a team or project