Functional software architecture: Difference between revisions

Revision as of 22:54, 6 January 2007

Revision as of 16:20, 14 March 2007

Line 71:

===Petri Nets===

[[Petri NetsNet]]s are known tools to model manufacturing systems [9]. They are highly expressive and provide good formalisms for the modelling of [[concurrent systemssystem]]s. The most advantageous properties are that of simple representation of states, concurrent system transitions and capabilities to model the duration of transitions.

Petri Nets therefore can be used to model certain business processes with corresponding state and transitions or activities with in and outputs. Moreover, Petri Nets can be used to model different software systems and transitions between these systems. In this way programmers use it as a schematic coding reference.

In recent years a number of attempts have shown that Petri Nets can contribute to the development of business process integration. One of these is the Model Blue methodology, which is developed by [[IBM]] Chinese Research Laboratory and outlines the importance of model driven business integration as an emerging approach for building integrated platforms [10]. A mapping between their Model Blue business view and an equivalent Petri Net is also shown, which indicates that their research closes the gab between business and IT. However, instead of Petri Nets they rather use their own Model Blue IT view, which can be derived from their business view through a transformation engine.

So, pros and cons in using Petri Nets as a modelling tool for the implementation of integrated IT systems are present. Maybe it should be combined with other methods and techniques to deliver positive results? For instance, various classes of Petri Nets can be used in combination with IDEF or CIMOSA and even UML [11]. Mostly to exercise alternative system design. However, a major drawback of Petri Nets, the inability to provide multiple views of entire enterprise systems, remains.

===Unified Modeling Language===