Abstraction means that every class should only contain the data and functionality that it needs to serve its purpose – no more and no less. Abstraction takes different forms, but it is generally something that we want to strive for.
Coupling means there is a dependency between two or more classes. We want to minimize this for several reasons: It makes it difficult to reuse code and complicates testing and maintenance efforts. We cannot eliminate coupling completely because it is necessary for classes to collaborate. However, we should aim to minimize it whenever possible.
Cohesion is a measure of how closely the members of a class are related. A class should have one single well-defined purpose, and everything it contains should contribute to that one purpose.
Decomposition means that large, complex things should be divided into smaller, simpler things.
Modularization means that each component should have a specific, non-redundant purpose and well-defined interfaces. This is related to decomposition.
Encapsulation means that the details of what an entity is made of (its variables and functions) are bundled into a single unit, such as a class.
Information hiding means that the encapsulated details of a class can be hidden from external entities for the sake of simplicity as well as reliability. This is related to encapsulation.
Separation of interface and implementation means that the interface to a class should be separate from how it actually works behind the scenes. This is a specific type of information hiding.
Sufficiency means that a component contains enough of its essential features to be usable.
Completeness means that a component contains everything that it needs and nothing more.
Primitiveness means that the design should be based on patterns that are easy to implement.
Separation of concerns means that stakeholders can focus on just a few issues at a time rather than trying to grasp the entire system at once.
No comments:
Post a Comment