Information System Design Info-440

Slides:



Advertisements
Similar presentations
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #4.
Advertisements

The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #21.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #18.
Week 23 - Revision1 Week 23 Revision DSA. Week 23 - Revision2 Agenda Section A: Multiple choice Section B: Problem-oriented questions Topics for revision.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Organizing Data Chapter 5. Data Hierachy Table = Entities X Attributes Entities = Records Attributes = Fields.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #3.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #7.
Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.
Systems Development Life Cycle
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Configuration Management
Where Do I Start REFERENCE: LEARNING WEB DESIGN (4 TH EDITION) BY ROBBINS 2012 – CHAPTER 1 (PP. 3 – 14)
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Object-Oriented Analysis and Design OVERVIEW. Objectives  Describe Information Systems  Explain the role of a systems analyst  Introduce object-oriented.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
The Information School of the University of Washington INFO-340: Database Management & Information Retrieval David Hendry Class L-02.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
Web Site Design & Management Class 7 March 12, 2003.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #16.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #14.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #15.
School of Information, Fall 2007 University of Texas A. Fleming Seay Information Architecture Class Four.
Systems Development Lifecycle
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #13.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Lecture # 17 July 28,2012 Data Modeling using the Entity Relationship.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #11.
Information Architecture & Design Week 3 Schedule -Syllabus Updates -Group Project Finalized -Research Presentations Finalized -IA Methodologies -Class.
University of Washington HCDE 418 Wireframes HCDE 418.
Data Modeling Using the Entity- Relationship (ER) Model
Elaboration popo.
Investigating System Requirements
Introduction to UML.
Database Development Lifecycle
Roadmap Week 1: Intro to MIS Week 2: Systems Analysis
Chapter 7: Software Engineering
SAP SuccessFactors extension with SAP HANA Cloud Platform Innovation Use Case SAP & Partner Confidential
Sharing lessons through effective modelling
Information System Design Info-440
Information System Design Info-440
Information System Design Info-440
National 5 Computing Science Specimen Question Paper
Learning Intention I will learn about the iterative software development process with a focus on the Design stage.
Informatics 121 Software Design I
Informatics 121 Software Design I
Entity-Relationship Model and Diagrams (continued)
Information Systems in Organizations 2
Informatics 121 Software Design I
Information System Design Info-440
Analysis models and design models
Software Design Lecture : 15.
CSE 490ra Projects.
Database Development Cycle
Informatics 121 Software Design I
Course Overview CS 4640 Programming Languages for Web Applications
Members: Keshava Shiva Sanjeeve Kareena
Homework Do Now: Agenda Monday November 7, 2016 Objectives:
Information System Design Info-440
Informatics 121 Software Design I
Course Overview CS 4640 Programming Languages for Web Applications
Functional skills Week 10.
Information system analysis and design
Presentation transcript:

Information System Design Info-440 Autumn 2002 Session #8

Agenda Admin/review Process Conceptual modeling Break Two exercises Reminder of where we are? Conceptual modeling Break Two exercises Return quiz Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Admin Announcements Interactive design project Quizzes Lab today: If you can, please bring scissors, tape, color pencils, etc. Anyone? Interactive design project To learn more about Tablet PCs, try: http://www.pencomputing.com Questions? Proposal due: Oct 28 (Monday) Quizzes Back today! Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Last time Design spaces Task analysis/User Flows Key idea: Map multiple items on a two-dimensional plot Example dimensions: Task, product, user-satisfaction, market landscape Task analysis/User Flows Key idea: Represent goals and tasks User flows are usually procedural Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Task Analysis/User Flows: Symbols Goal start No Task Task Decision Yes Other path Task Task end Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Process

Development process Define: Vision/scope Deploy: Delivery stable Version Release Define: Vision/scope Needs assessment Deploy: Delivery stable technology Beta software Vision/scope document Develop: Build the technology Design: Invent the technological solution Design specifications document Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Length of Development Cycle 1 Six month cycle Effective for well-established businesses Effective when making evolutionary improvements 3 two-month cycles Effective for new businesses/ideas Effective when trying to make revolutionary improvements Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Conceptual modeling

Shift focus from ‘users’ to the ‘system’ We’ve looked at users long enough! Contextual inquiry, affinity diagrams, personas, scenarios, task analysis, etc. Let’s start designing! Key idea: Difference between logical structure of a system and physical system Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Logical vs. Physical Design Physical: surface of the interface (skin) Colors, fonts, zones, grids, graphics, etc. Discipline: Information design Logical: structure underlying the interface (skull) Entities, relationships, attributes, operations, etc. Examples: HTML tags vs. spacer gifs Database schema vs. indexes of tables XML vs CSS … Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Three example from Quiz The TV Guide is ordered by day. Each day lists TV shows in a grid according to hour and station. Index - Friends 7:30 - Seinfield 8:00 TV Guide Show time Shows Times Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

In Skull beneath the Skin, What problem did Green and Benyon seek to solve?

Notations In the paper Skull beneath skin, Green & Benyon adapt Entity-Relationship Modeling notation Entities Relationships Attributes Different modeling languages use different notations Example: UML, ER, OMT, etc. Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Notation Entities Attributes Relationships Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Relationships more Relationships can have a degree 1 to 1 1 to M M to M Relationships can mandatory or optional Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Let’s work some examples on the board What does the grid for the TV Guide look like? How could we represent shows? How could we represent times? How could we represent the relationship between the two? Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Break

Exercise: Reverse engineer a conceptual model for dmoz http://dmoz.org/Sports/Skiing/ What are the entities? What are the relationships? What are the attributes? What operations can be applied to the entities? Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Exercise: Develop a conceptual model for this scenario Jill is a historian. She wants to help people understand how natural and built environments have changed over time. To do this she wants to develop a site which will allow people to match old photographs of buildings, landscapes, etc. to new photographs. Jill wants people to see, touch, and experience ‘change’. Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Quiz #1 Good work on the quiz Everyone received max points for Lydia - Your answers will come in handy when you interview for jobs! Everyone received max points for Describe a conceptual model for TV Guide. Lydia Comments… Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Copyright David Hendry (INFO-440 session 8 - 10/23/2002)

Next week Topics Two readings Interactive design project More on conceptual modeling Begin interaction design Metaphors and visual formalisms Two readings See syllabus Interactive design project Proposal due: Oct 28 (Monday) Copyright David Hendry (INFO-440 session 8 - 10/23/2002)