Socio-technical Systems (Computer-based System Engineering)

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering.
Advertisements

Chapter 10 – Sociotechnical Systems Lecture 1 1Chapter 10 Sociotechnical Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development.
Chapter 10 – Sociotechnical Systems Lecture 1 1Chapter 10 Sociotechnical Systems.
The Big Picture.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 2 Slide 1 Socio-technical Systems.
SWE Introduction to Software Engineering
Socio-technical Systems
The Big Picture.
©Ian Sommerville 2000Software Engineering, 6th edition Slide 1 Introduction l Getting started with software engineering l Objectives To introduce software.
Software Engineering General Project Management Software Requirements
Chapter 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Socio-technical Systems.
Software Engineering Chapter 2 Socio-technical systems Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
SWE Introduction to Software Engineering
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
Lecture 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
Requirements Engineering
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 1.
Chapter 10 – Sociotechnical Systems 1Chapter 10 Sociotechnical Systems.
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
Software Engineering Dr. K. T. Tsang
2. Socio-Technical Systems
3- System modelling An architectural model presents an abstract view of the sub-systems making up a system May include major information flows between.
Socio-technical Systems. Objectives l To explain what a socio-technical system is and the distinction between this and a computer-based system. l To introduce.
Socio-technical Systems
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
1 Software Engineering Chap 1 Instructor : Haya Samamneh.
Software Engineering Chapter 2: Computer-based System Engineering
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Systems Engineering l Designing, implementing, deploying and operating systems.
Made by: Sambit Pulak XI-IB. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence of data.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Software Requirements Engineering CSE 305 Lecture-2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 3 Slide 1 Critical Systems 1.
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Systems Engineering l Specifying, designing, implementing, validating, deploying.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering.
 CS 5380 Software Engineering Chapter 10 Sociotechnical Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Socio-technical Systems.
Socio-technical Systems. Objectives To explain what a socio-technical system is and the distinction between this and a computer-based system To introduce.
Chapter 10 – Sociotechnical Systems 1Chapter 10 Sociotechnical Systems CS 425 November 14, 2013 Ian Sommerville, Software Engineering, 9 th Edition Pearson.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Chapter 19 – Systems Engineering Chapter 19 Systems Engineering126/11/2014.
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
Basic Security Concepts University of Sunderland CIT304 Harry R Erwin, PhD.
©Ian Sommerville 2000Dependability Slide 1 Chapter 16 Dependability.
1 Software Engineering, 8th edition. Chapter 2 Courtesy: ©Ian Sommerville 2006 Feb 12 th, 2009 Lecture # 3 Socio-technical Systems.
Topic: Reliability and Integrity. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence.
1. 2 An Introduction to Software Engineering 3 What is software? Computer programs and associated documentation such as requirements, design models and.
Socio-Technical Systems, York EngD Programme, 2009Slide 1 LSCITS and Socio-technical Systems Prof Ian Sommerville.
ORGANIZATIONAL BEHAVIOR
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 2 Slide 1 Socio-technical Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Socio-technical Systems.
Slide 1 CS 310 Chapter 2 Socio Technical Systems A system that includes people, software, and hardware Technical computer-based systems include hardware.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter2: Systems Engineering l Designing, implementing, deploying and operating.
CHAPTER 2. Designing, implementing, deploying and operating systems which include hardware, software and people.
Classifications of Software Requirements
Socio-technical Systems
DT249/4 Information Systems Engineering
GROUP MEMBERS NAME ROLL NO SHAUBAN ALI 17-ARID-5650 UMAIR MUSHTAQ 17-ARID-5656 TARIQ SAEED 17-ARID-5657 MUSKAN WADOOD 17-ARID-5641.
Chapter 13 Quality Management
Systems Engineering Designing, implementing, deploying and operating systems which include hardware, software and people.
Presentation transcript:

Socio-technical Systems (Computer-based System Engineering) Chapter 2 Socio-technical Systems (Computer-based System Engineering)

System Engineering Is the activity of specifying, designing, implementing, deploying, maintaining systems, which include hardware, software , people and interaction of the system with users and its environment.

Objectives To introduce the concept of emergent system properties such as reliability and security To explain system engineering and system processes

What is a system? A collection of inter-related components working together towards some common objective. A system may include software, mechanical, electrical and electronic hardware and be operated by people. System components are dependent on other system components System is more than simply the sum of its parts! It has properties of the system as a whole. (emergent properties)

Socio-technical system characteristics They have emergent properties Properties of the system of a whole that depend on the system components and their relationships. They are often Non-deterministicغير قطعية They do not always produce the same output when presented with the same input because the system’s behaviour is partially dependent on human operators.

System categories , cont… Technical computer-based systems Systems that include hardware and software but where the operators and operational processes are not normally considered to be part of the system. Socio-technical systems Systems that include technical systems but also operational processes and people who use and interact with the technical system. Socio-technical systems are governed by organizational policies and rules.

Problems of systems engineering Large systems are usually designed to solve 'wicked' problemsالشرس Systems engineering requires a great deal of coordination across disciplines distrust and lack of understanding across engineering disciplines Systems must be designed to last many years in a changing environment

Emergent System properties Properties of the system as a whole rather than properties that can be derived from the properties of components of a system. Emergent properties are a consequence (result) of the relationships between system components They can therefore only be assessed and measured ONCE the components have been integrated into a system

Examples of emergent properties

Types of emergent properties Functional properties These appear when all the parts of a system work together to achieve some objective. For example, a bicycle has the functional property of being a transportation device once it has been assembled from its components.

Types of emergent properties (cont.) Non-functional emergent properties Examples are reliability, performance, safety, and security. These relate to the behaviour of the system in its operational environment. They are often critical for computer-based systems as failure that may make the system unusable.

Complexity of emergent system properties- reliability Because of component inter-dependencies, faults can be propagated through the system, so failure in one component can affect the operation of other components. System failures often occur because of unforeseen inter-relationships between component.

Influences on a system reliability Hardware reliability What is the probability of a hardware component failing and how long does it take to repair that component? Software reliability How likely is it that a software component will produce an incorrect output. Software failure is usually distinct from hardware failure in that software does not wear out. Operator reliability How likely is it that the operator of a system will make an error?

Influences on a system reliability (cont.) Properties such as performance, usability, and reliability are difficult to assess but can be measured after the system is operational. However, some properties such as safety and security pose a different problem, because it is very hard to predict all possible modes of access and explicitly forbid them. Safety - the system that reflects the system’s ability to operate without danger Security - the system should not permit unauthorised use Measuring or assessing these properties is very hard (why???)

The system engineering process Usually follows a ‘waterfall’ model because of the need for development of different parts of the system. There are important distinctions between the system engineering process and the software development process:

The system engineering process (cont.) Little scope for rework during system development because hardware changes are very expensive, reworking the system design to solve these problems. Software becomes so important in systems because of its flexibility Example: siting of Base station in mobile cell Always involves engineers from different disciplines , many engineering disciplines who must work together, much scope for misunderstanding here. Different disciplines use a different vocabulary and much negotiation is required. Engineers may have personal agendas to fulfil.

The system engineering process (cont.)

Inter-disciplinary involvement Air traffic control