Software Engineering: Petri Nets

-

This'll be a sort of abridged summary of the topic, any more information you might need, I recommend you try the book (name in bottom of the post).
The circles are states in the domain.
With the arrows pointing to where the process is going
And the thin rectangles the transitions between states 
Petri Nets are basically a diagram to help us visualize the process and how it flows in a domain.
In this chapter we talk about three types of representations:

  1. Condition Event Nets (CEN)
  2. Petri Nets (PTN)
  3. Colored Petri Nets (CPN)
Condition Event Nets are the most basic type of Petri nets. A CEN consists of conditions (states), events (transitions) and links (arrows) from conditions to events and from events to conditions. Syntactically conditions are represented as circles, while events are represented as oblong, i.e., "thin",
rectangles.



Petri Nets are pretty much the same as CENs but conditions are now called places and in those places are labels with a positive integer called the capacity. This indicates the maximum number of
tokens that may be assigned to that place. The capacity may be omitted, which is interpreted as unlimited capacity. The capacity tells us what is the required to transition between places.



 Colored Petri Nets are an extension of PTNs: A type-value system for tokens is now introduced. The term colored refers to the fact that tokens are now distinguishable in that they have a value, called their color, which is of a particular type, called their color set. A color set may define both simple and composite values.



Book used for this topic: Dines Bjørner, Software Engineering, Vol 2, Springer, 2006. (short SE-V2)

Comments

Post a Comment

Popular posts from this blog

JavaFX Snake Game (WIP)

-
Image
It's been a while, busy with classes. Decided to work on another little side project. Using what I've learned so far in my Java course, I wanted to test my JavaFX knowledge with this little game. Using GridPanes, Squares and Timeline Loops, I'm almost 85% done with the game, Snake eats and grows. Just need to add the lose conditions and that should do it. The game for now starts automatically. (So I need to add I title screen/pause screen) Link to the project on GitHub.
Read more

Software Engineering: Documents

-
Image
This'll be a sort of abridged summary of the topic, any more information you might need, I recommend you try the book (name in bottom of the post). In the professional realm documentation is everything (according to this book, it's probably true), lack thereof can make your job a living nightmare every time there's an update. Even if tedious proper documentation can go a long way. In Dines' Book there are 3 main types of documentation, each different but of equal importance. Informative Documentation Descriptive Documentation Analysis Documentation It can get a bit tricky trying to differentiate them so let me try  to explain it. Informative Documents are basically documents where you talk about the domain and everything involving it (like partners, place, the scope, etc) without necessarily going into detail about the technical stuff involved in your domain. In an informative document you can find the following: Descriptive Documents  
Read more

Where have I been?

-
It's been quite a while hasn't it? Where to begin, well shortly after my last update I was quickly hired by Hewlett-Packard Enterprise for almost two years now. How time sure flies doesn't it. I work there as a System's Software Engineer full time, working on diagnostic software for their many line of servers. It has been a great experience, all that I learnt and continue to learn is amazing. This is mostly the reason why this hasn't been updated since. But I started to miss these updates and hopefully soon I'll continue working on these. Sharing cool tips and tricks I've learned in the Industry or in my spare time. Got plenty of time, considering everything going on with this whole COVID-19 nonsense.Stay indoors fellas and wash your hands please!
Read more