Information Systems in Organizations 2.1 Analyzing organizations as systems and processes.

Slides:



Advertisements
Similar presentations
Business Processes, Data Modeling and Information Systems
Advertisements

BIS 360 – Lecture Seven Process Modeling (Chapter 8)
MIS 210 Fall 2004Sylnovie Merchant, Ph. D. Lecture 4: Data Modeling Process Modeling MIS 210 Information Systems I.
1 Database Requirements and Design. 2 DATA PEOPLE PROCEDURES HARDWARE SOFTWARE The Product: a working system.
Chapter 5: Modeling Systems Requirements: Events and Things
Information Systems in Organizations 2
CSE 441: Systems Analysis & Design
Introduction to Transaction Processing and Documentation Techniques COPYRIGHT © 2007 Thomson South-Western, a part of The Thomson Corporation. Thomson,
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes.
Information Systems in Organizations Gaming and Entertainment (e.g., Xbox, fantasy leagues, Roku) Mobile (Smartphones)
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Information Systems in Organizations 2
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
Exam 1 Review. Bureau of Labor Statistics, U.S. Department of Labor, Occupational Outlook Handbook, Edition, Computer and Information Systems.
Information Systems in Organizations 2.2 Systems Architecture: Devices, Network, Data and Apps.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
1 Introduction to Design. 2 Outline Basics of design Design approaches.
Information Systems in Organizations 2.2 Systems Architecture: Devices, Network, Data and Apps.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes.
Reminders Gradebook (Activity and Assignment Grades) Midterm Exam #1 Review Session – Tuesday, February 9th, from 3:00 - 4:00 pm in Alter Hall Room 748.
Exam Study Guide: Unit 1: Intro to MIS 1.1. The modern organization is a system and set of processes Evolution of organizational systems from start-up.
CSE 441: Systems Analysis & Design Basic CASE Models of Visible Analyst Lab2 Yusuf Altunel.
Information Systems in Organizations 2.2 Systems Architecture: Devices, Network, Data and Apps.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes.
Review Business Analyst vs. Systems Analyst – A Business Analyst identifies a problem and states – in business terms -- what the solution is. They define.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes & Modeling Processes with Swimlane Diagrams.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
Information Systems in Organizations 2
Information Systems in Organizations 2
Roadmap Week 1: Intro to MIS Week 2: Systems Analysis
Information Systems in Organizations 2
Entity Relationship Diagram
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2
Database Requirements and Design
Process & Logic Modeling
Information Systems in Organizations 2. 1
Entity Relationship Diagrams - 1
Information Systems in Organizations 2
Information Systems in Organizations 2
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2
Information Systems in Organizations 2. 1
Entity Relationship Diagrams - 2
Information Systems in Organizations 2
Information Systems in Organizations 2
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Entity Relationship Diagrams - 2
Tracking Customer and Service Information
Information Systems in Organizations 2
Information Systems in Organizations 2. 1
Information Systems in Organizations 2
Information Systems in Organizations 2
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2
Information Systems in Organizations 2
Presentation transcript:

Information Systems in Organizations 2.1 Analyzing organizations as systems and processes

Course Topics Overview Unit 1: Introduction Unit 2: Systems Analysis Unit 3: Organizational Systems Unit 4: Consumer Systems 2

Unit 2: Systems Analysis 2.Systems analysis: what makes a system tick? 2.1. Analyzing organizations as systems and processes Process decomposition: swim lane diagrams Data modeling: entity relationship diagrams 2.2. Systems architecture: devices, network, data, apps Visualizing architecture: conceptual diagramming Ex. of legacy, contemporary, and future information systems 3

? What is “systems analysis”? What is “systems architecture”? Problem Solving Technique Decomposition Business Process Modeling What is the problem? What is the solution?

Systems Analysis "Systems analysis is a problem solving technique that decomposes a system into its component pieces for the purpose of the studying how well those component parts work and interact to accomplish their purpose" - Wikipedia [ [ "the process of studying a procedure or business in order to identify its goals and purposes and create systems and procedures that will achieve them in an efficient way“ – Merriam-Webster Dictionary So what does a systems analyst do?

Systems Architecture Systems Architecture is a generic discipline to handle objects (existing or to be created) called "systems", in a way that supports reasoning about the structural properties of these objects. Systems Architecture is a response to the conceptual and practical difficulties of the description and the design of complex systems. – Boris Golden Once a systems analyst understands the business problem, they architect a solution

? What is a “swim lane diagram”? How is a process performed? Who does what? When do they do it? What happens before? What happens after?

Swim Lane Diagram Who does what and when?

? Give me a process and let’s make a swim lane diagram…

Learn IT #4 The deliverable for this assignment is a one page swim lane diagram for drive-through ordering at a fast food restaurant. 11

? What is an “entity relationship diagram”? Entity = Noun Relationship = Verb Attribute = Characteristic Data Model

Entity Relationship Diagram (ERD)

Primary ERD Symbols

Inventory Item Attributes ID Name Description Unit of Measure Weight Serial #

Internal ID Name Display Name Description Purchase Description Vendor Name Store Display Name Store Description Units Type Stock Unit Purchase Unit Sale Unit Display in Web Site Purchase Price Preferred Vendor Base Price List Price Online Price Income Account Asset Account Expense/COGS Account Costing Method On Special Tax Schedule On Hand Available On Order Committed Back Ordered Reorder Point Preferred Stock Level Reorder Multiple Drop Ship Item Special Order Item Copy SO Description Weight Weight Units Class Business Unit Date Created Last Modified Inventory Item Attributes

? Let’s model the data that is used by the process we modeled earlier…

Unit 2: Systems Analysis 2.Systems analysis: what makes a system tick? 2.1. Analyzing organizations as systems and processes Process decomposition: swim lane diagrams Data modeling: entity relationship diagrams 2.2. Systems architecture: devices, network, data, apps Visualizing architecture: conceptual diagramming Ex. of legacy, contemporary, and future information systems 18