This principle states that a given problem involves different kinds of concerns, which should be identified and separated to cope with complexity, and to achieve the required engineering quality factors such as robustness, adaptability, maintainability, and reusability. The principle can be applied in various ways and it is no exaggeration to state that the separation of concerns principle is an ubiquitous software engineering principle.
From the Aspect Oriented Software Architecture Design Portal . They define the term Concern as ,
Concern:A canonical solution abstraction that is relevant for a given problem.
More : http://trese.cs.utwente.nl/taosad/separation_of_concerns.htm
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment