Management Information Systems

Slides:



Advertisements
Similar presentations
Database Systems: Design, Implementation, and Management Tenth Edition
Advertisements

Chapter 7 Structuring System Process Requirements
Chapter 4 Enterprise Modeling.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
Management Information Systems MBA (II) Final Semester Lectures 4,5,6 Course Lecturer: Farhan Mir.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
© Copyright Eliyahu Brutman Programming Techniques Course.
Modules, Hierarchy Charts, and Documentation
Modeling the Processes and Logic
The Islamic University of Gaza
Introduction to Systems Analysis and Design
Chapter 7 Structuring System Process Requirements
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 7: The Object-Oriented Approach to Requirements
Traditional Approach to Requirements Data Flow Diagram (DFD)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Management Information Systems
USE Case Model.
Systems Analysis and Design in a Changing World, Fifth Edition
Modeling System Requirements:Events and Things
IT 244 Database Management System Data Modeling 1 Ref: A First Course in Database System Jeffrey D Ullman & Jennifer Widom.
Chapter 6 The Traditional Approach to Requirements
System Analysis & Design Introduction: System Analysis and design course intents to help students understand its importance in developing systems that.
Systems Analysis and Design in a Changing World, Fifth Edition
Data Flow Diagrams.
Lecture 6 Data Flow Modeling
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Chapter 7 System models.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
6 Systems Analysis and Design in a Changing World, Fifth Edition.
Big Ideas Differentiation Frames with Icons. 1. Number Uses, Classification, and Representation- Numbers can be used for different purposes, and numbers.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Management Information System Ghulam Yasin Lecturer Institute of Business Administration.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
section II Analysis Systems Analysis and Design
1 Prof. Dr. Nizamettin AYDIN
6 Systems Analysis and Design in a Changing World, Fourth Edition.
E-Learning: components of e-learning Mohammed Hassan 1.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
UML Diagrams By Daniel Damaris Novarianto S..
Systems Analysis and Design in a Changing World, Fourth Edition
ITEC 3220A Using and Designing Database Systems
Object-Oriented Analysis and Design
Unified Modeling Language
System Design.
UML Diagrams Jung Woo.
Abstract descriptions of systems whose requirements are being analysed
System models October 5, 2005.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Presentation transcript:

Management Information Systems Charles Parker 2nd Edition Chapter 3: System & Models Prepared By: Hamad Raza (Lecturer GCUF)

Systems A system is made up of a number of parts combined in a particular way to do something useful. We think of the combined parts as a single thing and we give it a name. Wheels, axles, pedals, gears, chain, seat and handlebars are combined to form a single whole we call a bicycle. A bike is a system when all the parts are connected correctly because it allows the rider to move from one place to another more easily.

Systems A system is a set of integrated elements that collectively work together to achieve some common purpose or goal. For Example: A football games is played according to the system that is composed of such elements as teams, stadiums, equipment, referees and rules. A CBIS is a collection of people, hardware, software, data & procedures that interact to provide timely data and information, both internally and externally to authorized people who need it.

Components of a System A system component / element can be tangible object such as a car or a person, an abstract concept such as data or information, or an event such as March 23 or “groundbreaking ceremony”. Tangible objects of course are those objects that we can touch or measure. Abstract concepts & events are intangible.

Components of a System When classifying systems, we frequently differentiate between a system’s logical description & physical description. Logical description of a system is a representation that specifies essential system elements in broad, often abstract terms. A physical description of the same system would be much more precise about how it is actually implemented.

System Environment All systems function within some sort of environment. The environment, like the system, is a collection of elements. These elements surround the system and often interact with it. Systems are normally delimited by a boundary, which separates them from their environment. Anything within the boundary is part of the system; Anything outside is a part of the environment.

Open Versus Closed Systems Systems are often classified as open or closed. A closed system is self-contained and does not interact or make exchanges across its boundaries with its environment. In other words, a closed system is one that has no interaction with any element not contained in it. An open system is one that interacts and makes exchanges with its environment. Most of the systems that occur naturally in business are open systems, and they interact with such environmental elements as consumers, suppliers, competitors, government and foreign countries.

Systems Models When studying system, it is often convenient to represent them in the form of a model. What is a Model? A Presentation of a real world elements and the relationship among them. For Example: 777 is a physical model of plane. The equation “Area = Length * Width” is a math model for calculating the internal area of rectangle. Porter’s five forces Model, Management level’s Model etc. Why we need Models The field of MIS uses many Models. Because management information system are often complex, it help to have a few models that simplify and clarify them.

General Versus Specific Models Models can be classified in many ways. One way concerns how general or specific the models are: General models are models that can be applied to wide variety of settings. Specific models are those that apply to a specific situation. For Example: Many of the graphical models Like Management Hierarchy Chart is a general model that can represent virtually any type of organization.

Types of Models Models can be classified in several other ways. These are: Graphical Models are models generally use such symbols as icons, boxes and lines to represent real-world elements and the relationships among them.

Types of Models Graphical Models (Cont.) Data flow diagrams (DFD) are widely used by systems analysts to graphically illustrate information systems. These graphical models show how data or information move from one process to another in an organizational system. These are useful for showing how systems work and are often used by systems analysts both to design systems & to clarify to users, programmers and other system analysts how components of a system fit together.

Types of Models Graphical Models (Cont.) Data flow diagrams (DFD)

Types of Models Mathematical Models A mathematical model is used to express quantifiable phenomena in mathematical terms. Q = economic order quantity of specific product D = annual usage of the product S = the cost of placing an individual order P = Price for the product H = Unit cost of carrying items in inventory

Types of Models Narrative Models A Narrative models describes system without trying to illustrate it in a formula or graph. For Example: A written description of a worker’s job duties. Physical Models A physical model is usually a three-dimensional representation that can be held or touched. For Example: System prototype is a physical model. A prototype is a small “pilot” model of a hardware or software system that is used to guide the systems analyst in building a larger system.

Who is responsible for Developing Models? Graphical & Narrative models of CBIS are usually constructed by system analysts. Whereas Mathematical models are commonly created by the operations research or management science staff, who are specially trained in building mathematical models.