why to architecture information

62
Information Architecture: An emerging 21 st century profession By : Dr. A.K. Ramani Head SCSIT,DAVV,Indore(M.P.) [email protected]

Upload: ashwani-kumar-ramani

Post on 27-Jan-2015

115 views

Category:

Education


1 download

DESCRIPTION

A Talk given in National Conference on Business & technology Conference at Indore, INDIA

TRANSCRIPT

Page 1: Why to Architecture Information

Information Architecture:

An emerging 21st century profession

By :

Dr. A.K. Ramani

Head SCSIT,DAVV,Indore(M.P.)

[email protected]

Page 2: Why to Architecture Information

Preface

In every enterprise ,a sound architecture is the key to success. As we know that a fragile architecture converts everything into chaos. So, by considering the stability of an enterprise, we should concentrate on its architecture. TOGAF is a framework that enable us to design, evaluate and build the right architecture for an enterprise. ADM is the core part of TOGAF .ADM is iterative and consists of many phases.

Page 3: Why to Architecture Information

Review of PresentationBusiness and IT evolution

Information Architecture

IA vs Design

Need of IA

Website Architecture

Enterprise Architecture and its benefits

Architecture team

Types of IA

Introduction to TOGAF

Related subjects

Wrap Up

Page 4: Why to Architecture Information

System is complex

Page 5: Why to Architecture Information

Different perceptions

Page 6: Why to Architecture Information

Yesterday’s Scenario

Page 7: Why to Architecture Information

Today’s Scenario

Page 8: Why to Architecture Information

Business Evolution

Old System

• De-centralized

• Federation

• Retailer Push

• Large inventories

• Manual processes

• Buying/Selling

• Mass consumers

New System

• Group

• Cohesion

• Customer pull

• Just in time

• Automatic processes

• Category management

• Individual customers

Page 9: Why to Architecture Information

IT Evolution

Old System

• Mainframes• Novell• DOS• Own development• SNA, IPX, Paper• Unmanaged• Unresponsive• Cost

New System

• Unix• Windows NT• Windows 95• Application Packages• TCP/IP• Managed• Enabling change• Benefit

Page 10: Why to Architecture Information

Vertical Business Processes

Page 11: Why to Architecture Information

Value Chains

Page 12: Why to Architecture Information

Technology/Business cycle times

Page 13: Why to Architecture Information

A rapidly changing technology and business landscape demands innovation and agility.

Page 14: Why to Architecture Information

“Never innovate out of fear, but never fear to innovate”.

Page 15: Why to Architecture Information
Page 16: Why to Architecture Information

Innovation lifecycle

Page 17: Why to Architecture Information

How to evolve new system from

old system??

Page 18: Why to Architecture Information

Solution is…..

Page 19: Why to Architecture Information

Architecture

1. Architecture -- (an architectural product or work)

2. Architecture -- (the discipline dealing with the principles of design and construction and ornamentation of fine buildings; ``architecture and eloquence are mixed arts whose end is sometimes beauty and sometimes use''

3.Architecture -- (the profession of designing buildings and environments with consideration for their esthetic effect)

4. Structure, Architecture -- (the manner of construction of something and the disposition of its parts; ``artists must study the structure of the human body"; "the architecture of a computer's system software'' )

Page 20: Why to Architecture Information

Architecture

+

Information

=

Information Architecture

Page 21: Why to Architecture Information
Page 22: Why to Architecture Information
Page 23: Why to Architecture Information

IA vs Design

• Two sides of the same coin?

• Each part of the other?• IA = one kind of design?• Design = one kind of IA?

Page 24: Why to Architecture Information

Is IA omnipresent??

Yes, it is..

Page 25: Why to Architecture Information

Spot the IA

Information Architecture

Waldo

Where’s the information architecture in this picture?

Page 26: Why to Architecture Information

An enigma history of information architecture

• Information architecture is as old as human communication.

• Where there’s information, there’s architecture.

Page 27: Why to Architecture Information

The most interesting architectures spring from problems of diversity:

o Diversity of informationo Diversity of audienceo Diversity of modes of accesso Diversity of use

But don’t overlook simple problems that have simple solutions

Page 28: Why to Architecture Information

Need of Information Architecture

• To support the business by providing the fundamental technology and process structure for an IT strategy.

• To provide a strategic context for the evolution of the IT system in response to the constantly changing needs of the business environment.

• To achieve the right balance between IT efficiency and business innovation.

Page 29: Why to Architecture Information

Website Information Architecture

• Information architecture is currently emerging as a discipline that concerns itself with the development of systematic approaches to the organization and presentation of online information.

• It is the combination of organization, labeling, search and navigation systems in websites, intranets, online communities and software

Page 30: Why to Architecture Information

User Driven Design

Page 31: Why to Architecture Information

Enterprise Architecture(EA)

Business StrategyIT Strategy

Page 32: Why to Architecture Information

Enterprise Architecture

It is a “glue” that allows both Business and IT strategy enable and drive each other.

Page 33: Why to Architecture Information

Enterprise Architecture

Page 34: Why to Architecture Information

The Technical Architecture Inputs

Page 35: Why to Architecture Information

Business benefits of EA

• Agility of enterprise

• Product time to market

• Flexible sourcing of value chain components

• Improved and consistent information exchange

• Risk reduction

Page 36: Why to Architecture Information

Financial benefits of EA

• Reuse

• Time savings

• Lower support cost

• Lower acquisition cost

• Technical adaptability

Page 37: Why to Architecture Information

The Architecture Team

Page 38: Why to Architecture Information

Information Architects do:• Research & understand user

requirements

• Find the patterns inherent in data, making the complex clear

• An information architect uses tools and methods to

– Plan

– Analyze

– Design

– Construct

– Verify

– Maintain

• Apply Experience

• Manage the IA Process

Page 39: Why to Architecture Information

Types of IA

• Top Down

• Bottom Up

Page 40: Why to Architecture Information

“Top-down” IA

It involves developing a broad understanding

of the business strategies and user needs, before defining the high level structure of site, and finally the detailed relationships between content.

Page 41: Why to Architecture Information

“Bottom-up” IA

It involves understanding the detailed relationships between content, creating walkthroughs (or storyboards) to show how the system could support specific user requirements and then considering the higher level structure that will be required to support these requirements.

Page 42: Why to Architecture Information

Not mutually exclusive—every project includes both.

Page 43: Why to Architecture Information

What does an architectureprocess give us?

A better understanding of the problems involved in creating an infrastructure for the public sector

– Common services

– Quality of service

– Vendor co-operation

– Centralisation of services vs flexibility in

choice of services

Page 44: Why to Architecture Information

Approach to Information Architecture

Architecture design is a technically complex process, and the design of heterogeneous, multi-vendor architectures is particularly complex. So, there is a need to simplify such complexity.

But how???

Page 45: Why to Architecture Information

TOGAF will help

Page 46: Why to Architecture Information

What is TOGAF?

• TOGAF is an architecture framework - The Open Group Architecture Framework.

• It enables you to design, evaluate, and build the right architecture for your organization.

Page 47: Why to Architecture Information

Real life definition of TOGAF

What TOGAF is What TOGAF is not

Generic Perspective about how to customize the framework.

Process driven Perspective, Artefact driven

“One size fits all organizations”. Specific to company size or to an industry

Flexible Ontology Driven

Set of conceptual tools Tool

Providing generic deliverables Prescribing a specific set of deliverables.

Page 48: Why to Architecture Information

TOGAF:Developing an architecture

Page 49: Why to Architecture Information

TOGAF: Information Architecture Process

TOGAF consists of three main parts:

• The TOGAF Architecture Development Method (ADM),

• The Enterprise Continuumo The TOGAF Foundation Architecture

The TOGAF Standards Information Base (SIB), The TOGAF Technical Reference Model (TRM)

o The Integrated Information Infrastructure Reference Model

• The TOGAF Resource Base

Page 50: Why to Architecture Information

TOGAF Framework concepts

Page 51: Why to Architecture Information

The TOGAF Architecture Development Method (ADM)

Figure : Architecture Development Cycle

Page 52: Why to Architecture Information

Figure : Architecture Development Cycle - Expansion

Page 53: Why to Architecture Information

The architecture development process needs to be linked into the organization

Page 54: Why to Architecture Information

Information architecture’s impact on the business

1. Customers consistently request:

• Better retrievability

• Solution-oriented information

• A seamless information experience across products

Page 55: Why to Architecture Information

2. Good information architecture can fulfill those requests and:

• Reduce total cost of ownership

• Reduce customer support calls

• Reduce number of non-defect customer support issues (NDOPs)

• Increase customer satisfaction

Page 56: Why to Architecture Information

3. All information developers can work toward these goals in their information deliverables and contribute to the overall information architecture.

Page 57: Why to Architecture Information

Use of Architecture Framework provides:

• speed

• simplify architecture development,

• ensure more complete coverage of the designed solution, and

• make certain that the architecture selected allows for future growth in response to the needs of the business.

Page 58: Why to Architecture Information

Worth reading

Page 59: Why to Architecture Information
Page 60: Why to Architecture Information

Related Subjects

• Usability / User experience/Interaction design• Information design• Graphic design• Information technology / System Design

Page 61: Why to Architecture Information

Questions

Page 62: Why to Architecture Information

Wrap Up

Contact information:

Dr. A.K Ramani

Head SCSIT,DAVV(Indore)

email: [email protected]

Thank you and Good Luck….