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

Slides:



Advertisements
Similar presentations
More Diagramming & Practice with Relationship Modeling
Advertisements

Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Managing Information Technology 6 th Edition CHAPTER 9 BASIC INFORMATION SYSTEMS.
Chapters 7 & 9 System Scope
Using Data Flow Diagrams
Using Dataflow Diagrams
Systems Analysis and Design, 7e Kendall & Kendall
ERD diagram Data Design - Mr. Ahmad Al-Ghoul
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 2 Kendall & Kendall Systems Analysis and Design, 9e Understanding.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
Chapter 7 Using Data Flow Diagrams
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition © 2005 Pearson Prentice.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Understanding and Modeling Organizational Systems Systems Analysis and Design, 8e.
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall © 2005 Pearson Prentice.
Using Dataflow Diagrams
Systems Analysis and Design Kendall & Kendall Sixth Edition
Chapter 7 Using Data Flow Diagrams
Topics Creating DFD Physical and logical DFD Event driven modeling
Chapter 17 Designing Databases
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.
System Analysis and Design
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Systems Analysis and Design Kendall & Kendall
The Traditional Approach to Requirements: Using Dataflow Diagrams Spring
DATA FLOW DIAGRAMS IT 155.
ER Diagram Notation. E-R Diagram: Chen Model Entity – represented by a rectangle with its name in capital letters. Relationships – represented by an active.
 An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database.  An Entity Relationship.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke’s Chapter Five: Data Modeling with the Entity-Relationship.
IS 320 Systems Analysis and Design Notes for Textbook Chapter 2
Data Flow Diagrams (DFDs). Data flow diagram (DFD) is a picture of the movement of data between external entities and the processes and data stores within.
Systems Analysis and Design Kendall & Kendall Sixth Edition
Database Design Using the REA Data Model
Chapter 9 Describing Process Specifications and Structured Decisions
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
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 16 Quality Assurance Through Software Engineering Systems Analysis and Design Kendall & Kendall Sixth Edition.
Chapter 9 Designing Databases Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Principles of Database Design, Part II AIMS 2710 R. Nakatsu.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Chapter 13 Designing Databases Systems Analysis and Design Kendall & Kendall Sixth Edition.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Using Dataflow Diagrams – Part 1 Systems Analysis and Design, 7e Kendall & Kendall 7 © 2008 Pearson Prentice Hall.
The Entity-Relationship Model, P. I R. Nakatsu. Data Modeling A data model is the relatively simple representation, usually graphic, of the structure.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition.
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)
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 David M. Kroenke’s Chapter Six: Transforming Data Models into Database.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
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.
Chapter 6 Structuring System Requirements: Process Modeling
Requirements Become the E-R Data Model
Data Dictionaries ER Diagram.
Systems Analysis and Design Kendall & Kendall Sixth Edition
Chapter 6 Structuring System Requirements: Process Modeling
Requirement Analysis using
Chapter 11 Describing Process Specifications and Structured Decisions
Chapter 17 Designing Databases
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 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-5 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-6 Virtual Organizations A virtual organization has parts of the organization in different physical locations. Computer networks and communications technology are used to work on projects.

Kendall & Kendall 2005 Pearson Prentice Hall 2-7 Virtual Organization Advantages Advantages of a virtual organization are: Reduced costs of physical facilities. More rapid response to customer needs. Flexibility for employees to care for children or aging parents.

Kendall & Kendall 2005 Pearson Prentice Hall 2-8 Enterprise Resource Planning Enterprise Resource Planning (ERP) describes an integrated organizational information system. The software helps the flow of information between the functional areas within the organization.

Kendall & Kendall 2005 Pearson Prentice Hall 2-9 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-10 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-11 Context-Level DFD Symbols (Continued) Process, representing the entire system. It is given the number 0.

Kendall & Kendall 2005 Pearson Prentice Hall 2-12 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-13 Data Flow Example

Kendall & Kendall 2005 Pearson Prentice Hall 2-14 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-15 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-16 Fundamental Entity Describes a person, place, or thing. Symbol is a rectangle.

Kendall & Kendall 2005 Pearson Prentice Hall 2-17 Associative Entity Joins two entities. Can only exist between two entities. Symbol is a diamond inside a rectangle. Also called a: Gerund. Junction. Intersection. Concatenated entity.

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

Kendall & Kendall 2005 Pearson Prentice Hall 2-19 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-20 Relationship Notation One is indicated by a short vertical line. Many is indicated by a crows foot.

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

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

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