Modeling execution architecture of software system using colored Petri nets

We present an application of Colored Petri Nets for modeling qf software architecture. Our work demonstrates how to use architectural modeling to control properties of industrial scale products and product families. The new software architecture of a mobile phone family is modeled by Colored Petri Nets and analyzed using the Design/CPN tool. The model describes the execution architecture and allows us to analyze both the time and space performance of the software system. Our experience shows that a special purpose model can be constructed,for large systems also and this model predicts system properties accurately enough to be useful. The insight this gave us into the internal operation of the software system together with the estimates of its per$n-mance helped guide us through the early phases of architectural design. We continue to and expect it to be a very valuable different product,family members. maintain the model tool in configuring

[1]  Nenad Medvidovic,et al.  Integrating architecture description languages with a standard design method , 1998, Proceedings of the 20th International Conference on Software Engineering.

[2]  Kurt Jensen,et al.  Coloured Petri nets (2nd ed.): basic concepts, analysis methods and practical use: volume 1 , 1996 .

[3]  Alexander Ran,et al.  Selected issues in architecture of software intensive products , 1996, ISAW '96.

[4]  Lawrence C. Paulson,et al.  ML for the working programmer (2. ed.) , 1996 .

[5]  Jeff Magee,et al.  Analysing dynamic change in software architectures: a case study , 1998, Proceedings. Fourth International Conference on Configurable Distributed Systems (Cat. No.98EX159).

[6]  E. Rechtin,et al.  The art of systems architecting , 1996, IEEE Spectrum.

[7]  Nenad Medvidovic,et al.  Domains of Concern in Software Architectures and Architecture Description Languages , 1997, DSL.

[8]  Lars Michael Kristensen,et al.  Design/CPN Occurrence Graph Manual , 1996 .

[9]  Mary Shaw,et al.  Truth vs. knowledge: the difference between what a component does and what we know it does , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[10]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[11]  Philippe Kruchten,et al.  Architecture blueprints—the “4+1” view model of software architecture , 1995, TRI-Ada '95.

[12]  Hans-Erik Eriksson,et al.  UML toolkit , 1997 .