Entradas

Imagen
Risk Analysis Topic: Hi, this is the last topic we learn at software engineering course. And one of the topics I liked more is the cut set of risk tree. Because is basically a tree that connect nodes by AND and OR. Basically at least for is something easy to remember and functional for explaining risk to the domain holder. An example of this can be this.
Imagen
The Software Architecture Design topic: Is more about how to implement in a diagram and obviously in RSL how a particular entity of the domain works in each phase. In my case I have a fixed topic thought-out the course and was financial system. What I basically did was a diagram about how the backend software system of transactions works in Bank. At first I thought Time table was something important for any diagram of software but then my professor clarified this to me today on the assignment. So the correct way of doing that is to change time table with Transaction Handle or Operator.
Rough-Sketch Requirements Topic: This topic of this week is a little bit complicated because is a topic that involucres a lot of material in one topic but basically rough sketch requirements is about a paper describing any requirements type machine, domain, etc. But in this case we needed to apply everything we learn from the few weeks ago. And actually make a better requirement than before.
Imagen
State Charts Topic: This week we are talking about state chart which for me is the most fun, logical, awesome diagram of all the ones we were talking. Here I show you one I made for an assignment about a watch: As you may see here this a state chart and I don't know you but for me is so easy to understand and clear. At first when I read this on the book I already could understand what it can say. But basically is like the box that is inside a giant box is part of him as an entity and the arrow points to the transition or the event that need to happen for that state to change. But seriously if I need to take a diagram between this or the other this one will be my choice.
Imagen
The Sequence Chart: This week we are talking about sequence chart which is kind of awesome because is about operations in time. I will show you a diagram so you could understand in image what I'm saying: As you may see basically is like a time-line and between two entities a, b, and c there can be operation that need each other. But you need to be careful because time is important in this diagram and you can go back.
Imagen
Petri Nets Topic: Well these week we continue with another type of diagram which basically is the same as the other one we discussed before but with other form of making the states and the transitions. As you may see here the difference here is that instead of the arrow having the name of the transition, here you need to manage keys in a circle and manage them well across the system. also here a state is represented by a rectangle. Also this kind of diagram I like it better than doing RSL haha.
Imagen
Diagrams Automata and Machine topic: This topic that we are discussing now is more about states and how transitions. And obviously the best way to implement this is by creating a good diagram that can make company to all the other files needed to prepare a good domain info. This is how those diagrams are. What I like the most about these is that is easy to understand, basically the circle is the state while the arrow show the transition that is caused by that event. But obviously thats not formalized so you need to formalize that by using RSL sadly.