Defining How a User Moves Through the System
Once you’ve defined the Use Cases for your software project, you can start to identify how will users flow through the system. That is what page or pages (or screen or screens if you prefer) will the user need to go through in order to get to where they need to go to do what they need to do.
A good product depends on your carefully building this out, so you can make it as easy as possible for the user. You don’t want them to go through 100 steps to do something easy, but you want it to be as clean as possible.
Consider something like checking out at Amazon. There’s a lot going on, but they try to make it as easy as possible for you to give them your money, including a “Buy Now” button if that is all you are going to be buying. Often with many systems, we try to through too much information at the end user so we can put it all on one screen, when in reality, a couple of screens might be best.
When thinking about what to show them, you might consider looking at what type of device will they be using. A large desktop is different than a small laptop, which is different yet than a mobile device.
One Comment