Object Oriented Software Engineering   View all facts   Glossary   Help

subject > measurement

measurement
subject			fact

measurement	is a subtopic of 1.5 - Software Quality
	is a kind of subject

Kinds of measurement :

• acceptability (7 facts) - The extent to which customers and users like a system
• availability (5 facts) - A quality that measures the amount of time that a system is running and able to provide services to its users
• cohesion (7 kinds, 5 facts) - A measure of the extent to which related aspects of a system are kept together in the same module, and unrelated aspects are kept out
• coupling (12 kinds, 5 facts) - A measure of the extent to which interdependencies exist between software modules
• coverage (3 facts) - A measure of the percentage of paths, statements or branches taken by a set of tests
• earned value (4 facts) (budgeted cost of work performed) - The amount of work completed, measured according to the budgeted effort that the work was supposed to consume
• efficiency (1 kind, 7 facts) - The extent to which a product or process can operate using the fewest possible resources
• efficiency of use (7 facts) - A measure of how fast an expert user can do their work using the system
• error handling (6 facts)
• error^3 (4 facts) - An inaccuracy in a numerical computation
• learnability (10 facts) - The speed with which a new user can become proficient with the system
• learning curve (4 facts) - A curve on a diagram that plots the time spent learning on one axis, and the amount of functionality learned on the other axis
• maintainability (1 kind, 10 facts) - An important quality of software that measures the extent to which the software can be modified at the lowest possible cost
• metric (3 facts) - A scale on which a software product or process may be measured
• modularity (5 facts) - The extent to which software is divided into components, called modules, which have high internal cohesion, low coupling between each other, and simple interfaces
• number of bugs (3 facts)
• number of defects found when inspecting a product (2 facts)
• number of failures encountered by users (2 facts)
• number of failures found when testing a product (2 facts)
• number of questions posed by users to the help desk (2 facts)
• number of use cases (1 kind, 3 facts)
• objective (5 facts) - A measurable value you wish to attain
• percentage of code that is reused (2 facts)
• person-month (4 facts) - A measure of effort. One person month is the amount of work done by one person in one month if they are working full time
• recovery from failure (5 facts)
• reliability (2 kinds, 13 facts) - An important quality of software that measures the frequency of failures, as encountered by testers and end-users
• requirement stability (3 facts) - A measure of the extent to which requirements are likely to change
• resource usage (6 facts)
• response time (12 facts) - The time that elapses from when a user issues a command to when the system provides enough results so the user can continue his or her work
• reusability (1 kind, 6 facts) - A quality that measures of the extent to which a product or process can be used in different contexts from which it was originally designed
• schedule^2 (3 facts) - The total elapsed time of a project
• severity level (3 facts) - A number given to a failure, defect or test case, indicating the amount of impact it has on the user or customer
• test case pass target (5 facts) - The desired percentage of test cases that will pass testing
• throughput (4 facts)
• traceability (5 facts) - The ability to determine the information that led to a decision being made
• usefulness (2 kinds, 7 facts) - The extent to which a system can be used to perform a task; combines usability and utility^2