Catalysis software design method
Encyclopedia
Catalysis is a method for the specification and design of component-based computer systems originally developed by Desmond D’Souza and Alan Cameron Wills in their 1999 book. It shows how to make precise abstractions, and emphasizes the formal specification of use cases using pre- and postconditions and ‘guarantees’ clauses. It also places stress on the specification of collaboration protocols so that kits of components can interact in a coherent ‘pluggable’ fashion. This removes much of the need to build translation or ‘mapping’ code. Catalysis therefore enhances the Unified Modelling Language (UML) with a definite method, showing how the various UML diagrams relate to each other and offering many design heuristics and process and design pattern
Design pattern
A design pattern in architecture and computer science is a formal way of documenting a solution to a design problem in a particular field of expertise. The idea was introduced by the architect Christopher Alexander in the field of architecture and has been adapted for various other disciplines,...

s. Catalysis builds on the Syntropy
Syntropy
Syntropy is a second-generation object-oriented analysis and software design method developed at Object Designers Limited in the UK during the early 1990s. The goal in developing Syntropy was to provide a set of modelling techniques that would allow precise specification and would keep separate...

 method and key ideas from both influenced the development of UML 2.0.

More recently, building on the work of D’Souza, Wills and that of John Cheesman and John Daniels, Derek Andrews of consultancy Trireme International has developed Catalysis II, which extends Catalysis to address the key issues of Service Oriented Architecture (SOA). Also building on the same foundation, Ian Graham developed Catalysis Conversation Analysis, a method of business process modelling with its roots in Semiotics
Semiotics
Semiotics, also called semiotic studies or semiology, is the study of signs and sign processes , indication, designation, likeness, analogy, metaphor, symbolism, signification, and communication...

 and the idea of a use case
Use case
In software engineering and systems engineering, a use case is a description of steps or actions between a user and a software system which leads the user towards something useful...

(cf. Graham, 2008).

External links

The source of this article is wikipedia, the free encyclopedia.  The text of this article is licensed under the GFDL.
 
x
OK