IS = Parts working together to deliver information to users. The importance of the process aspect—what processes do (system functionality), and how they.

Slides:



Advertisements
Similar presentations
Systems Development Environment
Advertisements

Beyond “The System Shall...” A Journey from Good to Great Requirements.
TCS2411 Software Engineering1 System Engineering and Analysis “What is the role of the software product?”
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
Concepts of Systems Theory
Information Systems in Organizations
Fundamental System Concepts Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: September 2014.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Types of Information Systems Prepared by SYED IBRAHIM K.
Systems Analysis I Data Flow Diagrams
An Introduction to Business Process Modeling using Data Flow Diagrams
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 6 The Traditional Approach to Requirements
Chapter 13 Starting Design: Logical Architecture and UML Package Diagrams.
Systems Analysis and Design in a Changing World, Fifth Edition
Information System.
Using Dataflow Diagrams – Part 2 Systems Analysis and Design, 7e Kendall & Kendall 7 © 2008 Pearson Prentice Hall.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Information Systems in Organisations System Development: The Environment.
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Changing Perspective From Structured to Object-oriented.
System models l Abstract descriptions of systems whose requirements are being analysed.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Systems Analysis and Design in a Changing World, 3rd Edition
6 Systems Analysis and Design in a Changing World, Fifth Edition.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Chapter 1 Foundations of Information Systems in Business.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
SFDV Principles of Information Systems Lecture 5: Designing the Solution.
MANAGING DATA RESOURCES ~ pertemuan 7 ~ Oleh: Ir. Abdul Hayat, MTI.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Design CIS 4800 Kannan Mohan Department of CIS Zicklin School of Business, Baruch College Copyright © 2009 John Wiley & Sons, Inc. Copyright © 2008 Course.
INFORMATION X INFO425: Systems Design Systems Design Project Deliverable 2.
Creating Data Flow Diagrams Presenter: Ms. Somia Razzaq.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
 An Information System (IS) is a collection of interrelated components that collect, process, store, and provide as output the information needed to.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Foundations of Information Systems in Business
Different views of information system (IS) structural view (data, hardware, software/application, procedures) Object view Services view (user interface,
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Different views of information system (IS) structural view (data, hardware, software/application, procedures) Object view Services view (user interface,
Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.
MIS Systems Analysis & Design Summary Updated 2013.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Is 581 assist Inspiring Minds/is581assistdotcom FOR MORE CLASSES VISIT
CompSci 280 S Introduction to Software Development
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Chapter 5 System modeling
Chapter 5 – System Modeling
Fundamentals of Information Systems, Sixth Edition
Software Specification Tools
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
SSA(D) vs OOAD M. Pickard CSC 513.
Solution Summary Business Service Management Solution on AIX® 6.1.
Overview of System Engineering
Chapter 13 Logical Architecture.
DATA FLOW DIAGRAM.
Public Management Information Systems System Analysis & Design Tuesday, December 04, 2018 Hun Myoung Park, Ph.D. Public Management & Policy Analysis.
Chapter 13 Logical Architecture.
Texas Pipe and Supply Presentation #3.
Documenting Accounting Information Systems
Public Management Information Systems System Design Monday, July 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
UML Design for an Automated Registration System
Presentation transcript:

IS = Parts working together to deliver information to users. The importance of the process aspect—what processes do (system functionality), and how they take control over system (logic). Common View of IS: data, IT, processes, user interface What is Information System: Systems Analysis & Design Summary More…

System Services View of IS: - data processing - data management - user interface System Architecture View: IS is interrelated tiers. What is Information System Object View: system parts are object and classes; packages and components.

Systems analysis— - Analyzing organizational tasks and processes that deliver some information—application domain - Includes manual task and processes - Deliverable: Logical design The Emphasis of the Course Systems Design (some exercises, term paper)

Data Process/Functionality Logic (control, decisions) User Interface Object Interactions Data Flow Diagram Class/Object Diagram Activity Diagram Use Case Diagram Decision Table Sequence Diagram Dialogue Diagram xx x x x xxx xx x x x x x x = primary purpose a diagram is invented for = provides hints/indications Tools for Systems Analysis

Challenges in Systems Analysis What is in the system? Where is system boundary? Process thinking (DFD, Activity Diagram) vs. Non-process thinking (use case diagram) Focus on details and completeness Capability to switch between big and small pictures Capability to read (and sometimes write) different notation schemes.

Some Highlights 7 diagrams for systems analysis studied (see table) MIS Perspective emphasized: - IS delivers information that serves organizational & management purposes - Management perspective (systems examples rooted in specific organizational contexts; concern with end-users, cost-benefit, systems adoption…) More…

2 Tools: MS Project, Visio Different systems studied: sales and inventory tracking doctor appointment, , DSS prescriptions management Web storefront order management class registration… Some Highlights

Links to database management course (9.350) Data modeling (class and object diagram) – drill down on data part of class/object, not so much on methods part. Information system – the data foundation is in DB systems. IS is a more specific application, with a purpose defined by the type of data/information it delivers. That’s All Folks!