CS 310 Ch8: System models Abstract descriptions of systems being analyzed to help the analyst understand the system functionality communicate with customers.

Slides:



Advertisements
Similar presentations
Chapter 7 System Models.
Advertisements

(C) Michael Brückner 2005/2006 Software Engineering 1 Course Software Engineering Class 10 / Requirements Engineering, Systems Modeling Michael.
Modeling Main issues: What do we want to build How do we write this down.
Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
SWE Introduction to Software Engineering
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.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
CS 425/625 Software Engineering System Models
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
7M701 1 Software Engineering Systems Models Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 7 (some items)
©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.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
7M701 1 Software Engineering Data Flow Models Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 7
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
7M822 Software Engineering: System Models 14 September 2009.
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
Slide 1 Chapter 8 Behavioral Modeling. Slide 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 1.
Chapter 7: System models
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Software Engineering 8. System Models.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models. System modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with.
System Models Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn Lecture 6 & 7.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
SYSTEM MODELS MUHAMMAD RIZWAN. Objectives  To explain why the context of a system should be modelled as part of the RE process  To describe behavioural.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
October 5, 2010COMS W41561 COMS W4156: Advanced Software Engineering Prof. Gail Kaiser
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.
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
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.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Rekayasa Perangkat Lunak (Software Engineering) M.Sukrisno Mardiyanto Kuliah Umum Universitas Dian Nuswantoro Semarang, 16 Oktober 2008.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
SWEN 5231 FORMAL METHODS Slide 1 System models u Abstract presentations of systems whose requirements are being analyzed.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Specification Techniques. System models are abstract descriptions of systems whose requirements are being analyzed Objectives  To explain why specification.
Chapter 6: System Models Omar Meqdadi SE 273 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
September 15, 2009COMS W41561 COMS W4156: Advanced Software Engineering Prof. Gail Kaiser
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
© 2000 Franz Kurfess System Design Methods 1 CSC 205: Software Engineering I Dr. Franz J. Kurfess Computer Science Department Cal Poly.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Object-oriented and Structured System Models
Main issues: • What do we want to build • How do we write this down
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Abstract descriptions of systems whose requirements are being analysed
IS301 – Software Engineering V:
تحلیل سیستم‌ها مدل‌سازی پردازشی.
System models October 5, 2005.
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Presentation transcript:

CS 310 Ch8: System models Abstract descriptions of systems being analyzed to help the analyst understand the system functionality communicate with customers Models present the system from different perspectives external perspective for the system’s context or environment behavioural perspective showing the behaviour of the system structural perspective showing the system or data architecture

Models 8.1 Context Models (illustrate the system boundaries) Architectural models show a system and its relationship with other systems Process models show the processes that the system supports. Used to describe a system’s overall behaviour. 8.2 Behavioural models (how a system behaves) Data flow models (DFD)* show how data moves through the system State machine models show the systems response to events 8.3 Data Models (ER diagrams and data dictionaries) 8.4 Object Models (like C++ classes) 8.5 Structured methods * Very little difference between DFD and process models

Context model: an ATM system This is architectural, it says nothing about how systems interact the system

Equipment procurement process Process models needed to describe activities

8.2.1 Data-flow models Data flow diagrams (DFDs) show the processing steps as data flows through a system from a functional perspective simple and intuitive notation that customers can understand Similar to process diagrams, with the focus on data flows tracking and documenting the data associated with a process helps to develop an overall understanding of the system Data flow diagrams may also show what data is exchanged with other systems in the environment

Order processing DFD How does this differ from an architectural process model? In the way it is arrived at: one is derived from what information passes through the system, the other from what is happening May be a small piece of one of the bubbles in the process model

8.2.2 State machine models Model the system response to external and internal events Often used for modelling real-time systems Conventions: system states are nodes events are arcs between these nodes when an event occurs, the system moves from one state to another

State machine: microwave oven state name what it does state transitions

Microwave oven expansion of the Operation state *

Context (8.1) versus Behavioral Models (8.2) Context: defines system boundaries high level: fig 8.1 shows simple boundaries lower level process diagrams (e.g. fig 8.2) show activities, distinguishing between internal and external activities Behavioral: how it behaves data flow (like process, but emphasis is on data) »sometimes an elaboration of an activity in a process model state machine

Sign On Select Option Send Message Process Diagram for IM Operation... Select SN Validate SN/PWD SN/pwd invalid sign on Present Options SN send/SN Send Message DFD for IM Sign On

8.3 (Semantic) data models Describe the logical structure of data processed by the system using ER model How does this differ from CS 325 notation?

8.4 Object models Describe the system in terms of object classes: a set of objects with common attributes and the services (operations) Natural way to reflect the real-world entities Abstract entities are more difficult to model this way Types inheritance models aggregation models interaction models What do you know about object models?

Library class hierarchy Inheritance models

Multiple inheritance Object classes can inherit from several super-classes Can lead to semantic conflicts when attributes/services with the same name in different super-classes have different semantics Makes class hierarchy reorganization more complex

Object aggregation

8.4.3 Object behaviour modelling using a UML sequence diagram

8.5 Structured Methods Often a company will have a well-defined modeling process Structured methods define a set of models a process for deriving these models rules and guidelines that should apply to the models Normally with specific CASE tool support This can be too restrictive More commmon practice: use a variety of models to elicit requirements