Information System InformationSystemKnowledgedata.

Slides:



Advertisements
Similar presentations
Level 1 Recall Recall of a fact, information, or procedure. Level 2 Skill/Concept Use information or conceptual knowledge, two or more steps, etc. Level.
Advertisements

16 key concepts.
What is Knowledge (& Innovation)? What is Political Economy? Possible Conceptual Approaches David F. J. Campbell Universität Klagenfurt / iff Fakultät.
Information Systems in Business
INTRODUCTION TO MODELING
Systems Analysis and Design, 7e Kendall & Kendall
Chapter 4 Enterprise Modeling.
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Systems Development Life Cycle
Modeling Human Reasoning About Meta-Information Presented By: Scott Langevin Jingsong Wang.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Chapter 3 Database Management
Artificial Intelligence
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall © 2005 Pearson Prentice.
Systems Analysis and Design Kendall & Kendall Sixth Edition
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall and Kendall Fifth Edition.
Systems Analysis and Design Kendall & Kendall
Knowledge; How to get it from YOUR brain to HIS/HER brain?
Database Design Using the REA Data Model
6 Systems Analysis and Design in a Changing World, Fourth Edition.
 An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database.  An Entity Relationship.
Traditional Approach to Requirements Data Flow Diagram (DFD)
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
IS 320 Systems Analysis and Design Notes for Textbook Chapter 2
Systems Analysis and Design Kendall & Kendall Sixth Edition
Chapter 17 Database Design Using the REA Data Model Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 17-1.
Chapter 17 Database Design Using the REA Data Model Copyright © 2012 Pearson Education 17-1.
Business Analysis and Essential Competencies
Author: Lornet LD team Reuse freely – Just quote Desired Properties of a MOT Graphic Representation Formalism Simplicity and User Friendliness (win spec,
Basic Concepts in Management. Management Types All manager’s job are not the same. Managers are responsible for different departments, work at different.
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition.
Standards for Mathematical Practice #1 Make sense of problems and persevere in solving them. I can: explain the meaning of a problem. choose the right.
1–1 Chapter 1 INTRODUCTION TO MANAGEMENT AND ORGANIZATIONS © Prentice Hall, 2002.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
DataBase Management Systems Introduction to Database Technology EAK 362/2 MIS LECTURE 4 PART 1.
Structured Analysis.
Big Ideas Differentiation Frames with Icons. 1. Number Uses, Classification, and Representation- Numbers can be used for different purposes, and numbers.
1 Introduction to Software Engineering Lecture 1.
Mindful Shift Chapter 12. “Of all species on earth, we human have the capacity of mind change: we change our minds and that of others”
Fanny Widadie, S.P, M.Agr 1 Database Management Systems.
The Nature of Knowledge
Topics Covered:  System System  Sub system Sub system  Characteristics of System Characteristics of System  Elements of Systems Elements of Systems.
CHAPTER 1 – INTRODUCTION TO THE FIELD OF ORGANIZATIONAL BEHAVIOR By Michael Beaudoin & Leon Ngo.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
CS311 Database Management system Somchai Thangsathityangkul 1.
1 Database Systems Entity Relationship (E-R) Modeling.
Major Science Project Process A blueprint for experiment success.
Entity-Relationship Diagram Presentation Gianna-lee Williams 6AQ Ms. Anderson.
Entity relationship diagram Name: Quian Crosby Form:6AQ Subject: Information Technology Teacher: Ms. D. Anderson.
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition.
2 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Data Models Why data models are important About the basic data-modeling.
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design, 7e Kendall & Kendall CH#2 ©2008 Pearson Prentice.
3.1 CSC 102 Introduction to Information Systems Databases.
Teanna Clarke 6aQ What is a Entity-Relationship Diagram?  An Entity-Relationship Diagram (ERD) is a tool that graphically shows the connections among.
FUNCTIONAL MODELING Alajas, Sophiya Ann Allego, Keefer Lloyd Maningo, Patrick Sage Pleños, John Enrick CPE 51ASATURDAY 7:30 – 10:30ENGR. ARNOLD ROSO.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Rationale Databases are an integral part of an organization. Aspiring Database Developers should be able to efficiently design and implement databases.
Lecturer: Dr Mohammad Nabil Almunawar Foundations of Information Systems in Business.
Operations Research Chapter one.
Chapter 6 The Traditional Approach to Requirements.
OVERVIEW OF SYSTEM ANALYS AND DESIGN
What’s distinctive about the study of human geography?
Data Information Knowledge and Processing
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Presentation transcript:

Information System InformationSystemKnowledgedata

3/5/2002e-business and Information Systems2 Information n concept n constraint n communication n control n form n instruction n knowledge n meaning, mental stimulus n pattern n perception n representation

3/5/2002e-business and Information Systems3 Knowledge n expertise, and skills acquired by a person through experience or education n the theoretical or practical understanding of a subject, what is known in a particular field or in total n facts and information or awareness or familiarity gained by experience of a fact or situation n Philosophical debates in general start with Plato's formulation of knowledge as "justified true belief". There is however no single agreed definition of knowledge presently, nor any prospect of one, and there remain numerous competing theories.

3/5/2002e-business and Information Systems4 Data n Collection of facts as the result of –experience –observation –experiment n This may consist of –numbers –words –images

3/5/2002e-business and Information Systems5 Information/Data n Information is an useful environment status n Data is a materialized information n Data is an artifact – human made

3/5/2002e-business and Information Systems6 System n Interacting/interrelated components n interdependent components n real or abstract n forming an integrated whole – has boundary – input – output

3/5/2002e-business and Information Systems7 Examples n Banking system n Education system n Transportation system n Computer system

3/5/2002e-business and Information Systems8 Graphic Model of a System n Context-level data flow diagram n Entity-Relationship Diagram n Use Case Model

3/5/2002e-business and Information Systems9 Context-Level Data Flow Model n Context-level data flow diagram – Process – Entity – Data flow

3/5/2002e-business and Information Systems10 Entity-Relationship Model n Entity-Relationship Diagram – Entity – Relationship n one-to-one n one-to-many n many-to-many

3/5/2002e-business and Information Systems11 Use Case Model n Use Case diagram – Actor – Use Case Symbol – Connecting line

3/5/2002e-business and Information Systems12 Management Levels n Levels of management – Strategic level – Managerial level n planning n control – Operational level n base on predetermined rules

3/5/2002e-business and Information Systems13 Strategic Level Make decisions on – long-term goal – multiple decision objectives

3/5/2002e-business and Information Systems14 Managerial Level Make decision on – short-term planning –control n resources n forecasting future resources n solving employee problems Partly Operational Partly Strategic

3/5/2002e-business and Information Systems15 Operational Level Make decisions n based on predetermined rules – single decision objective n that affect implementation in – work scheduling – inventory control – shipping – receiving – control of processes (such as production)