1 Peter Fox Xinformatics Week 10, April 10, 2011 Information Audit and XInformatics course summary.

Slides:



Advertisements
Similar presentations
Cognitive Academic Language Learning Approach
Advertisements

Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
OASIS Reference Model for Service Oriented Architecture 1.0
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Software Requirements
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
© Copyright Eliyahu Brutman Programming Techniques Course.
Lecture Nine Database Planning, Design, and Administration
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
USE Case Model.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
Evaluating Educational Technology and Integration Strategies By: Dakota Tucker, Derrick Haney, Demi Ford, and Kent Elmore Chapter 7.
1 Peter Fox Xinformatics – ITEC 6961/CSCI 6960/ERTH Week 12, April 27, 2010 Information discovery and integration and course summary.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
1 Shawlands Academy Higher Computing Software Development Unit.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Rational Unified Process Fundamentals Module 4: Disciplines II.
ITEC224 Database Programming
1 Peter Fox Xinformatics – ITEC 6961/CSCI 6960/ERTH Week 12, May 3, 2011 XInformatics course summary.
Introduction to Interactive Media The Interactive Media Development Process.
Software Requirements Engineering CSE 305 Lecture-2.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 Peter Fox Xinformatics 4400/6400 Week 11, April 16, 2013 Information Audit and dealing with Unstructured Information.
Requirements Engineering Requirements Elicitation Process Lecture-8.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Assessing Quality for Integration Based Data M. Denk, W. Grossmann Institute for Scientific Computing.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Approaching a Problem Where do we start? How do we proceed?
1 Peter Fox Xinformatics 4400/6400 Week 12, May 27, 2015 XInformatics course summary.
RHS 303. TRANSITION OF THEORY AND TREATMENT nature of existence and gives meaning to and guides the action Philosophical Base: Philosophy of occupational.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
ARCH-2: UML From Design to Implementation using UML Frank Beusenberg Senior Technical Consultant.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Requirement Handling
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
The Software Development Process
© 2010 Health Information Management: Concepts, Principles, and Practice Chapter 5: Data and Information Management.
ESIP Semantic Web Products and Services ‘triples’ “tutorial” aka sausage making ESIP SW Cluster, Jan ed.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
1 Class exercise II: Use Case Implementation Deborah McGuinness and Peter Fox CSCI Week 8, October 20, 2008.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Formal Specification: a Roadmap Axel van Lamsweerde published on ICSE (International Conference on Software Engineering) Jing Ai 10/28/2003.
UML - Development Process 1 Software Development Process Using UML.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
Data Foundation IG DF Organizing Chairs: Gary Berg-Cross & Peter Wittenburg.
Program Design. Simple Program Design, Fourth Edition Chapter 1 2 Objectives In this chapter you will be able to: Describe the steps in the program development.
Information Model Driven Semantic Framework Architecture and Design for Distributed Data Repositories AGU 2011, IN51D-04 December 9, 2011 Peter Fox (RPI)
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
 System Requirement Specification and System Planning.
Building Enterprise Applications Using Visual Studio®
Object-Oriented Software Engineering Using UML, Patterns, and Java,
The Systems Engineering Context
XInformatics course summary
Software Development Process Using UML Recap
Presentation transcript:

1 Peter Fox Xinformatics Week 10, April 10, 2011 Information Audit and XInformatics course summary

Contents Information audit Summary of this course What you needed to learn/ objectives 2

Businessdictionary.com Analysis and evaluation of a firm's information system (whether manual or computerized) to detect and rectify blockages, duplication, and leakage of information. The objectives of this audit are to improve accuracy, relevance, security, and timeliness of the recorded information. 3

What is an information audit? An information audit is a process that effectively determines the current information environment within an organization by identifying and mapping: –What information is currently available? –Where the information lives? –How the information is (or is not) delivered or accessed? –How the information is maintained, revised or deleted? 4

Results/ format (e.g.) The results of an information audit are twofold: there is a detailed report which includes: –What information do staff acquire? Where from? At what cost? How is it used? –What information do staff create? What happens to it? Where does it go? –What information is stored and why? What purpose will it serve? –What information is passed on or delivered? To whom? For what purpose? In what form? 5

Results/ format (e.g.) –Is there a gap, or a match, between that which is available and that which is needed? –What are the skills and responsibilities of the people who carry out these tasks? –What equipment and tools do they have available (hardware, software, filing cabinets, web sites, etc)? –Are there any control documents, such as policy statements, guidelines, service level agreements, procedures, manuals? –Is any of the information (produced, acquired, processed, re-delivered, or stored) superfluous to needs? –Are any of the information-handling activities non- productive? 6

Results/ format (e.g.) There is also a detailed flow chart: –A visual map that show the areas, processes, functions and activities through which information passes, clarifying gaps or fault-lines that need to be plugged or bottlenecks and overflows that need to be unblocked Sound familiar? 7

How to use? An information audit can be used as a baseline for making major improvements to the business process of an organization. It is extremely helpful in the identifying, buying, and implementation of enterprise systems, such as finance systems, portfolio management systems, document management systems, learning and knowledge management systems, etc. 8

9

The key is: As the volume, complexity and heterogeneity increases… –Suddenly information looks more like a continuum –All known methods, algorithms do not scale (except for very simple operations) –And because it is information, humans are part of the loop Thus - understand and apply theoretical foundations All to date are developed in an analog world, not a digital one!! 10

Abduction method of logical inference (Peirce) prior to induction and deduction i.e. "hunch” starts with a set of (seemingly unrelated) facts + intuition (some connection) and brought together – via abductive reasoning abduction is the process of inference that produces a hypothesis as its end result 11

A Use Case … is a collection of possible sequences of interactions between the information system under discussion/ design and its actors, relating to a particular goal … consists of a prose description of an information system's behavior when interacting with the actors … is a technique for capturing functional requirements of an information system … captures non-functional requirements

Ultimately: Wetware ‘Before you make the software interoperable, you need to make the people interoperable’: Ian Jackson, 13

Developed for NASA TIWG E.g. Table of Contents ==Plain Language Description== ===Short Definition=== ===Purpose=== ===Describe a scenario of expected use=== ===Definition of Success=== ==Formal Use Case Description== === Use Case Identification=== ===Revision Information=== ===Definition=== ===Successful Outcomes=== ===Failure Outcomes=== ==General Diagrams== ===Schematic of Use case=== ==Use Case Elaboration== ===Actors=== ====Primary Actors==== ====Other Actors==== ===Preconditions=== ===Postconditions=== ===Normal Flow (Process Model)=== ===Alternative Flows=== ===Special Functional Requirements=== ===Extension Points=== ==Diagrams== ===Use Case Diagram=== ===State Diagram=== ===Activity Diagram=== ===Other Diagrams=== ==Non-Functional Requirements== ===Performance=== ===Reliability=== ===Scalability=== ===Usability=== ===Security=== ===Other Non-functional Requirements=== ==Selected Technology== ===Overall Technical Approach=== ===Architecture=== ===Technology A=== ====Description==== ====Benefits==== ====Limitations==== ===Technology B=== ====Description==== ====Benefits==== ====Limitations==== ==References== ===Special Functional Requirements=== ===Extension Points=== ==Diagrams== ===Use Case Diagram=== ===State Diagram=== ===Activity Diagram=== ===Other Diagrams=== ==Non-Functional Requirements== ===Performance=== ===Reliability=== ===Scalability=== ===Usability=== ===Security=== ===Other Non-functional Requirements=== ==Selected Technology== ===Overall Technical Approach=== ===Architecture=== ===Technology A=== ====Description==== ====Benefits==== ====Limitations==== ===Technology B=== ====Description==== ====Benefits==== ====Limitations==== ==References==

Information theory Semiotics - study of sign processes or signification and communication, signs and symbols, into three branches: –Syntax: Relation of signs to each other in formal structures –Semantics: Relation between signs and the things to which they refer - meaning –Pragmatics: Relation of signs to their impacts on those who use them 15

THE PHYSICS OF INFORMATION © 2005 EvREsearch LTD EvREsearch©

Physics of information = uncertainty/ integrity Information of a random variable is defined as the Sum of p x log p, where p=probability. It represents the uncertainty of the variable Mutual information of two variables = how much information one variable contains about the other –i.e. the decrease of the uncertainty of one variable by knowing the other In probabilistic terms, the entropy decreases by conditioning on the distribution 17

Noise Uncertainty, especially any that is introduced is a source of noise, or more accurately – bias in the use or interpretation of the information –is context and structure dependent –Noise/ bias contamination is rampant in information systems Quality assessment, control and verification is less developed for information sources 18

Mode of noise introduction 19 From Shannon and Weaver (1949) Information Source Web Content, Structure Noise source Web browser? HTML page, user Msg?Signal?Recvd?Msg?

Intersecting disciplines: 20 Library Science Organizes- Cataloging and classification Preservation - ‘maintaining or restoring access to artifacts’ Cognitive Science mental representation, the nature of expertise, and intuition Social Science Collaborati on Cultural norms Rewards

Presentation Separation of content from presentation!! The theory here is empirical or semi-empirical Is developed based on an understanding of minimizing information uncertainty beginning with content, context and structural considerations and cognitive and social factors to reduce uncertainty Physiology for humans, color, … 21

Organization Organizations - producers v/s consumers Organization of information presentation, e.g. layout on a web page Yes - content, context and structure How to organize –What have you seen? –Needed? –Not had resolved? 22

Mental Representation Thinking = representational structures + procedures that operate on those structures Did you make progress? Methodological consequence: what have you learned about the study how we think about information systems? 23

Behind this: Information Models Conceptual models, domain models, explore domain concepts High-level conceptual models are created as part of initial requirements envisioning efforts - to explore the high-level static business or science or medicine structures and concepts. Conceptual models are created as the precursor to logical models or as alternatives to them MUST be followed by logical and physical models 24

(Information) Architectures Definition: –“is the art of expressing a model or concept of information used in activities that require explicit details of complex systems” (wikipedia) –“… as in the creating of systemic, structural, and orderly principles to make something work - the thoughtful making of either artifact, or idea, or policy that informs because it is clear.” Wuman 25

Architectures Building on content, context, and structure, think of information architectures as “in front of the interface” and “behind the interface” What’s the proportion – is it just like an iceberg? I.e. the majority of information architecture work is out of sight, "below the water.” 26

Reference architectures “provides a proven template solution for an architecture for a particular domain. It also provides a common vocabulary with which to discuss implementations, often with the aim to stress commonality. A reference architecture often consists of a list of functions and some indication of their interfaces (or APIs) and interactions with each other and with functions located outside of the scope of the reference architecture.” (wikipedia) Have you seen a reference architecture? 27

Design? “In the context of information systems design, information architecture refers to the analysis and design of the data stored by information systems, concentrating on entities, their attributes, and their interrelationships. It refers to the modeling of data for an individual database and to the corporate data models an enterprise uses to coordinate the definition of data in several distinct databases. 28

Design theory Elements –Form –Value –Texture –Lines –Shapes –Direction –Size –Color Relation to signs and relations between them 29

Principles of design Balance Gradation Repetition Contrast Harmony Dominance Unity 30

Broad life-cycle elements Acquisition: Process of recording or generating a concrete artefact from the concept (the act of transduction) Curation: The activity of managing the use of data from its point of creation to ensure it is available for discovery and re-use in the future Preservation: Process of retaining usability of data in some source form for intended and unintended use Stewardship: Process of maintaining integrity across acquisition, curation and preservation 31

Acquisition What do you know about the developer of the means of acquisition –Documents -not be easy to find/ read/ understand –Remember bias!!! Have a checklist (the Management list) and review it often 32

Curation From Producers to Consumers! Organization and presentation! Documentation! Provenance! So sorry for all the !!!!!!!!!!!!!!! Technology-neutrality? Add metainformation 33

Preservation Archiving is but one component Intent is that ‘you can open it any time in the future’ and that ‘it will be there’ Steps not be conventionally thought of Think far into the future …. history gives some guide to future considerations 34

Information Management Creation of logical collections Physical handling Interoperability support Security support Ownership Metadata collection, management and access. Persistence Knowledge and information discovery Dissemination and publication 35

36 Information Workflow Series of tasks performed to produce a final outcome Information workflow = “analysis pipeline” –Automate tedious jobs that users traditionally performed by hand for each dataset –Process large volumes of data/ information faster than one could do by hand

Information integration Involves: combining information residing in different sources and providing users with a unified view of them Recall the domain examples: –Geo? –Medical/ health? –Others? 37

Discovery? Discussion –What is the reality? –Information architecture considerations? –Facilitation of Xinformatics? 38

Visualization? Reducing the amount of data, quantization –Patterns –Features –Events –Trends –Irregularities –Exit points for analysis Also presentation of data Cognitive science and the mental representation 39

Factors that count! Quality –Is in the eyes of the beholder – why this is so important? Uncertainty –has aspects of accuracy (how the real world situation is assessed, it also includes bias) and precision (down to how many digits) Bias –Systematic error resulting in the distortion of measurement data caused by prejudice or faulty measurement technique –A vested interest, or strongly held paradigm or condition that may skew the results of sampling, measuring, or reporting the findings of a quality assessment: Psychological: for example, when data providers audit their own data, they usually have a bias to overstate its quality. Sampling: Sampling procedures that result in a sample that is not truly representative of the population sampled. (Larry English) 40

In one slide? Use case – you have to know the goal (+more) Conceptual and logical models -> information models Understand information flows and uncertainties (sign systems), the life cycle and manage them Apply information, library, cognitive, social science, and design elements to developing a design of an architecture Think the design through (e.g. get closer to the physical model (workflow?)) and assess the presentation, organization, content, context, structure, syntax, semantic and pragmatics 41

What would your slide include? 42

Objectives To instruct future information architects how to sustainably generate information models, designs and architectures To instruct future technologists how to understand and support essential data and information needs of a wide variety of producers and consumers For both to know tools, and requirements to properly handle data and information Will learn and be evaluated on the underpinnings of informatics, including theoretical methods, technologies and best practices. 43

Learning Objectives Through class lectures, practical sessions, written and oral presentation assignments and projects, students should: –Understand and develop skill in Development and Management of multi-skilled teams in the application of Informatics –Understand and know how to develop Conceptual and Information Models and Explain them to non-experts –Knowledge and application of Informatics Standards –Skill in Informatics Tool Use and Evaluation 44

Discussion All of the material? 45

Reading for this week pdfhttp:// 38.pdf 46

What is next April 17 – No class GM week April 24 – guest lectures, 9am: astro-, 10am: geo-, 11am: chem- May 1 – final project presentations (BE ON TIME, i.e. 5-10mins BEFORE 9AM) And, be prepared to be asked (and answer) questions 47