SWEN-261 Lecture Notes - Lecture 8: State Diagram, User Story, Unified Modeling Language
29 Sep 2017
School
Department
Course
Professor
Document Summary
The solution might have 2-5 states, and not much more. A finite-state machine is a notational mechanism for capturing this state-based behavior. If you don"t recognize that there is a state behavior, it might evolve implicitly which could cause each team member to have different models of the same behavior. A statechart can define behavior in multiple areas of your application. If your code contains logical combinations to select behaviors, this indicates that your software has various states. You typically want a deterministic state machine to define behavior of your software systems. Must be true in order for the transition to be triggered. When the event is triggered, an actionlist is executed. You can have multiple transitions coming in and out of a state. A transition executes near instantaneuosly relative to the time spent in a state. A transition can also return to the state it was in. For our project, we will always have an event for our transitions.
