Pt2520 Unit 3 Metrics

In this presentation, the author has explained different metrics and there attributed used to measure software. A person can only measure and represent it in number when he knows something about it. On the other hand, if has no idea about it then he doesn’t have any idea about it [1]. There are two types of software complexity metrics. One gives the efficiency of the machine while running the software which is called as computational complexity. Another one is giving us the factors which affect the software developer capacity to develop good software which is known as psychological complexity. There are two types of software metrics. The process metrics which gives details of the process used such as software life cycle used for development, the time consumed for the development etc. The
In large software products, a measure is a number of functions used. Some studies showed that some programmer uses the same number of functions to solve given a problem. Another important part of the software is data processed. To understand the psychological complexity of software understanding the amount of data processed by the software is important. VARS is the count of all user defined is the variables used during program development. The average number of variables is the sum of the count of live variables divided by executable statement count. The span defines how many times the variable is used. Based on modules sharing data there are two software measurement types Fan-in which gives the number of modules pass data either indirectly or directly. Whereas Fan-out gives the number of modules to which data passed indirectly or directly. There also another measure which is called as decision count which gives the number of decision statement used in the program. Paths are also used to count the number of different ways the program can be