Information Management and Information Design

Enterprise Architects
Jul. 27, 2015
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
Information Management and Information Design
1 of 26

More Related Content

What's hot

Repositioning the Value of the Architecture PracticeRepositioning the Value of the Architecture Practice
Repositioning the Value of the Architecture PracticeEnterprise Architects
Business capability mapping and business architectureBusiness capability mapping and business architecture
Business capability mapping and business architectureSatyaIluri
Using Business Architecture to Facilitate a North American Business Model at ...Using Business Architecture to Facilitate a North American Business Model at ...
Using Business Architecture to Facilitate a North American Business Model at ...Daniel Lambert, M. Sc.
How to develop and govern a Technology Strategy in 10 weeksHow to develop and govern a Technology Strategy in 10 weeks
How to develop and govern a Technology Strategy in 10 weeksLeo Barella
Business by DesignBusiness by Design
Business by DesignCraig Martin
Zen and the Art of Enterprise Architecture - IoTZen and the Art of Enterprise Architecture - IoT
Zen and the Art of Enterprise Architecture - IoTAlan Hakimi

What's hot(20)

Similar to Information Management and Information Design

DMBOK and Data GovernanceDMBOK and Data Governance
DMBOK and Data GovernancePeter Vennel PMP,SCEA,CBIP,CDMP
Data Architecture StrategiesData Architecture Strategies
Data Architecture StrategiesDATAVERSITY
Data Architecture, Solution Architecture, Platform Architecture — What’s the ...Data Architecture, Solution Architecture, Platform Architecture — What’s the ...
Data Architecture, Solution Architecture, Platform Architecture — What’s the ...DATAVERSITY
PowerPoint presentationPowerPoint presentation
PowerPoint presentationwebhostingguy
Valuing Information Management and IT ArchitectureValuing Information Management and IT Architecture
Valuing Information Management and IT ArchitectureGoutama Bachtiar
Bob panic solution architect - enterprise it systems & security architecture ...Bob panic solution architect - enterprise it systems & security architecture ...
Bob panic solution architect - enterprise it systems & security architecture ...bob panic

Recently uploaded

Marv Wexler - Transform Your with AI.pdfMarv Wexler - Transform Your with AI.pdf
Marv Wexler - Transform Your with AI.pdfSOLTUIONSpeople, THINKubators, THINKathons
Webinar Sept. 21 Bloomerang_FINAL.pdfWebinar Sept. 21 Bloomerang_FINAL.pdf
Webinar Sept. 21 Bloomerang_FINAL.pdfBloomerang
MSA Website Slideshow (1).pdfMSA Website Slideshow (1).pdf
MSA Website Slideshow (1).pdfHamzaKhan46086
Biotech Fundraising in a DownturnBiotech Fundraising in a Downturn
Biotech Fundraising in a DownturnVolker Hirsch
Gravyty Presentation for Bloomerang Year End Stewardship 9-26-23.pdfGravyty Presentation for Bloomerang Year End Stewardship 9-26-23.pdf
Gravyty Presentation for Bloomerang Year End Stewardship 9-26-23.pdfBloomerang
Eddie Tofpik's TA Presentation at SEEMT Sep 2023Eddie Tofpik's TA Presentation at SEEMT Sep 2023
Eddie Tofpik's TA Presentation at SEEMT Sep 2023TOFPIK

Information Management and Information Design

Editor's Notes

  1. The focus of this presentation is on information architecture and design and is an invitation to revisit our current understanding of information management.
  2. Standard background on who we are and what we do.
  3. The presentation starts with this premise It is a an invitation to revisit existing notions about Information Management and Information Architecture The aim of this presentation is to introduce a framework to clearly distinguish between terms like information management and data management, or data architecture and information architecture – unlike DAMA DMBOK which treats these terms as synonyms. And lastly identify relevant sets of architectural deliverables designed to support strategic IM
  4. Each of these frameworks or standards has something to say in the data and information space We’ll review some of the key definitions within these frameworks to better understand the what they have to say about the difference between data and information By better understanding the differences between data and information we will better understand the differences between information management and data management, information architecture and data architecture The DAMA circle defines a series of Knowledge Areas that collectively define the discipline of data management The TOGAF ADM defines a methodology for delivering Enterprise Architecture and includes data and application deliverables The MIKE2.0 model ( Method for an Integrated Knowledge Environment) provides a description of a set IM Core Solutions and includes data, architecture and IM components ISO 2382-1 Information Technology Vocabulary defines common terms used to describe data, information and the systems and technologies used to manage these
  5. Lets start by identifying an agreed definition of information The common theme across these definitions is the role of context DAMA, ISO 2382, MIKE 2.0 – Information is Data + Context. Data is the representation of facts, text etc – raw input. Data is meaningless until it is presented in a context
  6. The challenge then is to understand what this means in reality This statement implies that information is the product of two domains: data and context While we understand the management of data well, what constitutes the management of context is less clear Clearly, any definition of information as an asset needs to address both the data and context elements of the definition of Information
  7. DAMA seems to imply that ‘context’ equates to meta-data and doesn’t mention the role of information system MIKE 2.0 clearly distinguishes between the data and information system ISO 2382-1 does not define Information Asset – but does define Information System ISO 2382-1 and MIKE 2.0: Information System is a synonym for information asset Both MIKE2.0 and ISO 2382 make the distinction between data and the presentation platform (Information System) ISO 2382-1 states that data processing is not a synonym for information processing – the next slide may help make this distinction clearer
  8. ISO 2383-1 Data processing is not a synonym for information processing Reinforces the view that data and information assets are different things Reinforces the responsibility of the Information System (aka Information Asset) to manage the translation of Information to discrete data entities and interpretation of constituent Data back to Information.
  9. Information assets are then constructed from one or more data assets plus a system that is responsible for providing the context needed to communicate the correct or intended meaning. The value of an information asset is dependent on both the data asset and the presentation platform. The presentation platform is most often an application – but not always – i.e., there are manual presentation platforms we use (e.g., a book).
  10. Any definition of Information Management then needs to encompass the management of both data and context DAMA equates information management and data management MIKE 2.0: distinguishes between data management and information management ISO 2382-1 only defines the terms information management and data management in the context of an Information Processing System and so is not listed here. TOGAF does not define information management or data management
  11. Information management must necessarily be concerned with the management of contributing data assets as well as presentation platforms for a given information asset This is not to say that information management is the same as data management and application or system management. However, there is obviously a relationship between these activities.
  12. The term ‘information architecture’ has been hijacked by the web development community to mean the design of a web based solution (ie., layout and structuring of pages and page components) DAMA uses the term to describe a process for supporting the development an information solution – which is consistent with the web development definition TOGAF does not include the concept. It does however include the concept of Information Systems Architecture – and defines this is as the combined view across data and application architectures. ISO 2382-1 does not define the term – does not define data architecture either. MIKE 2.0 is a more consistent definition – relating information architecture back to the subject of information management – namely information assets. Recall that MIKE 2.0 defines Information Assets as the combination of data and presentation platform.
  13. It follows that information architecture must have a relationship to data architecture and presentation platform (i.e., application) architecture. Given that information architecture is dependent on both data and applications suggests that as a domain it sits between Business and Application or Data Architecture.
  14. This is an enterprise architecture domain reference model This model illustrates where information architecture sits and its relationships to other architecture domains. Information architecture supports Business architecture by describing the Information artefacts that the business needs to support decision making, it also provides an umbrella for the application and data architectures which describe the components that go together to form the business information artefacts (aka Information assets) Information architecture is also a component of Information security architecture, and integration or interoperability architecture.
  15. The TOGAF ADM does not include a specific Phase to develop Information Architecture. It does include Phase C to describe Information System architecture which suggests that within TOGAF the concept Information System is the same as an Information Asset. Unfortunately the TOGAF definition of an Information System is “The computer (or IT)-based portion of a business system.” TOGAF has little if anything to say about Information Design The DAMA framework does not include a dedicated information architecture Knowledge Area MIKE 2.0 Framework does mention architecture in the context of IM – but this is limited to EII and SOA architectures. As we have seen it does at least provide distinct definitions for the terms information and data arahcitecture.
  16. This framework is the result of ongoing discussion within Enterprise Architects – affectionately known as the IM Wall It introduces the Information Architecture and Information Design as core elements of Information Management. As we have seen these components are arguably gaps in the other common frameworks in the IM space. It also highlights the relationship and dependency on Data Management It positions Information Design as a component that Content Management an Analytics and Reporting components need to align to.
  17. Richard Buchanan thought leader in Design Thinking Richard Buchanan describes 4 ‘Orders’ of Design, and the suggestion that contemporary society is as interested in the experience as the object or visual aesthetic. Information Design can be associated with each of the four orders. Information Design is evident in: Presentation (Graphic design) The physical platform or device (e.g., mobile device) The experience (communication of intended meaning, digital user experience) An environmental design (integration across visual, device and communication experience)
  18. Deliverables for Information Design includes a Information Delivery Model that describes information asset types, the channels by which they are available and the presentation standards that apply.
  19. Information Portfolio Architecture describes the architecture or structuring of information assets and their relationship to key business processes Different information classes are best suited for use with particular content types and particular delivery platforms (technologies). Information Portfolio Architecture models and categorises information assets according to class, content type and delivery platform, highlighting where there are weak matches and opportunities to improve.
  20. Our definition of Information asset Lifecycle management needs to include: Management of data sources over the life of the asset Management of presentation and delivery platform over the lifecycle of the asset
  21. Information Portfolio Model Categorised by Business Capability or Information Asset Class Logical Data Component = Information Asset Questions: What is the impact of changing a given Data Entity? How well supported are our key information assets? (app health of managing app) + Data Quality of constituent Data Entities Where do we need MDM? (same Data Entity across multiple Info Assets) Channel Architecture Model – input to Digital Strategy Categorise by Delivery Channel Channels aligned with Consumer (Role) Questions: What is user experience with our information assets? Do we have gaps across channel information availability? CDM (Use DAMA Definition) Group by Logical Data Component (Subject Area) Relationships between Conceptual Data Entities Questions: Do we have a common business language?