Measurements in Software Engineering.pptx

It describes the different measurements in software engineering

1. Measurement: WHAT it is.. WHY DO IT..? ? ?

2. Topics Covered What is measurement? General Observations Measurement in Software Engineering Scope of Software Metrics Conclusion

3. Measurement Measurement is the process by which number or symbols are assigned to attributes of entities in the real world in such a way as to describe them according to clearly defined rules. Thus, measurement captures information aout attributes of entities. We define the attributes using numbers or symbols. Makes the picture of a thing. Hence, we can make judgements about entities solely by knowing and analyzing their attributes. 16/01/2018

4. General Observations The accuracy of a measure depends on the measuring instrument as well as on the definition of the measurement. Even when measuring devices are reliable and used properly, there is margin for error in measuring the best understood physical attributes. Is the scale acceptable for the purpose to which it is put ? What kind of manipulation can we apply to the results of measurement? 16/01/2018

5. 16/01/2018 “What is not measurable make measurable”. …Galileo Galilei Measurement makes concepts more visible and thus more understandable and controllable. Measuring the unmeasurable should improve our understanding of particular entities and attriutes . Quantification of things becomes possible. Two types of quantification – Measurement and Calculation.

6. Measurement in Software Engineering Neglect of measurement in software engineering for most of development projects results in - Fail to set measurable target for product. Gilb’s Principle of Fuzzy Targets : projects without clear goals will not achieve their goals clearly. Fail to understand and quantify component cost. Fail to quantify or predict the quality of produced products. Fail to determine whether the used new technology is effective and efficient. 16/01/2018

7. Measurement in Software Engineering Objective for software engineering should be fulfilled and must be specific, tied to what the managers, developers and users need to know. Managers’ Goals What does each process cost? How productive is the staff? How good is the code being developed? Will the user be satisfied with the product? How can we improve? Engineers’ Goals Are the requirements testable? Have we found all the faults? How we met our product or process goals? What will happen in the future? 16/01/2018

8. Measurement in Software Engineering Measurement is important for three basic activities: There are measures that help us to understand what is happening during development and maintainance . Measurement allows us to control what is happening on our projects. Measurement encourages us to improve our processes and products. 16/01/2018

9. Scope of Software Metrics Cost and Effort Estimation COCOMO Model Putnam‘s SLIM Model Albercht’s Function Points Model Productivity models and measures Staff Productivity Data Collection Unambiguity, consistency and completeness of data and data integrity 16/01/2018

10. Scope of Software Metrics Quality Models and Measures 16/01/2018

11. Scope of Software Metrics Reliability Models Performance evaluation and models Structural and Complexity Metrics Management by Metrics Evaluation of methods and tools Capability maturity assessment SEI CMM Model 16/01/2018

12. Conclusion Measurement plays a significant role in S oftware Engineering. Software Measurement done by software metrics is a diverse collection of fringe topics that range from models for predicting software project costs at specification stage to measures of program structure. We must be bold in our attempts at measurement. Just because no one has measured some attributes of interest does not mean that it cannot be measured satisfactorily. 16/01/2018