Using software metrics and rigorous software testing

This preview shows page 38 - 39 out of 39 pages.

We have textbook solutions for you!
The document you are viewing contains questions related to this textbook.
Principles of Information Systems
The document you are viewing contains questions related to this textbook.
Chapter 5 / Exercise 9
Principles of Information Systems
Reynolds/Stair
Expert Verified
Using software metrics and rigorous software testing are two measure for improvingsoftware quality and reliability.Software metrics are objective assessments of the system in the form of quantifiedmeasurements. Metrics allow an information systems department and end users to jointlymeasure the performance of a system and identify problems as they occur. Metrics mustbe carefully designed, formal, objective, and used consistently.Examples of softwaremetrics include:1.Number of transactions that can be processed in a specified unit of time2.Online response time3.Number of known bugs per hundred lines of program codeEarly, regular, and thorough testing will contribute significantly to system quality. Testingcan prove the correctness of work but also uncover errors that always exist in software.Testing can be accomplished through the use of:1.Walkthroughs: A review of a specification or design document by a small group ofpeople2.Coding walkthroughs: Once developers start writing software, these can be used toreview program code.3.Debugging: When errors are discovered, the source is found and eliminated
We have textbook solutions for you!
The document you are viewing contains questions related to this textbook.
Principles of Information Systems
The document you are viewing contains questions related to this textbook.
Chapter 5 / Exercise 9
Principles of Information Systems
Reynolds/Stair
Expert Verified
1-39

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture