For most software projects, the design needs to describe a plan for architecture and internal interface so that the software development team is well-organized and working together.  The goal is to build a software product that will survive past its first major change.

Too often, design time is spent negotiating things that should have been resolved when capturing requirements. (See Requirements capture for more discussion.)

This is the best time to be sure you've captured the state transitions of your products (and its component pieces.) 

We can help you design your software or review your existing design for problems. One of our experts is an especially useful resource for developing a software design or reviewing your existing design. He is familiar with UML techniques and understands how critical an accurate state transition / statechart design is to real-time systems.