![]() |
subject > criterion > principle |
![]() ![]() | ||||||
principle comparison table |
Subject | is an instance of | is a kind of | state | found at | is a subtopic of | has definition |
---|---|---|---|---|---|---|
approach to identifying generalizations | principle | 5.8 - The Process Of Developing Class Diagrams | ||||
code layout principle | principle | Sun | Programming Style Guidelines | |||
cost estimation principle | principle | 11.3 - Cost Estimation | ||||
design principle | principle | 9.2 - Principles Leading to Good Design | ||||
ethical principle of usability evaluation | principle | 7.6 - Evaluating User Interfaces | ||||
IEEE/ACM code of ethics | principle | Software engineers shall:
| 1.3 - Software Engineering as a Branch of the Engineering Profession | |||
principle behind frameworks | principle | that applications that do different but related things tend to have similar designs - in particular, the patterns of interactions among the components tend to be very similar | 3.3 - Frameworks: Reusable Subsystems | |||
requirements principle | principle | separate the 'what' from the 'how'. The 'what' refers to the requirements - what is needed to solve the problem. The 'how' refers to how the solution will be designed and implemented. | 1.7 - Activities Common to Software Projects | |||
rule | principle | A principle that should almost always be applied | ||||
usability principle | principle | 7.5 - Usability Principles |
Next criterion: quality Up: criterion Previous criterion: elapsed time