Your assessment requires you to submit a diagram of your final project’s navigation flow.
“That’s all well and good,” you might well say, “but what bloody kind of diagram?” Or possibly, “Why?”
I hope, at least, that you’ll ask that, since if you were to be asking a different question, this post would not be providing the answers.
Straight up, for this stage of the project, before development starts, you are essentially the client. Later you will become the consultant, but that’s after semester break. The purpose of diagrams for you as the client, is to clarify your ideas for the site you are about to build – to nail the user experience of the site and the information architecture of your project.
The classic way of starting that process is simply to draw a diagram of the different pages in your hypothetical site, e.g.:
That’s fine for assessment if you feel it helps you get a grip on what you’re doing. However, there are other options out there that I suspect are more useful for the projects at hand, and which are closer to real world best-practice. The key point is that in the real world design is ideally not a one-step process, but a cycle that repeats. Continue reading ‘a 30 second introduction to agile modelling.’