Software Engineering:- HOW TO CHARACTERISE A GOOD SOFTWARE DESIGN?

HOW TO CHARACTERISE A GOOD SOFTWARE DESIGN?
Coming up with an accurate characterisation of a good software design that would hold across diverse problem domains is certainly not easy. In fact, the definition of a “good” software design can vary depending on the exact application being designed. For example, “memory size used up by a program” may be an important issue to Characterise a good solution for embedded software development—since embedded applications are often required to work under severely limited memory sizes due to cost, space, or power consumption considerations. For embedded applications, factors such as design comprehensibility may take a back seat while judging the goodness of design. Thus for embedded applications, one may sacrifice design comprehensibility to achieve code compactness. Similarly, it is not usually true that a criterion that is crucial for some application, needs to be almost completely ignored for another application. It is therefore clear that the criteria used to judge a design solution can vary widely across different types of applications. Not only do the criteria used to judge a design solution depend on the exact application being designed, but to make the matter worse, there is no general agreement among software engineers and researchers on the exact criteria to use for judging a design even for a specific category of application. However, most researchers and software engineers agree on a few desirable characteristics that every good software design for general applications must possess. These characteristics are listed below:
Correctness: A good design should first of all be correct. That is, it should correctly implement all the functionalities of the system.
Understandability: A good design should be easily understandable. Unless a design solution is easily understandable, it would be difficult to implement and maintain it.
Efficiency:  A good design solution should adequately address resource, time, and cost optnnsatkm issues.
Maintainability: A good design should be easy to change. This is an important rB9tGrement. Since change requests usually keep coming from the customer even after release