Posts Tagged ‘information architect’

Why creating a flowchart?

This article is part of the series Information Architecture for wireframes using Justinmind Prototyper

A Navigation map of you site will help you understand the pathways users take, helping you create shortcuts, cutting off unnecessary pages or steps, reducing bounce rates and increasing usability. It is very important to create the flowcharts before designing the wireframes.

Collaborative work

With Justinmind Prototyper, your navigation map can be commented and all requirements can be linked to specific pages with drag and drop, so, for example, the Project Manager can write that page 2 needs a login, the Information Architect can describe what kind of content goes on the library page, and the designers can change sizes or typography, and annotate that on the project. All comments will be saved and organized in a database, which can be filtered according to many criteria.

Advantages of interface-flow diagrams

On AgileModeling.com, Scott W. Amber says “User interface-flow diagrams are typically used for one of two purposes. First, they are used to model the interactions that users have with your software, as defined in a single use case. For example, a use case can refer to several screens and provides insight into how they are used. Based on this information, you can develop a user interface-flow diagram that reflects the behavioral view of the single use case. Second, (…) they enable you to gain a high-level overview of the user interface for your application. This overview is effectively the combination of all the behavioral views derived from your use cases, the result being called the architectural view of your user interface (Constantine and Lockwood 1999). I prefer to take the high-level overview approach, also referred to as the architectural approach, because it enables me to understand the complete user interface for a system.” http://www.agilemodeling.com/artifacts/uiFlowDiagram.htm

He mentions several sources and articles related to the subjects on his site, so it’s worth a visit.

Tip: KISS – keep it simple, stupid

Flowcharts don’t necessarily need all information you’ll have on your website: just what’s crucial. You’ll have more information on your homepage than described, but obviously, you just need the things you think your users will need less. For more info about it, please read Steve Krug’s website (http://www.sensible.com/)

Justinmind Prototyper is the simulation and prototyping tool for designing high fidelity wireframes and mockups. For more information, subscribe to Justinmind’s blog or drop us a line on twitter.


Article from articlesbase.com

Presented as a small, nearly inconsequential feature on the Gibson Lifestyle newsletter is an article featuring video of the Gibson Robot tuning system. Not so newsworthy. . . until you realize that the system is installed on an EJ160E John Lennon ROund Shoulder acoustic.
Video Rating: 4 / 5