Statestep
- Discovered from this article Wikipedia: State transition table
- Michael Breen article on Philips CDR project
- statestep home
- it's probably easiest to download the tool and work your way through the example
- FMPP
- install FMPP
CLASIFY
- http://mbreen.com/
- http://en.wikipedia.org/wiki/Formal_methods
- http://en.wikipedia.org/wiki/Use_case
- http://formalmethods.wikia.com/wiki/Formal_Methods_Wiki
- http://en.wikipedia.org/wiki/Table_%28information%29
Dear Nikos, Thank you for your email. Please find attached an evaluation license which is good for three months. This can be extended if you want to use Statestep in connection with any other project. If you were generating code from the model, I expect you would use the C code generation template which can be downloaded separately from the website. Should your customer decide to use Statestep for the project, the cost would probably be around EUR 900 for a one-year licence, or double that for a perpetual licence. I hope it proves suitable. Whether Statestep is used or not, I wish you success with your customer. If you have any questions, please let me know and I will do my best to help. Best regards, Michael Breen Hello Nikos, Thank you for telling me how you found the website. There is a manual on the documents page, if you want to try that, but it's probably easiest to download the tool and work your way through the example http://statestep.com/tutorial/Tutorial.html It starts off with a decision table example to show how the interface works, then moves on to finite state machines. I am not sure if it will prove suitable to your application. For a lift, at least some of the behaviour is likely to be modeled in some other way, e.g., you may have a state variable to model the doors (closed, opening, open, closing), but if there are multiple lifts you will probably have some algorithm to decide which one answers a call (is it the one closest, can a lift already moving stop at that floor, etc.) Statestep is most likely to give you an advantage where there are multiple finite state machines (each one a column in the tables) which need to be considered together, giving rise to complexity which is difficult to manage with other approaches. You'll probably just have to try to model the system to see if it is appropriate or not. Kind regards Michael --- Your licence key is attached in a .zip file. To install: unzip the file, start Statestep, click Info -> About -> Update Key. Then copy and paste the full contents of the file - or just click 'Read File'.
nikos.chalikias@lightfastelectronics.com-2012-09-22.licencekey.txt
Statestep general licence key. User: Nikos Chalikias <nikos.chalikias@lightfastelectronics.com> Use: Evaluation Expires:2012-09-22 MC0CFQCCmtiQ7lsGPwUPF5JJmoqTt4WY1AIUEE7Ld038X/FXYPD5mwsa9728HVM=
<cpp>
One thing to consider doing is to create a Statestep model separate from the specification you deliver to your customer
(actually, a Statestep model will normally be only part of your specification deliverables anyway; see the User Guide).
This might seem like more work than you want to do.
However, you should find that using Statestep allows you to substantially improve the quality of the specification that you do deliver.
/* Indeed, it may elicit so many questions that your customers start to wonder at your talent for thinking up scenarios that never occurred to them.
They will also better appreciate the effort involved in that "small" extra feature they wanted. */
So, even if the model is never delivered, creating it can still be a significant benefit to you as well as your customer.
</cpp>
