http://yunus.hacettepe.edu.tr/~tonta/courses/fall2010/bby607/bby607dersamac2010.htm

Hacettepe University Department of Information Management

BBY 607 Information Architecture (Fall 2010) Yaşar Tonta

Class meets: Fridays 09:00-12:00 (Ofis)

Instructor: Yaşar Tonta (e-mail: tonta@hacettepe.edu.tr; phone: 297 82 04) 

Web site: http://yunus.hacettepe.edu.tr/~tonta/courses/fall2010/bby607/bby607dersamac2010.htm

First Assignment

SOCIO-TECHNICAL ANALYSIS AND DESIGN

This assignment consists of the following components.

  1. Identifying objectives
    Obtain information about the customer, his/her business to find out the tasks and functions that will be facilitated by the web site and to define the objectives of the web site. Describe the web site’s objective clearly. Mission and objectives of the web site need to be re-evaluated continuously. The team should think of web site’s objective in every step of the design process.
  2. Describing customer’s vision
    What is the concept or vision that the customer has in mind with regards to the look and feel of the web site? If there are more than one customer, there may be more than one vision (and they sometimes conflict with one another). If this is the case, the vision needs to be built in such a awy that it contains points of view of each customer and customers should be convinced.
  3. Describing users
    Description of the user group or groups that will really use the web site. This step is important because we should decide as to what users want to do. For example, if users visit the site for daily news and events, then such information should be readily accessible and should not be hidden in deep down. Usually there is more than one user group. For example, a commercial site can be used by both customers and staff. Interests of two groups may complement each other (e.g., both groups may be interested in product information). But the interests of different groups are usually different.
  4. Creating an inventory of the content
    Identifying what type of information should be included in the web site depending on its objective and target user group.  Content inventory is usually created for practical reasons.  If it is not possible to create the needed content –for example, providing summary of daily transactions-, then this type of content should not be included in the inventory.  Content inventory is usually a “wish list” of all the customers.
  5. Identifying the server platform
    Serious decisions should be made in this stage regarding the technology that will be used to provide content (such as the selection of service provider or server operating system and software).  These decisions are based in part on the type of content. For example, database support is needed for fast-changging content, or a streaming media server is needed for visual content. Selection of technology depends on the budget. Even if the information architect is involved in the preparation of the budget, s/he cannot solely decide how much Money should be allocated to a project.  Information architect should change the content inventory according to budget.
  6. Creating site maps
    Site map determines how it is that potential users visit the site.  What is important in this is that it should be decided which resources should be offered through the main page or secondary pages. There are several styles of organizing sites.  Selection depends on the site’s objective and user group(s). For instance, a web site focusing on group discussion should provide several fast conncetions. Information providing sites should present this information from the main page and in the center.  (Site map design nakes use of usability elements as well.  Each site map should be tested on real users in order to identify intuitional navigation streams.)
  7. Creating content maps
    Content map is a description of the content of the web site as it appears to a database.  Content maps should classify different types of data and determine relationships between them.  Content maps are sent to database specialist for programming.  Content maps may contain links that are not obvious in site maps.  For instance, site maps may contain paths that point to personnel and products.  Content maps, on the other hand, show the relationships between personnel and products (who is responsible for what product).  Content maps also make sure that importent content is not included. If an item in the content inventory cannot be classified under a content map classififcation, then the existing content map (and probbably site map) should be reviewed to correct this.
  8. Designing page layouts
    Once different types of content are described, an information architect focuses on how content will be displayed on the web page.  In addition to usability elements, the quality of content and user group will also be taken into account at this stage.  Page layouts may contain drawing sketches and block diagrams.  These layouts are the first step of presenting information in such a way that it is easy to read and pleases the eyes.
  9. Designing constructive processes
    At this point, the web site is ready to be transferred to programmers, authors and artists.  All three groups should work within the confines of the plan. The information architect should create a series of design parameters for each group.  Authors will get instructions on not only what they are to write about but also which style they are to use and the length and subdivisions of the text or even which font they are to use in the final version. Graphic designers should be provided a series of objects –banner, logo, and so on- along with customer’s choices, information architect’s vision and user requiremements. HTML programmers and other programmers should know the level of functionality desired fort he web site. For example, if an information architect expects the web site to be resized according to different browsers, this should be documented. A production plan displaying the targets and fullfilment dates should be prepared and the communication among three groups should be facilitated. (To keep the design process on track, continuous tests should be carried out and the customer should see the results.)

 

Note: The description of the assignment belongs to Stephen Downes and it was adapted from Mary E. Brown’s ILS 599 Information Architecture course syllabus.. http://www.southernct.edu/~brownm/599ia_Sp2006_syllabus.html]

Yaşar Tonta

tonta@hacettepe.edu.tr

Last updated: 30 September 2010