1. Sept-Dec 2009 - w1d21 Third-Generation Information Architecture CMPT 455/826 - Week 1, Day 2 (based on R. Evernden & E. Evernden)

2. Architecture “We use the word architecture –whenever we want to define –a high-level overview of interrelated components –and when the relationships among them are complex and difficult to understand. The basic idea of information architecture –reflected a fundamental need to impose better management structures on system development. Sept-Dec 2009 - w1d22

3. Focuses of the 3 Generations 1 st Generation –Systems as standalone applications –within individual organizations. 2 nd Generation –Systems as integrated sets of components –within individual organizations. 3 rd Generation –Information as a corporate resource –with supporting IT tools and techniques. Sept-Dec 2009 - w1d23

4. Accomplishing these Generations Opportunity: in order to accomplish these objectives, developers concentrate on different aspects of the data –1 st Generation: physical aspects Putting data into the computer and getting it back out from the computer –2 nd Generation: logical aspects Managing data in the computer Sharing the data –3 rd Generation: useful aspects Anticipating data needs outside the computer Recognizing how the data is used and how it could be used BUT how can we model this? Sept-Dec 2009 - w1d24

5. 3rd Generation Driven By: –Emergence of the Internet, e-commerce, and an increase in business-to-business applications; –Growing interdependence among organizations; –Adoption of knowledge management, systems thinking, and a more holistic view of information as a resource. Sept-Dec 2009 - w1d25

6. 3rd Generation Content –Explicit definition of principles and background theory –Development of multidimensional architectures; –Customization of information frameworks to the needs of individual organizations; –Generic information patterns and maps. Sept-Dec 2009 - w1d26

7. Deciding information management requirements. Information is complex; –any architecture described in a single chart or diagram is likely to be insufficient for such needs –a single diagram suggests the architecture is at best two- dimensional –whereas most organizations need to consider at least four or five dimensions The output from this step includes –principles, information design guidelines, standards, and naming conventions. –deciding which dimensions are in fact part of the architecture Sept-Dec 2009 - w1d27

8. So: which dimensions should be part of the architecture? Opportunity: we need to go beyond consideration of dimensions of data, to also include their relationships: E-R diagrams can provide a starting point –They model entities and relationships in two ? (meaningless physical, i.e. X and Y) dimensions –What else connects with the data? –What modeling implications does this have? Sept-Dec 2009 - w1d28

9. Creating a management toolkit Requirements determine which architectural dimensions are relevant and in turn govern which tools are needed. –A toolkit includes checklists, charts, and diagrams derived from using the dimensions, either on their own or in combination. –Dimensions transform a complicated problem into a simpler one by subdividing it into segments allowing people from different fields of expertise to collaborate. provide a cohesive structure or blueprint for a long-term information strategy, permitting the gradual development of the information resource. –The number of dimensions and the range of possibilities mean that tools can be tailored to the conditions and context of use, ensuring the right tools are available to implement the architecture. Sept-Dec 2009 - w1d29

10. What is context of use? Opportunity: it would be useful to have some guidance on context of use. context of use –is defined by ISO 9241-11: 1998 as users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used –is dealt with in human-centered design in ISO 9241-210 (which I can let you see if you are interested any further) –Does this give you any ideas for major dimensions to include in our modelling? –How might these dimensions apply to our data model? Sept-Dec 2009 - w1d210

11. Defining an information map An information map –charts relevant information items, as well as the links and groupings among them. –contains information about information (beyond metadata), including explanations about how it is or could be used, who uses it how it is structured why it is structured in a particular way –Data and process models (or OO models) of the business and its supporting systems are often too technical in terms of both content and structure to meet the full potential of an information map. Sept-Dec 2009 - w1d211

12. Defining an information map The related descriptions, definitions, and examples –should be in the language of business management rather than the jargon of technology. Information about how information is used –has great potential for improving the effectiveness of information as it might be used –and for creating innovative new ways to generate revenue. Sept-Dec 2009 - w1d212

13. But what does it look like Opportunity: this paper provides goals for 3 rd Generation Information Architectures, but does not provide specific tools or formats for a map. NOTE: The authors run a consulting company and would probably be happy for you to hire them to use their tools and formats to develop an Information Architecture for you. Sept-Dec 2009 - w1d213

14. Using the information resource Third-generation architectures are not static; –they evolve through experience and use Comments from employees, customers, suppliers and from anyone using the information –help adapt the architecture to meet the overall needs of the organization Sept-Dec 2009 - w1d214

15. This concludes our introduction Starting next week, the papers contain more content Remember: You need to submit a critique for the first of the papers for each week by Friday noon of the week that proceeds their being dealt with Sept-Dec 2009 - w1d215