1ENMA 6010: System Modeling, Simulation, and Analysis - Overview © 2009 – Mark Polczynski All rights reserved.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Alternative Approach to Systems Analysis Structured analysis
Chapter 7 Structuring System Process Requirements
OASIS Reference Model for Service Oriented Architecture 1.0
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Capturing the requirements
Analysis Modeling Over view of today’s lesson T he analysis model is the first technical representation of a system. Analysis modeling uses a combination.
Lecture 13 Revision IMS Systems Analysis and Design.
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Overview of Software Requirements
© Copyright Eliyahu Brutman Programming Techniques Course.
Modeling the Processes and Logic
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
Modeling System Functions
SYSTEMS ANALYSIS. Chapter Five Systems Analysis Define systems analysis Describe the preliminary investigation, problem analysis, requirements analysis,
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
Chapter 7 Structuring System Process Requirements
6 Systems Analysis and Design in a Changing World, Fourth Edition.
ENMA 6010: State Transition Diagrams1 ENMA 6010 State Transition Diagrams Modeling Time-Dependent Behavior Reference: Wikipedia – State Transition DiagramsState.
Chapter 6: The Traditional Approach to Requirements
Modeling and Simulation
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
The Software Development Life Cycle: An Overview
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
S/W Project Management
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
Managing the development and purchase of information systems (Part 1)
1 Validation & Verification Chapter VALIDATION & VERIFICATION Very Difficult Very Important Conceptually distinct, but performed simultaneously.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
Chapter 7 Structuring System Process Requirements
Mohammad Amin Kuhail M.Sc. (York, UK) University of Palestine Faculty of Engineering and Urban planning Software Engineering department Requirements Engineering.
ITEC224 Database Programming
Business Analysis and Essential Competencies
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition Irwin/McGraw-Hill.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition Irwin/McGraw-Hill.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Sept. 18, 2003CS WPI1 CS 509 Design of Software Systems Lecture #3 Thursday, Sept. 18, 2003.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Systems Analysis and Design in a Changing World, Fourth Edition
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Smart Home Technologies
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Chapter 11  2000 by Prentice Hall System Analysis and Design: Methodologies and Tools Uma Gupta Introduction to Information Systems.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
Software Engineering Lecture 10: System Engineering.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
WELCOME TO OUR PRESENTATION UNIFIED MODELING LANGUAGE (UML)
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Unified Modeling Language
Overview of System Engineering
OO Design and Development
CS 8532: Advanced Software Engineering
Chapter 4 System Modeling.
Presentation transcript:

1ENMA 6010: System Modeling, Simulation, and Analysis - Overview © 2009 – Mark Polczynski All rights reserved

BA (Before AutoCad) People have been building amazingly complex systems for a long time. In the old days, for example, ship designs often consisted of exact scale models. Basically, the designer said: Build a ship exactly like this, (except bigger). Today, these models adorn the shelves of maritime museums and hobby shops. But originally, these models were essential to system design and construction. 2ENMA 6010: System Modeling, Simulation, and Analysis - Overview

3 Modern System Design Today, being much advanced over our ancestors, we generally say: “Build a system something like this…” And, what we get, of course, is something like the system we want. Now, technological advances enable us to conceive of ever-larger systems of ever-increasing complexity and interdependency. The result is that often the systems we are designing and building deviate further and further from what it is that we originally imagined.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview4 The complexity of the systems we are building is approaching that of human behavior. For these systems, we have incomplete a-priori knowledge of: Nature - design/function: How a particular system would behave under all possible expected and unexpected conditions. Nurture - environment/history: How previous and current external factors cause temporary and permanent changes in the behavior of a system. Growth - changes in nature and nurture: How the behavior of the system will be required to change over time in order to remain viable. Complex systems can behave as irrationally as people!

ENMA 6010: System Modeling, Simulation, and Analysis - Overview5 Like human beings, system behaviors can be: - Difficult to understand and predict, - Often appear illogical, inconsistent, even self-destructive. For complex systems, it is difficult to understand and predict: All cause/effect relationships, Among multiple subsystems, And/or interacting systems, That may have contrary goals, And goals that are constantly changing.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview6 Problem : As systems become larger, more complex, and more interdependent, the task of conceptualizing and specifying function and design increases dramatically. Solution : Go back to the old ways! The basic premise of this course is that the best design specification for large complex systems is a descriptive model of the system. This course is all about: Modeling, simulating, and analyzing systems… In ways that completely and accurately capture the behavior of the desired system implementation.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview7 What is this course NOT about? This course is not about AutoCad, Simulink, or rapid prototyping. These topics are well-covered by the Mechanical Engineering Department. Rather, we cover a wide range of general tools from many different disciplines which can be used to model, simulate, and analyze large complex systems. The intent is to provide the current or perspective engineering manager with an overview of a wide range of tools in the system modeling toolbox. This will help the student: Understand the strengths and limitations of available tools, Select appropriate tools, Evaluate the results of using the tools.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview8 What this course is NOT about – Part 2 This course is not about training expert practitioners in the use of the tools covered. In fact, it is assumed that as engineering managers, students may never themselves actually apply the tools. However, as managers, students can be expected to manage teams and/or projects that utilize these tools. To that end, this course provides the student with the chance to apply the tools to real-world problems, Thereby providing the understanding and technical credibility to effectively manage the use of such tools.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview 9 Goals of System Modeling: 1.To focus on important system features while downplaying less important features, 2.To verify that we understand the user’s environment, 3.To discuss changes and corrections to the user’s requirements at low cost and with minimal risk, 4.To verify that we have documented our understanding in a way that would allow others to construct/maintain the system.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview 10 Characteristics of Good Models: 1.Graphical, with support for detailed text descriptions: Picture is worth a thousand words  picture links to a thousand words. 2.Top-down partitionable: Globe  Continents  Countries  etc… 3.Minimally redundant: Make changes in just one place in the model. 4.Transparent: Requires no expertise in model building to understand the model.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview11 Modeling tools we will be using in this course: 1.Context Diagram: Scope and boundaries of model. 2.Entity Relationship Diagram: Interactions between system elements. 3.Entity Flow Diagram: Movement of patients and materials. 4.State Transition Diagrams: Transitions between system wait states. 5.Process Flow Diagrams: Decisions controlling system behavior. 6.Causal Loop Diagram: System cause and effect relationships. 7.IBIS Analysis: Description of “fuzzy” decisions. 8.Monte Carlo Simulation: Entity flow and resource utilization.

ENMA 6010: System Modeling, Simulation, and Analysis - Overview12 State transition diagram Entity relationship diagram Process flow diagram Entity flow diagram Part 1 of this Course Part 1 of this Course

ENMA 6010: System Modeling, Simulation, and Analysis - Overview13 Danger: Because we are pulling modeling techniques from different fields, we will occasionally run into terminology conflicts, e.g.: Data flow diagram  Entity flow diagram