State transition means change of application state. like in ATM when customer inserts the card, ATM change the state from CARD INSERT to PIN Entry State or Error State. like there are so many states in ATM for transaction.
No Peter, this is not an interview question.
I came across this term while reading a book. I am testing for long time, but i didn't came across this term.
That is the reason i have asked this question.
As some members already pointed out, State Transition Diagrams represents the transition from one state to another (of an application or machine) given an input.
I have mostly used state diagrams for one of my Advanced Logic Design classes in school.
Other than that I have seen development teams using State diagrams during design planning and implementations.
In a previous existance, the company i worked for used Yourdon Structured Methodology (is Ed Yourdon still going??) for awhile, which included state transition diagrams. We used them to attempt to design out potential deadlocks in multithreaded code. Design docs riddled with STDs did not always make pleasent reading [img]images/icons/wink.gif[/img]
YSM was a bit better than SSADM which we had been using previously, but still caused a huge amount of time to be wasted with plastic stencils and A0 sheets.