Chapter 6: System Models Omar Meqdadi SE 273 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.

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.
Chapters 7 & 9 System Scope
UML: Use Cases Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
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
1 SWE Introduction to Software Engineering Lecture 13 – System Modeling.
©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)
Topics Creating DFD Physical and logical DFD Event driven modeling
©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.
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
7M822 Software Engineering: System Models 14 September 2009.
©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
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
©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.
Chapter 5 – System Modeling
Chapter 10 Architectural Design
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
CS 310 Ch8: System models Abstract descriptions of systems being analyzed to help the analyst understand the system functionality communicate with customers.
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.
The Unified Modeling Language Part I Omar Meqdadi SE 2730 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
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.
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.
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.
By Orvilla V. Balangue, MSCS SAS-ICT Faculty
Specification Techniques. System models are abstract descriptions of systems whose requirements are being analyzed Objectives  To explain why specification.
Chapter 5 – System Modeling Lecture 9 Section A 27/4/2015 Section B 29/4/2015 1Chapter 5 System modeling.
 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
© 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.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
CompSci 280 S Introduction to Software Development
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Object-oriented and Structured System Models
Department of Computer Science
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:

Chapter 6: System Models Omar Meqdadi SE 273 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville

2 Topics covered Context models Behavioural models Data models

3 System models Abstract descriptions of systems whose requirements are being analysed

4 System modelling System modelling helps the analyst to  Understand the functionality of the system  Models are used to communicate with customers Different models present the system from different perspectives  External perspective showing the system’s context or environment  Behavioural perspective showing the behaviour of the system  Structural perspective showing the system or data architecture

5 Model types Data processing model showing how the data is processed at different stages. Composition model showing how entities are composed of other entities. Architectural model showing principal sub-systems. Classification model showing how entities have common characteristics. Stimulus/response model showing the system’s reaction to events.

6 Context models Architectural models show the system and its relationship with other systems. Context models are used to illustrate the operational context of a system - they show what lies outside the system boundaries. Social and organisational concerns may affect the decision on where to position system boundaries.

7 The context of an ATM system

8 Process model Process models show the overall process and the processes that are supported by the system.

9 Equipment procurement process

10 Behavioural models Behavioural models are used to describe the overall behaviour of a system. Two types of behavioural model are:  Data processing models that show how data is processed as it moves through the system;  State machine models that show the systems response to events. These models show different perspectives so both of them are required to describe the system’s behaviour.

11 Data-processing models Data flow diagrams (DFDs) may be used to model the system’s data processing. These show the processing steps as data flows through a system. DFDs are an intrinsic part of many analysis methods. Simple and intuitive notation that customers can understand. Show end-to-end processing of data.

12 Data flow diagrams DFDs model the system from a functional perspective. Tracking and documenting how the data associated with a process is helpful to develop an overall understanding of the system. Data flow diagrams may also be used in showing the data exchange between a system and other systems in its environment.

13 Order processing DFD

14 Insulin pump DFD

15 State machine models Model the behaviour of the system in response to external and internal events. Often used for modelling real-time systems. Show system states as nodes and events as arcs between these nodes. When an event occurs, the system moves from one state to another. State charts are an integral part of the UML and are used to represent state machine models.

16 Statecharts Allow the decomposition of a model into sub-models A brief description of the actions is included following the ‘do’ in each state. Can be complemented by tables describing the states and the stimuli.

17 Microwave oven state description

18 Microwave oven model

19 Data dictionaries Data dictionaries are lists of all of the names used in the system models. Descriptions of the entities, relationships and attributes are also included. Advantages  Support name management and avoid duplication;  Store of organisational knowledge linking analysis, design and implementation; Many CASE workbenches support data dictionaries.

20 Data dictionary entries

21 Weather Monitoring System Requirements The system shall have the means of determining the current time and date so that it can report the highest and lowest values for any of the four primary measurements during the previous 24 hour period. The system shall have a display that continuously indicates all eight primary and derived measurements, as well as current time and date. Through he use of a keypad the user may direct the system to display the 24 hour low or high of any one primary measurement, with the time of the reported value. The system shall allow the user to calibrate its sensors against known values, and set the current time and date of the system clock.

22 New Data Dictionary Time & Date Sensors: Temperature, Pressure, Humidity, Wind Speed, Wind Direction Keypad Input Manager Display (LCD Device) Display Manager Timer (clock) Sensor Sampler

23 Semantic data models Used to describe the logical structure of data processed by the system. An Entity-Relation-Attribute model sets out the entities in the system, the relationships between these entities and the entity attributes Widely used in database design. Can readily be implemented using relational databases. No specific notation provided in the UML but objects and associations can be used.

24 Library semantic model