Development Methodology
Pixstar subscribes to the 80/20 rule: By identifying the few major ways of organizing a system solution that meets 80% of users' information needs, then we've reduced the chance that we'll overwhelm the user with too many choices; many of which are only rarely useful, and all of which have a significant maintenance overhead. Not trying to be all things to all users also means that system owners and managers have less to maintain, saving them time and money.
Defining the Information Architecture
There are two main approaches to defining information architecture. They are:
Top down information architecture
With top-down design, the information architect usually seeks to create a hierarchical organizational model where the user’s main questions are identified and addressed. This is usually accomplished by establishing a high level structure using components and detailed content relationships based on user requirements and business strategies.Content
To a large extent, content is the driving force of information architecture. Content inventories are used to determine where content resides, the owners of the content, the quantity and quality of the content and any relationships between the content. This aids in the identification of the system’s proposed content and in the determination of required functionality.
Components of Development
Content
To a large extent, content is the driving force of information architecture. Content inventories are used to determine where content resides, the owners of the content, the quantity and quality of the content and any relationships between the content. This aids in the identification of the system’s proposed content and in the determination of required functionality.Prototypes
Prototypes can be the initial method used for building the system or designing the information architecture. Prototypes can be as simple as an informal meeting using hand-drawn pictures of the system, or they can be as complex as developing fully interactive systems using sample production data. Using prototypes enables the users and other members of the project team to review the architecture or the system before either is finalized.
Storyboards
Story boards are another method for addressing the system model as well as the information architecture prior to the development phase. Story boards are pictorial representations depicting how a user would interact with a system or access a data repository to complete the required or repeated task. Storboards aid in making it possible for non-technical personnel to visualize the proposed system or architecture.
By following a systematic and comprehensive development documentation process, we can ensure deliverables are realistic and attainable within the resource constraints of our clients. Using this detailed documentation approach ensures there is a clear and concise understanding of the project scope thereby eliminating any costly surprises later.
Prototypes
Prototypes can be the initial method used for building the system or designing the information architecture. Prototypes can be as simple as an informal meeting using hand-drawn pictures of the system or they can be as complex as developing fully interactive systems using sample production data. Using prototypes enables the users and other members of the project team to review the architecture or the system before either is finalized.
Story Boards
Story boards are another method for addressing the system model as well as the information architecture prior to the development phase. Story boards are pictorial representations depicting how a user would interact with a system or access a data repository to complete the required or repeated task. Story boards aid in making it possible for non-technical personnel to visualize the proposed system or architecture.