information architecture sire (strategic information requirements elicitation) approach from: g....

INFORMATION ARCHITECTURE SIRE (Strategic Information Requirements Elicitation) approach From: G. Motta & G. Pignatelli “From strategic to conceptual information modeling : a method and a case study”, ITAIS 2010 - Rev March 2012, October 2012, May 2013

Modeling techniques for enterprise information architectureSIRE enterprise information catalogueThe mapping method: a case studyReview questionsShort exerciseAppendix

2

SIRE’s position in BI modeling

• What kind of information our business needs?

• How far is current information from required information?

• How can we easily identify the information we need at strategic level?

• We here addresses such issue by an Enterprise Information Modeling named SIRE (Strategic Information Requirements Elicitation)

Enterprise Information Modeling

SIRE

1. Process duration2. Activity timeliness3. Resource flexiblity

1. Production unitcost

2. Productivity3. Usage / workload

1. Customer access / acquisition unitcost

2. Customer use cost

1. Technology response time

2. Technology timeliness

3. Activity & technology flexibility

1. Execution unitcost

2. Preparation effort

Flexibility & speedCost

Mana

ger

Cust

omer

Wor

ker

1. Response time 2. Response timeliness3. Vendor flexiblity

1. Spec conformity of service and products

2. Technologydependability

1. Expectation conformityof the service

2. Service dependability3. Customer satisfaction

1. Expectation conformityof work / work environment

2. Technologydependability

3. Employee satisfaction

Quality & satisfaction

KPI Identification /

mappingHIGO

Aggregate Strategic Level (ASL)

GUI ModelingGOA

Analytic Information Modeling

DFM

Rich Semantic Level (RSL)

Software Engineering Interface (SEI)

Implementation Level

SIRE: position in the functional analysis grid

• SIRE (Strategic Information Requirements Elicitation) is a catalog of the information domains of an enterprise.

• It uses a grid model, where information domains are layered into information levels, namely 1. master information

2. event information

3. analytic information• Developed in University of

Pavia (2008)

Information Domain

Information Level

Master Event Analysis

Domain 1

……

Domain n

Analysis Layer

Analysis DomainInformation Process User

Interface ASLRSMSEI

4

Early overall frameworks

• 70-80s : Business Systems Planning (BSP)– Grid framework for processes,

systems, data classes, functions (organizations)

– Shows usage of data classes by processes

– Method framework rather than domain modeling

• 90s: Information Engineering (IE) / Information Strategy Planning (ISP)– It intends to cover the whole cycle

from design to implementation– It links strategy level (BSP) with

conceptual level (Entity Relationships, Data Flow Diagrams (DFD))

– IE modeling techniques are now superseded by UML

Business

Process

Information Class

IC1 - Materials Master

IC2- Inventory Level

IC3 - Receivin

g Transact

ions

IC4- Inspecti

on Transact

ions

P1 X - X X

P2 ... X ... ...

... ... ... ... ...

Pn X X - X

5

Recent domain frameworks

• SCOR® (Supply Chain Organization and Reference Model) – Strategically and business oriented – Framework for manufacturing– No reference framework for data

• eTOM (Enhanced Telecom Operations Map®) – Strategically and business oriented – Framework for telco companies– Reference framework for data

Shared Information Data Model (SID)

– Key concept: “Aggregate Business Entity (ABE) is a well-defined set of information and operations that characterize a highly cohesive, loosely coupled set of business entities” (TMForum, 2003).

http://upload.wikimedia.org/wikipedia/commons/e/ef/ETOM.png

INFORMATION ARCHITECTURE SIRE (Strategic Information Requirements Elicitation) approach From: G. Motta & G. Pignatelli “From strategic to conceptual information modeling : a method and a case study”, ITAIS 2010 - Updated and revised on March and October 2012


ENTERPRISE INFORMATION CATALOGUE: core categories

ENTERPRISE INFORMATION CATALOGUE: the grid

INFORMATION CATALOGUE

Master Event Analysis

Stakeholders

Law

Competitor

Customer

Supplier

Broker

Shareholder

Resources

Personnel

Plants

Raw materials

Cash

Context

Structure

Project

Region

Output

Process

Product

Service

A case study in local Government :

• Municipality owns 13.000+ flats • Real estate management is outsourced : each

outsourcer has a different Information System• A new local law redefines rules for rents based on

– Market value of the flat – Social situation of applicants [Index of Equivalent Economic

Situation (IEES)] .

• Issue – What information our business needs?

• We are illustrating the information schema issue

SIRE- Strategic Information Requirements Elicitation - ITAIS 2010

12

Method: overview

1 Customize grid 2 Map SIE grid to ER

3 Link information islands 4 Refine

Step 1 Customize the gridMaster Data

Transactions Data

Events Certifications

Stakeholder

Law

oAllocation criteriaoSafetyoSocial contribution

o Periodic Check o Conformity / Non Conformity state

Customer

Tenanto Master Datao Other Information

oLease dealoLeasesoPayment Delayo Breach oLease RenewalsoAdjustmentsoLease abatementsoLease raiseso Appeal

HouseholdoMaster Datao IEES oOther Info

oCertified IEES

Broker REMoREM Master Data

Resources Unit

Flat

oMaster Data

o Routine Maintenanceo Extraordinary Maintenanceo Rationalization Actionso Renovationo Architectural Barrier-Free Design and Environmental improvemento Utilities o Services

Garage

14

INFORMATION TYPES

Master Data Transaction Data Analysis Data

Identification

Description

Man-Machine transaction

Machine-Machine transaction

Information

Types

Stakeholde

r

Customer

Private

Enterprise

Step 1 Comment on Method

Customization is based on Creation / Decomposition / Specialization • EG1 Customer is specialized into Private, Enterprise• EG2 Master Data are specialized into Identification &

Description • EG3 Transaction Data are specialized into Man to Machine and

Machine to Machine

Step 2 Map grid to ER

Step 3 Link information islands

Step 4 Refine

Method: summary

1. Customize the grid• Creation / Decomposition /

Specialization 2. Map grid to ER

• convert SIE grid into a preliminary ER schema

• link master information and transaction within the same information domain

3. Link information islands• identify common entities, attributes

and relation between domains• merge and / or link them in order

to obtain a more cohesive ER schema

4. Refine• insert new relations • specialize or decompose entities

and attributes • aggregate or generalize entities.

Review questions

• Describe the position of SIRE in the functional analysis grid in terms of abstraction levels and scope

• Describe the key elements of SIRE: Information Type and Information Domain

• Explain and exemplify the steps of the SIRE method

CHEAPAIR

• Issue – Mario Rossi, CEO of CHEAPAIR was really upset. CHEAPAIR was full

of database, but he was feeling he had not information for analysis.– He reviewed the information domains of the corporation, they included

• Regulation, highly variable across the world, • Resources as pilots, ground personnel, planes • Customers • Agents• Suppliers• Customer transactions as reservations, cancellations, claims etc.• Operations as maintenance, flights, refueling • Etc.

– He wanted to have a one glance view of the whole enterprise information

• Elicit information requirements and model them by SIRE • Suggestion: select a flight company e.g. Air China and visit its

website

GRAND HOTEL

• Issue – Ms Alex Orta, CEO of Grand Hotel Inc., was concerned

• Grand Hotel was full of database, but she was feeling she did not know if the information stored was complete or not.

• She considered the information domains of the corporation– Regulation, highly variable across the world, – Resources as rooms, personnel– Customers and suppliers– Customer transactions as reservations, cancellations, stays etc.– He did not know how good or bad was the performance about his main

product, i.e. flights, nor about services as booking, check-in and alike– Etc.

• Elicit the information requirements of Grand Hotel Inc. and model them by using the SIRE grid

• Suggestion: choose a website of an hotel chain e.g. Shangrila and analyze it

University

• Issue – Professor Bachelet, Rector of University of Orta (UO), was concerned

• UO was full of database, but he was feeling she did not know if the information stored was complete or not.

• He considered the information domains of the UO– Regulation, highly variable across the world – Personnel as professors and faculty staff – Equipment as building, laboratories and alike– Customers as students– External customers as enterprises which funded the UO – Customer transactions as enrollment, exam, etc.– He did not know how good or bad was the performance about his main product,

i.e. courses, nor about services as dormitories, check-in and alike– Etc.

• Elicit the information requirements of UO and model them by using the SIRE grid

• Suggestion: choose a website of an University e.g. TJU and analyze it


SIRE & IT Strategic Planning: a case study in HC


27

SIRE & IT Strategic Planning

SIESIE

• The HC case study shows the coverage by IT systems of critical information

• Steps: – Customize SIRE grid – Interview key users– Validate results

Coverage of Zachman’s Framework by SIRE

Layer What (Data)

How (Function)

Where (Network)

Who (People)

When (Time)

Why (Motivation)

Scope (Contextual) Planner

List of things important to the business

List of processes the business performs

List of locations in which the business operates

List of organizations important to the business

List of events significant to the business

List of business goals / strategies

Business Model (Conceptual) Owner

Semantic or ER Model

Business Process Model

Business Logistics System

Work Flow Model

Master Schedule Business Plan

System Model (Logical) Designer

Logical Data Model

Application Architecture

Distributed System Architecture

Human Interface Architecture

Processing Structure

Business Rule Model

Technology Model (Physical) Builder

Physical Data Model

System Design

Technology Architecture

Presentation Architecture

Control Structure Rule Design

Component Configuration Implementer

Data Definition Program Network

Architecture Architecture Timing Definition

Rule Specification

Functioning Enterprise Worker

Data Function Network Organization Schedule Strategy

The yellow background shows the coverage by the core method and the gray one shows the further coverage achieved by crossing strategic information entities with other dimensions of analysis

information architecture sire (strategic information requirements elicitation) approach from: g....

Documents

information engineering

master information

information domains

kind of information

information levels

event information

current information

required information