Systems Analysis and Design Kendall & Kendall

Slides:



Advertisements
Similar presentations
More Diagramming & Practice with Relationship Modeling
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
Chapters 7 & 9 System Scope
Using Data Flow Diagrams
Chapter 7 Structuring System Process Requirements
Using Dataflow Diagrams
Systems Analysis and Design, 7e Kendall & Kendall
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 2 Kendall & Kendall Systems Analysis and Design, 9e Understanding.
Systems Analysis and Design in a Changing World, Fourth Edition
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
Topics Creating DFD Physical and logical DFD Event driven modeling
Chapter 3 Managing the Information Systems Project
Structuring System Requirements: Process Modeling
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
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 7 Using Data Flow Diagrams
Modeling the Processes and Logic
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.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
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.
Chapter 7: The Object-Oriented Approach to Requirements
Concepts in Enterprise Resource Planning 2 nd Edition Chapter 1 Business Functions, Processes, and 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.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Chapter 6 The Traditional Approach to Requirements
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
Systems Analysis and Design in a Changing World, Fifth Edition
Phase 2: Systems Analysis
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 2 Understanding Organizational Style and Its Impact on Information Systems Systems Analysis and Design Kendall & Kendall Sixth Edition.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Chapter 9 Moving to Design
10 ITK261 The traditional approach to design Reading: Chapter 10 Oct 9, 11.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Information System InformationSystemKnowledgedata.
Understanding and Modeling Organizational Systems
Using Dataflow Diagrams – Part 1 Systems Analysis and Design, 7e Kendall & Kendall 7 © 2008 Pearson Prentice Hall.
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.
Information System Analysis Topic-2. Data Gathering Observations Questionnaires Interviews.
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)
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
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.
Systems Analysis and Design in a Changing World, Fourth Edition
Information Systems in Organizations 2. 1
Data Dictionaries ER Diagram.
Systems Analysis and Design Kendall & Kendall Sixth Edition
Information Systems in Organizations 2. 1
Requirement Analysis using
Systems Analysis and Design Kendall and Kendall Fifth Edition
Presentation transcript:

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

Major Topics Organizational environment Nature of systems Context-level data flow diagram Entity-relationship diagram Levels of management Organizational culture

Organizations Organizations are composed of interrelated and interdependent subsystems. System and subsystem boundaries and environments impact on information system analysis and design.

Organizational Environment Community environment Geographical Demographics (education, income) Economic environment Market factors Competition Political environment State and local government

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.

Tue 13-10 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.

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.

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.

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.

Context-Level DFD Symbols Entity, a person, group, department, or system that supplies or receives information. It is labeled with a noun.

Context-Level DFD Symbols (Continued) Process, representing the entire system. It is given the number 0.

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.

Data Flow Example

Wed 14-10 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.

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.

Fundamental Entity Describes a person, place, or thing. Symbol is a rectangle.

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.

Attributive Entity Describes attributes and repeating groups. Symbol is an oval in a rectangle.

Figure 2.9 Three different types of entities used in E-R diagrams Different symbols are used to represent different types of entities. An associative entity can only exist if it is connected to at least two other entities. An attributive entity is used when we want to show data that are completely dependent on the existence of an fundamental entity.

Figure 2-12 A more complete E-R diagram showing data attributes of the entities

Thu 15-10 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.

Figure 2.8 Examples of different types of relationships in E-R diagrams

Relationship Notation One is indicated by a short vertical line. Many is indicated by a crows foot.

Entity Relationship Example

Attributes Data attributes may be added to the diagram.

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.

Levels of Management

Managerial Control The three levels of managerial control are: Operations management. Middle management. Strategic management.

Operations Management Make decisions using predetermined rules that have predictable outcomes make decisions. Oversee the operating details of the organization. dependent on internal information.

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.

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.

Managerial Levels Each of the three levels of management have: Different organization structure. Leadership style. Technological considerations. Organization culture. Human interaction. All carry implications for the analysis and design of information systems.

Organizational Culture Organizations have cultures and subcultures. Learn from verbal and nonverbal symbolism.

Verbal Symbolism Using language to convey: Myths. Metaphors. Visions. Humor.

Nonverbal Symbolism Shared artifacts Rites and rituals Clothing worn Trophies, etc. Rites and rituals Promotions Birthdays, etc. Clothing worn Office placement and decorations