Object Oriented Software Engineering View all facts Glossary Help |
subject > criterion |
criterion comparison table |
Subject | write for | express | use in | has definition | have | measure in | convert into | modify | compute | is a subtopic of | is a synonym of | is a kind of | written in | write in |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
constraint | a logical statement that should evaluate to true | A small block of text in curly brackets embedded in a UML diagram. It is normally written in a formal language which can be interpreted by a computer | any side-effects | any data | a non-boolean result | 5.6 - More Advanced Features of Class Diagrams | criterion | braces (curly brackets) in a UML diagram | in any language supported by a given tool | |||||
effort | cost estimation | The amount of labour used in a task or project, expressed in person-months or person-days | person-months or person-days | the cost of a software project by multiplying it by the weighted average cost of employing a software engineer for a month (or a day). | 11.3 - Cost Estimation | development effort | criterion | |||||||
elapsed time | cost estimation | The difference in time from the start date to the end date of a software project | 11.3 - Cost Estimation | criterion | ||||||||||
principle | criterion | |||||||||||||
quality | An attribute of a product or process that, if improved, would better satisfy one or more of the stakeholders of that product or service | 1.5 - Software Quality | criterion | |||||||||||
standard | a particular audience | A document describing a body of well-respected information that engineers should conform to in order to ensure they are following best-practice, and will consistently produce good-quality products | 4.13 - Developing Requirements - References | document |
Next subject: critical path Up: subject Previous subject: cost estimate