Can patterns be expressed in [SOME PARTICULAR FORMALISM OR NOTATION]?
You are welcome to try, but bear in mind that a representation of a design or design rule in some formal notation is not a pattern if it omits descriptions of context, the problem(s) it solves, evidence for adequacy of the solution, construction or implementation guidelines, or relations with other patterns. • Why should I use patterns? For the same kinds of reasons that you should reuse good code: Benefitting from the knowledge and experience of other people who have put more effort into understanding contexts, forces, and solutions than you have done or want to do. Further, patterns can be more reusable than code, since they can be adapted so that you can build software to address particular special circumstances that cause you to be unable to reuse an existing component. Patterns also give developers common sets of names and concepts for dealing with common development problems, thus enhancing communication. • Wouldn’t it be nice to have some patterns-based CASE tools? Maybe, but pa
