Web Site Design Articles

 

Object Orientation: Skills for Information Architects

In Information Architecture - A New Opportunity, which appeared in the 12/21/00 WebReference newsletter, Angshuman Das’ discussed the ongoing debate between user-centered, simple design vs. media-rich, cinematic Web sites. Das suggested designers capitalize on becoming Information Architects by combining both methods. "With some skill and talent we can expect a good salary and respect," said Das.

That got my attention! Information Architecture, here I come! Well okay, let’s back up a minute; the article did mention we need talent and skills. Talent can be natural or an acquired ability, so working on the skills part while trusting the talent part seems the best solution.

Remember, Information Architects remove the mystery of technology for users, making the technology a byproduct of the total experience rather than a monster to frustrate, fight and possibly overcome. Information Architects master communication with users using various methods. They visualize connections between patterns, connecting the dots and thereby develop possible solutions not seen by the average developer.

We've all seen those high tech Flash sites, digital movies, panoramas and talking (audio) Web sites. We've all seen technology over done and with little purpose other than demonstration, leaving us users wondering, "why did I have to wait for this?"

So, let’s morph our design skills into that of an Information Architect by using the programming technique of object orientation. Object Orientation requires:

• visualizing
  the project as moving and breathing with flexible plans and goals, recognizing and expecting changes, working as a team toward solutions that complement the desired outcome of the entire project, realizing that the "right" way might not always be the workable solution;
  
  
• communicating
  an understanding of the design to the rest of the team, selecting several methods (textual, visual, diagrammatical) for relaying the design concept to team members, making these explanations chock full of information and explanations, helping each team member conceptualize the more troublesome parts of the project;
  
  
• morphing
  problems into workable solutions, expecting and dealing with problems by working out more complicated, risky parts of the project first, understanding that the team as a whole should work for the success of the entire project, not the bits and pieces for which each individual may be responsible;
  
  
• defining
  the training and knowledge needed for project members to communicate effectively to the end user, obtaining user feedback at each step in the process, sharing this information with all team members with the goal of better understanding why the eventual solution best solves each identified problem and making sure to benchmark each user test phase.

Object Orientation also requires the modularization of information. Information, when processed through an object-oriented filter, is usually broken up into objects, attributes and behavior.

Discovering the Project Objects

Following the object orientation model, a project should be broken up into stand-alone modules. Laying out the entire project as a roadmap and then dividing into its individual, bite-sized pieces, or objects, is usually a good way to start. Ensuring project team members see the relationship between their parts of the entire project is of paramount importance.

Detecting the more complicated, problematic and interrelated parts of the project is the hallmark of a skilled Information Architect. Accomplishing these tasks comes first, since their outcome affects the relationships of other, less complicated, but dependent tasks. Should the entire project prove unviable, this method allows for earlier failure detection. Hence, in the case of failure, less money will have been wasted.

Understanding Attributes and Behavior

Objects are "things," things have qualities, and thus need a descriptive coating. Attributes perform this function by defining the state of an object (open, closed, etc.); think of attributes as adjectives and objects as nouns. What part of speech is behavior analogous to?

Behavior defines how an object reacts in a given set of circumstances, making behavior the operations of the design. Below, example 1 explains the use of objects, attributes and behavior.

Example 1: Let’s use a database as our object. We desire a secure database so security becomes the object’s attribute. The object’s behavior allows logged-in users to query the database.

Example 2 demonstrates the use of interesting objects with relevant attributes and behavior.

Example 2: In this second example, let the objects be graphic buttons. We want the buttons’ attribute, color, to give the user a reference as to where they are and what they might find if they click the button. We assign movement (JavaScript rollovers) as the behavior. The end user now receives additional information, a color, when moving the curser over the button.

After understanding the principles, practice applying these skills with more complicated media-rich, cinematic effects. But remember the Flash, audio and other potentially enhancing effects without any relevancy? Sites using irrelevant objects with undiscovered attributes often frustrate users as they wait through longer downloads; worse yet the experience may confuse the user as they attempt to discover the purpose of your site. Prevent these mistakes in your Web development by remembering that interesting objects require relevancy and a user- enhanced experience.

Conclusion

In this article, I concentrated on object orientation of the Web site design process. Many of you probably recognize that software development also uses some of these techniques. Web site design shares commonalities with software development in the organization, planning and execution phases. Both rely on clear methods of communication to both team members and eventually, users.

Throughout this essay I've applied the same principled processes used in software development to Web site development while, at the same time, developing our Information Architecture skills. The Object Orientation process focuses on working out the more complicated tasks first. It requires that we look for and recognize patterns, providing us more opportunities for developing solutions.

Through object orientation, we keep team members informed and linked to the outcome of a project. Information and communication flow, encouraging team members to rely on each member’s strengths while compensating for weaknesses. When a whole project is laid out graphically, dissected, and broken into its respective parts, object orientation encourages team participation throughout the entire project while simultaneously facilitating synergy and continued team problem solving. Best yet, the end user becomes the team’s focus.

About the author: Peggie Brown is president of Brown Holdings LLC Group. Brown Holdings LLC Group provides sites such as KatsueyDesignWorks, a custom site design and development company, ContentXperts and Katsuey’s Legal Gateway, a free legal research site.

This article is the copyrighted property of KatsueyDesignWorks. No reprints are allowed without expressed permission.

If you need a great business web site, KatsueyDesignWorks is the place to start - and end - your search for a web site designer.

We provide:

• Custom Designs
• Custom Graphics
• CSS
• Search Ready
• Great Service
• Economical Prices
• Modern Browser Compliant