Different views of information system (IS) structural view (data, hardware, software/application, procedures) Object view Services view (user interface,

Slides:



Advertisements
Similar presentations
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Advertisements

Ch 3 System Development Environment
Information Systems Analysis and Design
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
© ABB AB, Corporate Research - 1 5/19/2015 abb Project Breakdown Structure Creation.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals State the purpose of systems design.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
Lecture 5a: Sequence Interaction Diagrams CSE 111 Copyright W. Howden1.
Concepts of Systems Theory
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Interaction Models. Interaction Definition An interaction is a behavior that comprises a set of messages exchanged among a set of objects within a context.
Fundamental System Concepts Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: September 2014.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
SE 555 Software Requirements & Specification Requirements Analysis.
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 1.1.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
RUP Requirements RUP Artifacts and Deliverables
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
INFO101: Management Information Systems INFORMATION X.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Lesson 7 Guide for Software Design Description (SDD)
CSI315 Web Applications and Technology Overview of Systems Development (342)
CS 310 Ch8: System models Abstract descriptions of systems being analyzed to help the analyst understand the system functionality communicate with customers.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
Introduction to Software Engineering
2-Oct-15 1 Introduction to Software Engineering Softwares Importance of SWE Basic SWE Concepts ICS Software Engineering.
2-Oct-15 Introduction to SWE1 Introduction to Software Engineering Softwares Importance of SWE Basic SWE Concepts.
Lecture 4 Title: The Scope Management Plan
Process Analysis Agenda  Multiple methods & perspectives There are lots of ways to map processes  Useful in many situations not just HRIS design  Preparation.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
CCT 333: Imagining the Audience in a Wired World Class 6: Qualitative Research Methods.
IS = Parts working together to deliver information to users. The importance of the process aspect—what processes do (system functionality), and how they.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
section III Design Systems Analysis and Design
Software Design Process
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
UML - Development Process 1 Software Development Process Using UML.
4+1 View Model of Software Architecture
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Different views of information system (IS) structural view (data, hardware, software/application, procedures) Object view Services view (user interface,
MIS Systems Analysis & Design Summary Updated 2013.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
Requirements Models Representing the Product in Ways Other than Text.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Chapter 5 – System Modeling
Information System Applications
CompSci 280 S Introduction to Software Development
Project Planning: Scope and the Work Breakdown Structure
Software Engineering Lecture 4 System Modeling The Analysis Stage.
System Design, Implementation and Review
Chapter 5 – System Modeling
Fundamentals of Information Systems, Sixth Edition
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Chapter 13 Logical Architecture.
Chapter 13 Logical Architecture.
UML Design for an Automated Registration System
Chapter 13 Logical Architecture.
Information system analysis and design
Presentation transcript:

Different views of information system (IS) structural view (data, hardware, software/application, procedures) Object view Services view (user interface, data management, data processing/functionality) Architecture view (tiers. modules) MIS Systems Analysis & Design Summary

Systems analysis: - Analyzing organizational tasks/processes either supported or not supported by electronic or pre-electronic IT - Deliverable: Logical design The Emphasis of the Course Systems Design (exercises, term paper)

Data Process/Functionality Logic (control, decisions) User Interface Object Interactions Class/Object Diagram Activity Diagram Use Case Diagram Sequence Diagram Dialogue Representations x x x xx x x x x x x x = primary purpose a diagram is invented for = provides hints/indications Systems Analyst’s Toolbox: System Aspects & Diagramming Tools Use Case Description x x

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

Some Highlights Diagramming tools for systems analysis studied 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 software tools: MS Project, Visio Different systems studied (customer order management, Web storefront, HR, sales/marketing) Some Highlights Guest speakers from Investors Group on experiences of system analyst That’s All Folks!