Statechart and Activity Modeling
Click Submit to View Solution
Consider a bulb with a push down switch. The bulb initially remains off. When the switch is pushed down, the bulb is on. Again when the switch is pushed up, the bulb turns off. The lifecycle of the bulb continues in this way until it gets damaged.
Limitations: A complex system often has sub-states, which is not covered as a part of this lab. The following interface only let you represent simple states. Please check out the references section to know more about them.
Let us consider the development activities of SE Virtual Labs. The process begins by checking out the code from Subversion repository. Necessary modifications are then made to the checked out code (local copy). Once the developer is done with his changes, the application has to be tested to verify whether the new functionality are working fine. This test has to be performed with two of the more popular web browsers: Firefox and Internet Explorer, to support cross-browser accessibility. If testing fails in at least one of the two browser, developer goes back to his code, and fixes it. Only when all the browsers pass the test, a patch is generated from the local copy, and applied to the production code. The local copy is then committed resulting in update of the SVN repository. Note that, if the local copy is committed before generating a patch file, then local changes would get registered, and one won't be further able to generate the patch file. Note: For further clarification, at any point of time there exists three versions of the source code: Production copy, local copy, and copy in SVN repository.
Limitations: The objective of this system is to provide knowledge on the fundamental aspects of activity diagrams. As such, it lacks certain features as listed below, which a dedicated UML Diagram editor should have.