IT Project Management Information System and Information Architecture

www.themegallery.com

LOGO

IT Project ManagementInformation System and Information Architecture

Prof. Dr. Ir. Riri Fitri Sari, MM, MSc

Electrical Engineering Dept.University of Indonesia

1 Mei 2012

Agenda

- Information System (http://www.slideshare.net/missishot/information-systems-intro

- Information Architecture

Organizations and Their Responses Strategic systems Continuous improvement efforts Business Process Reengineering (BPR) Business alliances Electronic commerce

What Is an Information System?Information systems (IS) collect, process, store, analyze, and disseminate information for a specific purpose.

SAP R3 user interface

Enterprise SOA is a blueprint for an adaptable, flexible, and open IT architecture for developing services-based, enterprise-scale business solutions

SOAs build applications out of software services

What is information architecture?Intuitive navigation doesn’t happen by chance

The problem: finding is the new doingThe shear wealth of functionality and information has become the new problem

http://www.slideshare.net/hapy/information-architecture-intro

information architecture isThe science of expressing a model or concept forinformationUsed for activities that require expressions ofcomplex systemsConsists of:

Structural design of shared informationenvironmentsOrganizing and labelling information to supportusability and find ability

From Wikipedia

Simpler partial definition“the art and science of organising and labelling websites,

intranets, online communities and software to support usability and find ability.”

Structuring content and systems so people can find information

It involves designing:Content groupingNavigationLabellingtaggingTaxonomies, thesauri, indexes, metadata

WHY ??An effective information architecture

enables people to step logically through a system confident they are getting closer to the information they require.

Most people only notice information architecture when it is poor and stops them from finding the information they require.

Be aware before you begin!!!!Designing anything based on your own

preferences and biases is not the best approach

Getting it right means understanding the problem at hand or goals as well as knowing your audience

Make sure you understand the problem or site goals clearly ……

Tips for good Information Architecture

Cookie cutting solutions tend not to work!!!Don’t take a website that worked for one

person/business and build your site IA the sameDon’t just take an organisations structure and mimic

it- example ato.gov.au Get your needs analysis right FIRSTThere is no one solution for an information-rich siteBlogs generally demonstrate bad IA Why??

historyThe term “information architecture” was first coined by

Richard Saul Wurman in 1975. Wurman was trained as an architect, but became interested in the way information is gathered, organised and presented to convey meaning. Wurman’s initial definition of information architecture was “organising the patterns in data, making the complex clear”.

The term was largely dormant until in 1996 it was seized upon by a couple of library scientists, Lou Rosenfeld and Peter Morville. They used the term to define the work they were doing structuring large-scale websites and intranets.

First step in IA analysisMake sure you can answer the following 2 questionsWhat are your sites major audiences?What are you audiences major

questions/problems/needs and how are you going to answer them?

There are many ways to document an IA

Site maps Annotated page layouts Content matrices Page templates Personas Prototypes Storyboards

Site mapsSite maps are perhaps the most widely known and

understood deliverable from the process of defining an information architecture.

A site map is a high level diagram showing the hierarchy of a system. Site maps reflect the information structure, but are not necessarily indicative of the navigation structure.

Annotated page layoutsPage layouts define page level navigation, content

types and functional elements. Annotations are used to provide guidance for the visual designers and developers who will use the page layouts to build the site.

Page layouts are alternatively known as wireframes, blue prints or screen details.

Content matrixA content matrix lists each page in the

system and identifies the content that will appear on that page.

It may also document interactions between pages, page tags and other relevant information

Page templatesPage templates may be required when

defining large-scale websites and intranets. Page templates define the layout of common page elements, such as global navigation, content and local navigation. Page templates are commonly used when developing content management systems.

PersonasPersonas are a technique for defining

archetypical users of the system. Personas are a cheap technique for evaluating the information architecture without conducting user research.

PrototypesPrototypes are models of the system. Prototypes can be

as simple as paper-based sketches, or as complex as fully interactive systems. Research shows that paper-based prototypes are just as effective for identifying issues as fully interactive systems.

Prototypes are often developed to bring the information architecture to life. Thus enabling users and other members of the project team to comment on the architecture before the system is built.

StoryboardsStoryboards are another technique for

bringing the information architecture to life without building it. Storyboards are sketches showing how a user would interact with a system to complete a common task.

Storyboards enable other members of the project team to understand the proposed information architecture before the system is built.

Sources and referenceshttp://www.steptwo.com.au/papers/kmc_whatisinfoarchhttp://www.semanticstudios.com/publications/semantics/000149.phphttp://en.wikipedia.org/wiki/Information_architecturehttp://www.iainstitute.org/

www.themegallery.com

LOGO