CS 575 Spring 2012 Lecture 2. Engelbart Video Discussion Object-oriented system UI, Code, Documentation, Papers Language design – “overlay” hierarchy.

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Map of Human Computer Interaction
Lesson 1: Introduction to IT Business and Careers
CSCI 1412 Tutorial 1 Introduction to Hardware, Software Parminder Kang Home:
1 University of Palestine Information technology college Electronic Document Management System Technologies Electronic Document Management System Technologies.
1-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 1 THE INFORMATION.
CS 575 Spring K.V. Bapa Rao. Outline Administrative Review of previous class Douglas Engelbart’s demo video Student Presentations Discussion.
CS 575 Spring K.V. Bapa Rao. Outline Administrative Review of previous class Discussion of Engelbart’s Paper (contd) Student Presentations.
CS 575 Spring 2010 Class Meeting 3 Bapa Rao. Outline administrative Review of previous week Douglas Engelbart’s demo Student Presentations Agenda for.
CS 575 Spring K.V. Bapa Rao. Outline Administrative Review of previous class Douglas Engelbart’s demo video (Conclusion) Student Presentations.
Chapter Chapter Goals Describe the layers of a computer system Describe the concept of abstraction and its relationship to computing Describe.
CS 575 Spring K.V. Bapa Rao. Outline Administrative Review of previous class Student Presentations Licklider’s papers RDF Overview General.
Chapter 1 Assuming the Role of the Systems Analyst
Computers: Tools for an Information Age
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
Cs 575 Week 4 Spring 2008 Bapa Rao. Outline Organizational Discussion on previous week’s presentations Continuing discussion on Engelbart’s article Student.
Chapter 1 Assuming the Role of the Systems Analyst
Introduction to Software Engineering CS-300 Fall 2005 Supreeth Venkataraman.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Cs 575 Week 5 Spring 2008 Bapa Rao. Outline Organizational Review of previous meeting Student presentations Discussions.
Cs 575 Week 6 Spring 2008 Bapa Rao. Outline Organizational Review of previous meeting Student presentations Discussions.
Chapter 2 Introduction to Systems Architecture. Chapter goals Discuss the development of automated computing Describe the general capabilities of a computer.
Lecture # 1 M.Sc / BS(CS)/ BS(I.T) DPT www. Shahid Rasul.com.
Moving forward with Scalable Game Design. The landscape of computer science courses…  Try your vegetables (sneak it in to an existing course)  Required.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
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.
CS102 Introduction to Computer Programming
Chapter 01 Nell Dale & John Lewis.
System Design Chapter 8. Objectives  Understand the verification and validation of the analysis models.  Understand the transition from analysis to.
By, David Anderson.  Determine team members to collaborate on assessment.  Create a written AT assessment plan:  Determine assessment questions  Expected.
Introduction to Computer and Programming CS-101 Lecture 6 By : Lecturer : Omer Salih Dawood Department of Computer Science College of Arts and Science.
Database System Concepts and Architecture Lecture # 3 22 June 2012 National University of Computer and Emerging Sciences.
Management Information Systems
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Information Systems Analysis and Design
Human Resource Management Lecture 27 MGT 350. Last Lecture What is change. why do we require change. You have to be comfortable with the change before.
Human Computer Interaction – Introduction Hanyang University Jong-Il Park.
Chapter 10 Information Systems Analysis and Design
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
1-1 Chapter 1 THE INFORMATION AGE IN WHICH YOU LIVE Changing the Face of Business.
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
The Beauty and Joy of Computing Lecture #3 : Creativity & Abstraction UC Berkeley EECS Lecturer Gerald Friedland.
CS 390 Unix Programming Summer Unix Programming - CS 3902 Course Details Online Information Please check.
Lecture 7: Requirements Engineering
Lecture 1 Introduction Figures from Lewis, “C# Software Solutions”, Addison Wesley Richard Gesick.
1 Implementing Communications-Driven and Group Decision Support Systems Collaborating with peers at other locations is needed in many companies.
Computer Concepts 2014 Chapter 10 Information Systems Analysis and Design.
Experiences from Representing Software Architecture in a Large Industrial Project Using Model Driven Development Andres Mattsson 1 Björn Lundell 2 Brian.
Silberschatz, Galvin and Gagne  Operating System Concepts UNIT II Operating System Services.
1 SWE 513: Software Engineering People II. 2 Future Experience What will you be doing one year from now? Ten years from now?
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
LECTURE 20 26/11/15. Summary - Testing ◦ Testing affects all stages of software engineering cycle ◦ One strategy is a bottom-up approach – class, integration,
Hardware/Software Basics Test
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
Learning Objectives Understand the concepts of Information systems.
Introduction to Performance Testing Performance testing is the process of determining the speed or effectiveness of a computer, network, software program.
CS 575 Lecture 3 Spring 2012 K.V. Bapa Rao CSULA.
Using Technology to Solve Problems Unit 2 Mod 2 SO 7.
Introduction to Human Factors in Information Systems Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
Public Management Information Systems System Analysis & Design Saturday, June 11, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Configuration Control (Aliases: change control, change management )
PROGRAMMING (1) LECTURE # 1 Programming and Languages: Telling the Computer What to Do.
Victoria Ibarra Mat:  Generally, Computer hardware is divided into four main functional areas. These are:  Input devices Input devices  Output.
Chapter 1 Assuming the Role of the Systems Analyst.
DDC 1023 – Programming Technique
Lecture # 1 M.Sc / BS(CS)/ BS(I.T) DPT.
National Diploma in Computer Studies
KNOWLEDGE MANAGEMENT (KM) Session # 36
Presentation transcript:

CS 575 Spring 2012 Lecture 2

Engelbart Video Discussion Object-oriented system UI, Code, Documentation, Papers Language design – “overlay” hierarchy of objects – Custom languages Finite State Machines Compiler-compiler Software Engineering – Source-code control, Documentation Communication – Message handling and management Human-computer, Human-human collaboration concepts implemented in hardware & Software sytems – Remote Videocams, mouse, …

Augmenting the Human Intellect 1962 Engelbart’s report/proposal to Air Force Ofc. Of Scientific Research – Capability to obtain better solutions to complex problems New conceptual framework – Not small tricks Example scenario: an architect’s workday – Design alternatives – Operational environments – Functional specifications – Detailed design – Tools Synthesis, analysis, verification, debugging

Engelbart Overview Conceptual framework is needed to know – What to augment artifacts language methodology Training – Goal: problem solving process Process is what we actually do, and are trying to do more effectively – Structure or organization across the board Little steps, organized as a process hierarchy – Versus objects? Process repertoire or toolkit Basic capabilities (‘hardware’) to higher-level capabilities – Synergy, emergent capabilities, … Which subprocess to choose? – Executive Capability: planning, selecting, and supervising – Augmentation impact Suppose you had a better writing tool… – Hardware, software, dictionary, spell checker, fact researcher, … – Pencil to word processor » Benefits? » Break down old process, come up with new process » New capabilities!

Engelbart: Two-domain system H-LAM/T

Engelbart (contd) Capability repertoire hierarchy – Basic capabilities (human and artifact) are the raw materials – Mental structuring (cognitive structures) Development Models: garden, basketball team, machine building – Concept structuring – Symbol structuring – Process structuring ‘M’ in H-LAM/T – Physical structuring A in H-LAM/T – Interdependence among all these structures

Engelbart (contd) How did humans get ‘augmented’ during our development? – 1. concept manipulation – 2. symbol manipulation – 3. Manual, External, Symbol Manipulation Whorf’s hypothesis: Language affects our thinking and capabilities – 4. Automated external symbol manipulation (neo- whorfian: technology affects language and capabilities) Language can also evolve to meet conceptual and task needs (counterargument to whorfian hypothesis)

Engelbart (contd) Brick-pencil experiment

Engelbart (contd) Brick-pencil expt (de-augmentation) – Typewriter: 7 sec – Pencil: 20 secs – Brick, small letters: 65+ secs – Brick, large letters: 42 secs Impacts on effectiveness of culture – Too hard  too few people doing it – Different concepts for work, record-keeping, etc. What about known impacts of actual augmentation, 46 years after Engelbart wrote this proposal?

Engelbart (contd) Concept structuring – concepts are tools – concepts have handles--representations – concept structures map to mental structures – some concept structures are better than others – language (natural lang esp) is the grand concept structuring tool

Engelbart (contd) Symbol structuring – some symbols work better than others depends on the purpose – need flexibility, translatability – view generation capability (rather than physical linear ordering)

Engelbart (contd) Interdependence among hierarchies – Cyclic – Regenerative Improvement in one category feeds improvement in other categories

Engelbart (contd) Roles and levels – executive – direct-contributive model of executive superstructure – Bureaucratic hierarchy is onerous – contractor-subcontractor model Flexibility in the Executive Role – executive tasks are complex – orderly flexibility requirement on symbol etc. structures is costly – disorderly process of change must be supported ‘agile methodologies’

Engelbart (contd) Who will benefit – Every person who does his thinking with symbolized concepts Human language, pictographs, formal logic, mathematics, … – Architects, engineers, lawyers, writers, … – ‘information workers’

Human-computer symbiosis Issues – Speed mismatch – System requirements (hardware, memory, …) – Organizational mismatch: Memory organization (Information structuring and retrieval) – Language mismatch What versus how – I/O mismatch Voice, mobile, touch, …

Computer as communication device “In a few years, men will be able to communicate more effectively through a machine than face to face” What is communication? – Two tape recorders exchanging data – Two humans having a meeting – Collaborative Modeling

Licklider Contd--Economics Models are complex Simplification is risky and dangerous – Oversimplification – Premature simplification Communicating models is expensive – Cost of not doing it?

Licklider Contd Computer as switch vs. interactor Distributed intellectual resources – ‘critical creative mass’ Vision of internet – Store-and-forward technology Economics: billing models

Vision of internet Node Mediator for online life: OLIVER Social groups Better for individual Better for society

Summary Human Augmentation & Man-Computer symbiosis studied systematically very early on Licklider’s vision of internet was based on communication Led to TCP/IP

Needfinding Exercise Post-disaster – Lost pet – Missing relative Age, disability – Locating relief centers Available Match needs – Getting help to come to you – Procurement Barter Keeping track of balance Money transfer – Limitations Servers down High traffic Random failures of connectivity but worldwide connectivity may still be available

Workarounds, hacks Errors

Good Questions? Feature x: is it important to you? Specific vulnerability of systems to abuse Open-ended: what features would you like to see? User self-profile Who would you interview?

Data recording Notetaking Photos videos

Other Strategies Diary studies