Week 7 - Systems Engineering and Analysis

Slides:



Advertisements
Similar presentations
Modeling Main issues: What do we want to build How do we write this down.
Advertisements

Principles of Engineering System Design Dr T Asokan
Chapter 3 - Modeling and Process Modeling1 Chapter 3 – Modeling and Process Modeling By Dr. Sartuk KARASOY Middle East Technical University
UML Diagrams Jung Woo. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, business.
Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.
Objectives Detailed Object-Oriented Requirements Definitions
CS3773 Software Engineering Lecture 03 UML Use Cases.
SWE Introduction to Software Engineering
©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 Real-time requirements  Intro to Software Engineering  Software Development Process Models  Formal methods in software specification  Structured.
CS 425/625 Software Engineering System Models
Analysis Modeling Instructor: Dr. Jerry Gao. Analysis Modeling Jerry Gao, Ph.D. Jan Elements of the analysis model - Data modeling - Functional.
CSC 402 Requirements Engineering 1 Requirements Techniques, cont. Formal requirements analysis techniques include: – DFD (covered) – ERD (covered) – Finite.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Lecture 6 & 7 System Models.
Modeling State-Dependent Objects Using Colored Petri Nets
Detailed Object-Oriented Requirements Definitions
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 1.
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
6 Systems Analysis and Design in a Changing World, Fourth Edition.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 6: The Traditional Approach to Requirements
2 Approaches to Requierements Engineering Reference: Systems Analysis and Design in a Changing World, 3 rd Edition, chapter 2 and chapter 6.
Principles of Engineering System Design Dr T Asokan
Chapter 4 System Models A description of the various models that can be used to specify software systems.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Ch.2 Part C: Message Sequence Charts, UML EECE **** Embedded System Design.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Intro to Software System Modeling
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Chapter 7 The Object-Oriented Approach to Requirements.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 15 The Unified Modeling Language: a Primer.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
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.
Technical Methods for Specifying Requirements 1. When to Use Technical Methods  If the description of the requirement is too complex for natural language.
MADALINA CROITORU Software Engineering week 4 Practical Madalina Croitoru IUT Montpellier.
UML Activity Diagrams.
Chapter 6: System Models Omar Meqdadi SE 273 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
CompSci 280 S Introduction to Software Development
Requirements Techniques, cont.
UML Diagrams By Daniel Damaris Novarianto S..
Main issues: • What do we want to build • How do we write this down
The Engineering Design of Systems: Models and Methods 3rd Edition
Diagramming Techniques
UML Diagrams Jung Woo.
UML Activity Diagrams & State Charts
Dynamic Modeling Lecture # 37.
Presentation transcript:

Week 7 - Systems Engineering and Analysis Buede Chapter 12 – Graphical Modeling Techniques Image from http://www.cs.ubc.ca/~murphyk/Bayes/bnintro.html. Left – Systems engineers us a lot of graphical models which look like state diagrams. If you have to predict how the pieces of a large system will interact, you need help visualizing that. This one is a “generative model for how to create generative models.” SE-Week 6

Wasson also talks about modeling Mostly scattered by topic – what you are modeling. E.g., Sec 15.2 – System behavioral response model Ch 17 – Use Cases & UML Ch 20 – Modeling system and support operations Ch 51 – System modeling and simulation

Data, Process, and Behavior Models Data Models – relationships among input and outputs. Process Models – define functional decomposition of the system function and flow of inputs and outputs for those functions. Behavior Models – define the control, activation, and termination of of system functions needed to meet performance requirements.

Modeling Approaches & Methods Data Modeling Entity-relationship diagrams (ERDs) Higraphs Process Modeling Data flow diagrams (DFDs) IDEF0 N2 charts Behavior Modeling Function flow block diagrams (FFBDs) Behavior diagrams (BDs) State-transition diagrams (STDs) Statecharts Control flow diagrams (CFDs) Petri nets (PNs) Object-oriented Modeling Object modeling technique (OMT) Real-time object-oriented modeling (ROOM) Table 12.1

Data Flow Diagram Semantics Figure 12.6

Context (External Systems) Diagram in DFD Figure 12.9

N2 Charts – an SE favorite! Figure 12.10

Function Flow Block Diagrams Basic Series Concurrent Selection Multiple-exit function Enhanced Iteration Looping Replication Series Concurrent Figure 12.11-12

Selection & Multiple-exit Functions, Iteration, Looping in FFBD Figure 12.13

FFBD for Elevator

Elevator Functional Architecture

Behavior Diagrams Figure 12.14

Finite State Machines Finite state machines: discrete valued inputs, outputs and internal items Sequential: past inputs impact current outputs (e.g., state-transition diagram) Combinational: current outputs characterized only current inputs Continuous machines: continuous and discrete inputs, outputs and internal items Figure 12.16

State-transition Diagram for ATM Event Output Partially Completed Figure 12.17

State-transition Diagram for an Elevator Figure 12.18

Statechart External System Statechart For Cruise Control System Figure 12.19

For Cruise Control System Statechart, cntd Decomposition of the “Not Off” State For Cruise Control System Figure 12.20

of Cruise Control System Statechart, cntd Decomposition of the “Alive” State for the Indicator of Cruise Control System Figure 12.21

of Cruise Control System Statechart, cntd Decomposition of the “On” State for the Indicator of Cruise Control System Figure 12.22

Statechart for Cruise Control System Figure 12.23

Object-oriented Modeling – our favorite in software? Object Modeling Technique (OMT) Object model (ERD) Dynamic model (STD & nested state diagrams) Functional model (DFD) Real-time Object-oriented Modeling (ROOM) Objects = Actors Actors communicate via messages ROOMcharts Combine functional and behavioral models Generalization of Statecharts Unified Modeling Language (UML) (SysML)