Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition.

Slides:



Advertisements
Similar presentations
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Managing Information Technology 6 th Edition CHAPTER 9 BASIC INFORMATION SYSTEMS.
Advertisements

Chapters 7 & 9 System Scope
Using Data Flow Diagrams
Using Dataflow Diagrams
© 2005 by Prentice Hall 7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Systems Analysis and Design, 7e Kendall & Kendall
Chapter 4 Enterprise Modeling.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 2 Kendall & Kendall Systems Analysis and Design, 9e Understanding.
Chapter 7 Using Data Flow Diagrams
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Understanding and Modeling Organizational Systems Systems Analysis and Design, 8e.
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall © 2005 Pearson Prentice.
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Using Dataflow Diagrams
Systems Analysis and Design Kendall & Kendall Sixth Edition
Chapter 7 Using Data Flow Diagrams
Chapter 3 Managing the Information Systems Project
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 2 Topics –Context-Level DFD –Entity-Relationship Diagrams.
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall and Kendall Fifth Edition.
Chapter 9 Using Data Flow Diagrams
Chapter 7 Using Data Flow Diagrams
Use Case Modeling.
Chapter 8 Structuring System Data Requirements
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Systems Analysis and Design Kendall & Kendall
ER Diagram Notation. E-R Diagram: Chen Model Entity – represented by a rectangle with its name in capital letters. Relationships – represented by an active.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Chapter 7 Structuring System Process Requirements
 An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database.  An Entity Relationship.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition.
IS 320 Systems Analysis and Design Notes for Textbook Chapter 2
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Systems Analysis and Design Kendall & Kendall Sixth Edition
Database Design Using the REA Data Model
Using Dataflow Diagrams – Part 2 Systems Analysis and Design, 7e Kendall & Kendall 7 © 2008 Pearson Prentice Hall.
Chapter 7 Structuring System Process Requirements
Chapter 7 Using Data Flow Diagrams
Chapter 9 Designing Databases Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Information System InformationSystemKnowledgedata.
Chapter 13 Designing Databases Systems Analysis and Design Kendall & Kendall Sixth Edition.
Using Dataflow Diagrams – Part 1 Systems Analysis and Design, 7e Kendall & Kendall 7 © 2008 Pearson Prentice Hall.
IS3320 Developing and Using Management Information Systems Lecture 16: Data-Flow Diagrams 1 (Intro to Context-Level diagrams) Rob Gleasure
Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design, 7e Kendall & Kendall CH#2 ©2008 Pearson Prentice.
Software Analysis 1 PROCESS MODELING: Data Flow Diagrams (DFDs)
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Kendall & KendallCopyright © 2014 Pearson Education 2 Kendall & Kendall Systems Analysis and Design, Global Edition, 9e Understanding and Modeling Organizational.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Using Dataflow Diagrams Systems Analysis and Design, 8e Kendall & Kendall 7.
MIS 360: System Analysis and Design Dr. Qasem Al-Radaideh Department of Computer Information Systems Faculty of Information Technology Yarmouk University.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Chapter 6 Structuring System Requirements: Process Modeling
Chapter 6 Structuring System Requirements: Process Modeling
Data Dictionaries ER Diagram.
Systems Analysis and Design Kendall & Kendall Sixth Edition
Chapter 6 Structuring System Requirements: Process Modeling
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
G063 - Data flow diagrams.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Systems Analysis and Design Kendall and Kendall Fifth Edition
Presentation transcript:

Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition

Kendall & Kendall 2005 Pearson Prentice Hall 2-2 Major Topics Organizational environment Nature of systems Context-level data flow diagram Entity-relationship diagram Levels of management Organizational culture

Kendall & Kendall 2005 Pearson Prentice Hall 2-3 Organizations Organizations are composed of interrelated and interdependent subsystems. System and subsystem boundaries and environments impact on information system analysis and design.

Kendall & Kendall 2005 Pearson Prentice Hall 2-4 A SYSTEMS PERSPECTIVE output input boundary THE ENVIRONMENT interfaces interrelationship subsystems THE SYSTEM

Kendall & Kendall 2005 Pearson Prentice Hall 2-5 Organizational Environment Community environment Geographical Demographics (education, income) Economic environment Market factors Competition Political environment State and local government

Kendall & Kendall 2005 Pearson Prentice Hall 2-6 Open and Closed Systems Systems are described as either Open Free-flowing information. Output from one system becomes input to another. Closed with restricted access to information Limited by numerous rules. Information on a need to know basis.

Kendall & Kendall 2005 Pearson Prentice Hall 2-7 Context-Level Data Flow Diagram (DFD) A context-level data flow diagram is an important tool for showing data used and information produced by a system. It provides an overview of the setting or environment the system exists within: which entities supply and receive data/information.

Kendall & Kendall 2005 Pearson Prentice Hall 2-8 Data Flow Example

Kendall & Kendall 2005 Pearson Prentice Hall 2-9 Context-Level DFD Symbols Entity, a person, group, department, or system that supplies or receives information. It is labeled with a noun.

Kendall & Kendall 2005 Pearson Prentice Hall 2-10 Context-Level DFD Symbols (Continued) Process, representing the entire system. It is given the number 0.

Kendall & Kendall 2005 Pearson Prentice Hall 2-11 Context-Level DFD Symbols (Continued) Data flow, represented by an arrow. It shows information that passes to or from the process. Data flow is labeled with a noun.

Kendall & Kendall 2005 Pearson Prentice Hall 2-12 Entity-Relationship Diagrams (E-R Diagrams) Entity-relationship diagrams help the analyst understand the organizational system and the data stored by the organization. Symbols are used to represent entities and relationships.

Kendall & Kendall 2005 Pearson Prentice Hall 2-13

Kendall & Kendall 2005 Pearson Prentice Hall 2-14 Entities There are three types of entities: Fundamental entity, describing a person, place, or thing. Associative entity, linking entities. Attributive entity, to describe attributes and repeating groups.

Kendall & Kendall 2005 Pearson Prentice Hall 2-15 Fundamental Entity Describes a person, place, or thing. Symbol is a rectangle.

Kendall & Kendall 2005 Pearson Prentice Hall 2-16 Associative Entity Joins two entities. Can only exist between two entities. Symbol is a diamond inside a rectangle.

Kendall & Kendall 2005 Pearson Prentice Hall 2-17 Attributive Entity Describes attributes and repeating groups. Symbol is an oval in a rectangle.

Kendall & Kendall 2005 Pearson Prentice Hall 2-18 Relationships Relationships show how the entities are connected. There are three types of relationships: One to one. One to many. Many to many. Relationship lines are labeled.

Kendall & Kendall 2005 Pearson Prentice Hall 2-19 Relationship Notation One is indicated by a short vertical line. Many is indicated by a crows foot.

Kendall & Kendall 2005 Pearson Prentice Hall 2-20 Entity Relationship Example

Kendall & Kendall 2005 Pearson Prentice Hall 2-21 Attributes Data attributes may be added to the diagram.

Kendall & Kendall 2005 Pearson Prentice Hall 2-22

Kendall & Kendall 2005 Pearson Prentice Hall 2-23 Creating Entity-Relationship Diagrams Steps used to create E-R diagrams: List the entities in the organization. Choose key entities to narrow the scope of the problem. Identify what the primary entity should be. Confirm the results of the above through data gathering.

Kendall & Kendall 2005 Pearson Prentice Hall 2-24 Levels of Management

Kendall & Kendall 2005 Pearson Prentice Hall 2-25 Operations Management Make decisions using predetermined rules that have predictable outcomes make decisions. Oversee the operating details of the organization. dependent on internal information.

Kendall & Kendall 2005 Pearson Prentice Hall 2-26 Middle Management Make short-term planning and control decisions about resources and organizational objectives. Decisions may be partly operational and partly strategic. Decisions are dependent on internal information, both historical and prediction oriented.

Kendall & Kendall 2005 Pearson Prentice Hall 2-27 Strategic Management Look outward from the organization to the future. Make decisions that will guide middle and operations managers. Work in highly uncertain decision- making environment. Define the organization as a whole. Often make one-time decisions.

Kendall & Kendall 2005 Pearson Prentice Hall 2-28 Organizational Culture Organizations have cultures and subcultures. Learn from verbal and nonverbal symbolism. Often competing cultures. Cultures affect how people use information and information systems.