Riehle, D.; Zllighoven, H.: Understanding and Using Patterns in Software Development, Theory and Practice of Object Systems, Vol. 2(1), pp. 3-13.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....triggers and application event handling. The result is that neither the current capabilities of workflow languages nor insight into more complex requirements of business processes is advanced. We indicate requirements for workflow languages through workflow patterns [5 8, 48] As described in [36], a pattern is the abstraction from a concrete form which keeps recurring in specific nonarbitrary contexts . Gamma et al. 17] first catalogued systematically some 23 design patterns which describe the smallest recurring interactions in object oriented systems. The design patterns, as such, ....

D. Riehle and H. Zullighoven. Understanding and Using Patterns in Software Development. Theory and Practice of Object Systems, 2(1):3--13, 1996.

....and application event handling. The result is that neither the current capabilities of workflow languages nor insight into more complex requirements of business processes is advanced [7] We indicate requirements for workflow languages through workflow patterns [5 8, 52] As described in [40], a pattern is the abstraction from a concrete form which keeps recurring in specific nonarbitrary contexts . Gamma et al. 19] first catalogued systematically some 23 design patterns which describe the smallest recurring interactions in object oriented systems. The design patterns, as such, ....

D. Riehle and H. Zullighoven. Understanding and Using Patterns in Software Development. Theory and Practice of Object Systems, 2(1):3--13, 1996.

....most popular book in the field. The authors of the book are known as the Gang of Four. 2.3 What is a Design Pattern A general and widely accepted definition of a pattern is as follows: A pattern is the abstraction from a concrete form which keeps recurring in specific non arbitrary contexts. [6] A pattern is more than just a battle proven solution to a recurring problem. The problem occurs within a certain context, and in the presence of several competing concerns. The proposed solution involves some kind of structure, which balances these concerns in the manner most suitable for the ....

Dirk Riehle and Heinz Zullighoven. Understanding and using patterns in software development. Theory and Practice of Object Systems, 2(1), 1996.

....players. With the increasing maturityofwork ow technology, work ow language extensions, we feel, should be levered across the board, rather than slip into yet another technique proposals. Approach We indicate new requirements for work ow languages through work ow #### #####. As described in [15], a pattern is the abstraction from concrete form whichkeeps recurring in speci c non arbitrary contexts . Gamma et al. 8] rst catalogued systematically some 23 design patterns which describe the smallest recurring interactions in object oriented systems. The design patterns, as such, provided ....

D. Riehle and H. Zullighoven. Understanding and Using Patterns in Software Development. ###### ### ######## ## ###### #######, 2(1):3-13, 1996.

.... In the 1970s, Alexander developed a pattern language for architecture [1] the house building discipline, that is, not software or computer architecture For more on the history of patterns, see Appleton [3] For somewhat different definitions than the following, see Riehle and Zllighoven [39]. 2.1.1. Pattern Patterns are schematic, proven solutions to recurring problems. Basically, patterns are characterized by a name, a problem description, and a problem solution [36] A well known name allows us to concisely refer to a specific pattern. It is certainly easier to talk about the ....

....to problem categories (e.g. patterns for access control) Gamma et al. 16] and Mssenbck [36] on the other hand, subdivide patterns 3 dependent on their purpose 4 (e.g. such for object creation) and their scope (class vs. object) Different templates exist to document software patterns [5, 6, 16, 39]. Usually, the structure of a design pattern is depicted by a complete diagram while the implementation only shows the most important interfaces and some code snippets (possibly in pseudo code) The diagram is not necessarily a class diagram, even though the term design pattern is often implicitly ....

D. Riehle and H. Zllighoven. "Understanding and Using Patterns in Software Development". Theory and Practice of Object Systems, 2 (1): 3-13, 1996.

....that actions executed sequentially according to some global clock. Pattern : The codi cation of a section of an artifact or a process, with repetitive nature. Otherwise stated, ithe abstraction from a concrete form which keeps recurring in speci c non arbitrary contextsj [59]. Protocol : The speci cations of some means that allow a certain kind of interaction among a set of pieces of software. Otherwise stated, ithe set of rules that software components on dioeerent machines use to realize a given abstractionj [49] Re nement : ....

D. Riehle and H. Z#llighoven. Understanding and Using Patterns in Software Development. Theory and Practice of Object Systems (John Wiley), 2(1):313, April 1996.

....re use. One topic is the reuse of persons. As we have shown in previous sections it seems promising to reuse the experience of framework developers and software architects in application development projects. An important support on the level of micro structures are programming patterns (cf. Riehle, Zllighoven, 1996). Implementing software frameworks first of all means implementing software. But what makes the implementation more complicated is that software frameworks are at best partially operative by themselves. They have to be abstracted from and used with concrete applications. For application frameworks ....

D. Riehle, H. Zllighoven. Understanding and Using Patterns in Software Development. In: K. Lieberherr, R. Zicari (eds.): Theory and Practice of Object Systems, Special Issue Patterns. Guest Editor: S. Berczuk,Vol. 2, No.1, 1996, pp. 3-13.

No context found.

Riehle, D.; Zllighoven, H.: Understanding and Using Patterns in Software Development, Theory and Practice of Object Systems, Vol. 2(1), pp. 3-13.

No context found.

D. Riehle and H. Zullighoven. Understanding and using patterns in software development. Theory and Practice of Object Systems, 2(1):3--13, 1996.

No context found.

D. Riehle and H. Z ullighoven. Understanding and Using Patterns in Software Development. Theory and Practice of Object Systems, 2(1):3--13, 1996.

No context found.

Riehle, D.; Zllighoven, H.: Understanding and Using Patterns in Software Development, Theory and Practice of Object Systems, Vol. 2(1), pp. 3-13.

No context found.

D Riehle, H, Zullighoven, "Understanding and Using Patterns in Software Development", Theory and Practice of Object-Oriented Systems, 2, 1, 1996

No context found.

Riehle D. and Zllighoven H. Understanding and Using Patterns in Software Development. Theory and Practice of Object Systems 2, 1, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC