Lecture "Software engineering - Lecture 12: Software metrics" has contents: Why measure software, fundamentals of measurement theory, use case points. Invite you to consult | SOFTWARE ENGINEERING Lecture 12 Software Metrics MBA Course Notes Dr. ANH DAO NAM 1 Software Engineering Slides are from Ivan Marsic and Thomas E. Potok, and Richard A. Volz, modified by Anh Dao Nam Textbooks: Bruegge & Dutoit: Object-Oriented Software Engineering: Using UML, Patterns and Java, Third Edition, Prentice Hall, 2010. Miles & Hamilton: Learning UML , O’Reilly Media, 2006. Some interesting sources for the advanced material include: Richard A. Volz, Technical Metrics for Software R. Pressman, Software Engineering - A Practitioner's Approach, 6th ed., 2005 C. Ghezzi, M. Jazayeri, and D. Mandriolo, Fundamentals of Software Engineering. Prentice Hall, second ed., 2002 A. Endres and D. Rombach, A Handbook of Software and Systems Engineering. The Fraunhofer IESE Series on Software Engineering, Pearson Education Ltd., 2003. S. Robertson and J. C. Robertson, Mastering the Requirements Process. Addison-Wesley Professional, second ed., 2006. 2 Topics Why Measure Software Fundamentals of Measurement Theory Use Case Points 3 Definitions Measure - quantitative indication of extent, amount, dimension, capacity, or size of some attribute of a product or process. ., Number of errors Metric - quantitative measure of degree to which a system, component or process possesses a given attribute. “A handle or guess about a given attribute.” ., Number of errors found per person hours expended 4 Motivation for Metrics Estimate the cost & schedule of future projects Evaluate the productivity impacts of new tools and techniques Establish productivity trends over time Improve software quality Forecast future staffing needs Anticipate and reduce future maintenance .
