Anda di halaman 1dari 33

Socio-technical Systems

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide1

Objectives

Pokok bahasan ini untuk menjelaskan apa yang dimaksud


dengan socio-teknikal dan perbedaan antara sistem berbasis
komputer biasa
Untuk memperkenalkan konsep dan sifat dari sistem yang
mendesak (emergent), dan konsep kehandalan
sertakeamanan dari sistem
Akan dijelaskan tentang mengapa konteks dari suatu
organisasi akan mempengaruhi desain dan kegunaan dari
sistem
Akan dijelaskan juga mengapa sistem akan dapat diwariskan
sehingga faktor ini sangat kritis untuk proses bisnis

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide2

Topik yang Dibahas

Sifat sistem yang mendesak (emergent)


Rekayasa sistem
Hubungan antara organisasi, manusia dan
sistem komputer
Legacy / Nilai / Value dari sistem

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide3

Apa yang dimaksud dengan sistem?

Sebuah perangkat yang terdiri dari beberapa komponen


yang bekerja bersama-sama untuk mencapai tujuan yang
sama.
Sebuah sistem terkadang termasuk software, mekanik,
elektrikal dan perangkat keras yang dioperasikan oleh
manusia.
Sebuah komponen sistem tergantung terhadap sistem
yang lain. Sehingga sebuah sistem dengan sistem yang
lain adalah kesatuan yang ter-ikat.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide4

Kategori Sistem

Technical computer-based systems

Sistem ini mencakup perangkat lunak dan keras namun


operator hanya sebagai bagian dari operasional. Sistem
ini tidak tergantung dengan adanya manusia.

Socio-technical systems

Sistem ini mencakup sistem teknis baik perangkat lunak


dan keras. Akan tetapi pada proses operasionalnya
sangat bergantung ataupun dapat berinteraksi dengan
baik dengan manusia. Sistem ini diatur oleh kebijakan
organisasi atau aturan yang dibuat.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide5

Socio-technical system characteristics

Emergent properties

Non-deterministic

Adalah sifat dari keseluruhan sistem yang bergantung pada


komponen dan hubungan antara satu sistem dengan sistem
yang lain ataupun dengan manusia.
Sistem ini tidak selalu menghasilkan output yang sama ketika
diberikan masukan yang sama, karena perilaku sistem
tergantung pada operator manusia.

Complex relationships with organisational objectives

Sejauh mana sistem mendukung tujuan dan kebergantungan


tujuan terhadap organisasi.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide6

Emergent properties

Sifat dari sebuah sistem secara keseluruhan


didapatkan dari sifat komponen sistem yang lain,
karena pada sistem ini muncul sebagai
konsekuensi atau turunan dari hubungan antar
sistem.
Sistem ini memiliki kemampuan tersebut hanya
dapat dinilai dan diukur setelah terintegrasi
dengan sistem sebelumnya.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide7

Contoh dari emergent properties

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide8

Tipe dari emergent property

Functional properties

Fungsi ini muncul ketika bagian-bagian dari sebuah sistem


sepeda untuk beberapa keperluan. Misalkan sebuah sepeda
muncul sebagai alat transportasi, sejak ditemukannya sepeda.

Non-functional emergent properties

Sebagai contoh adalah reliability, performa (kecepatan,


kehandalan dsb.). Hal ini muncul seiring berjalannya waktu dan
masalah tersebut terkadang muncul ketika sistem sedang
berjalan. Sama dengan sebuah sistem komputer, sehingga
perlu dipikirkan bagaimana untuk mengantisipasi masalah yang
muncul ketika sistem dibuat.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide9

System reliability engineering

Komponen memiliki dependensi yang berbeda


Karena masing-masing memiliki dependensi
yang berbeda, sangat riskan untuk muncul
masalah atau kegagalan dari sistem.
Tidak mungkin untuk mengantisipasi semua
masalah yang akan muncul.
Terkadang, software akan memberikan hasil dari
keluaran sistem yang berbeda dari pengukuran
yang sebenarnya.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide10

Pengaruh dari reliability

Hardware reliability

Software reliability

Apakah komponen memiliki kemungkinan gagal? Berapa lama


waktu yang diperlukan untuk memperbaiki komponen tersebut?

Seberapa besar kemungkinan bahwa komponen perangkat


lunak akan menghasilkan output yang salah? Keluaran yang
dihasilkan berbeda dari pengukuran yang dihasilkan oleh
perangkat keras.

Operator reliability

Seberapa besar kemungkinan operator dari sistem error?

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide11

Inter-disciplinary involvement
Software
engineering

Electronic
engineering

Mechanical
engineering

Structural

ATCsystems

Userinterface

engineering

engineering

design

Civil
engineering

Electrical
engineering

Architecture

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide12

System requirements definition

Three types of requirement defined at this stage

Abstract functional requirements. System functions


are defined in an abstract way;
System properties. Non-functional requirements for
the system in general are defined;
Undesirable characteristics. Unacceptable system
behaviour is specified.

Should also define overall organisational


objectives for the system.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide13

System objectives

Should define why a system is being procured


for a particular environment.
Functional objectives

To provide a fire and intruder alarm system for the


building which will provide internal and external
warning of fire or unauthorized intrusion.

Organisational objectives

To ensure that the normal functioning of work carried


out in the building is not seriously disrupted by
events such as fire and unauthorized intrusion.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide14

System requirements problems

Complex systems are usually developed to


address wicked problems

Problems that are not fully understood;


Changing as the system is being specified.

Must anticipate hardware/communications


developments over the lifetime of the system.
Hard to define non-functional requirements
(particularly) without knowing the
component structure of the system.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide15

The system design process


Partition
requirements

Definesubsystem
interfaces
Identify
subsystems

Specifysubsystem
functionality
Assignrequirements
tosubsystems

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide16

The system design process

Partition requirements

Identify sub-systems

Identify a set of sub-systems which collectively can meet the


system requirements.

Assign requirements to sub-systems

Organise requirements into related groups.

Causes particular problems when COTS are integrated.

Specify sub-system functionality.


Define sub-system interfaces

Critical activity for parallel sub-system development.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide17

System design problems

Requirements partitioning to hardware,


software and human components may involve a
lot of negotiation.
Difficult design problems are often assumed to
be readily solved using software.
Hardware platforms may be inappropriate for
software requirements so software must
compensate for this.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide18

Requirements and design

Requirements engineering and system design


are inextricably linked.
Constraints posed by the systems environment
and other systems limit design choices so the
actual design to be used may be a requirement.
Initial design may be necessary to structure the
requirements.
As you do design, you learn more about the
requirements.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide19

Spiral model of requirements/design

Requirements
Elicitation and
Analysis

Architectural
Design

Start

Problem
Defi nition

Review and
Assessment

System Requirements and Design

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide20

System modelling

An architectural model presents an abstract view


of the sub-systems making up a system
May include major information flows between
sub-systems
Usually presented as a block diagram
May identify different types of functional
component in the model

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide21

Burglar alarm system

Movement
sensors

Door
sensors

Alarm
controller

Siren

IanSommerville2004

Voice
synthesiser

Telephone
caller

SoftwareEngineering,7thedition.Chapter2

External
controlcentre

Slide22

Sub-system description
Sub-system

Description

Movement sensors

Detects movement in the rooms monitored by the system

Door sensors

Detects door opening in the external doors of the building

Alarm controller

Controls the operation of the system

Siren

Emits an audible warning when an intruder is suspected

Voice synthesizer

Synthesizes a voice message giving the location of the suspected intruder

Telephone caller

Makes external calls to notify security, the police, etc.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide23

ATC system architecture


Radar
system

Position
processor

Transponder
system

Datacomms.
system

Backup
position

Aircraft
comms.

Telephone
system

Comms .

Backupcomms.

processor

processor

processor

Aircraft
sim ulation
system

Flightplan
database

Weathermap
system
Accounting
system

Controller
info.system

Controller
consoles

Activitylogging
system

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide24

Sub-system development

Typically parallel projects developing the


hardware, software and communications.
May involve some COTS (Commercial Off-the-Shelf)
systems procurement.
Lack of communication across implementation
teams.
Bureaucratic and slow mechanism for
proposing system changes means that the development
schedule may be extended because of the need for
rework.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide25

Human and organisational factors

Process changes

Job changes

Does the system require changes to the work


processes in the environment?
Does the system de-skill the users in an environment or
cause them to change the way they work?

Organisational changes

Does the system change the political power structure in


an organisation?

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide26

Organisational processes

The processes of systems engineering overlap and


interact with organisational procurement processes.
Operational processes are the processes involved in
using the system for its intended purpose. For new
systems, these have to be defined as part of the system
design.
Operational processes should be designed to be flexible
and should not force operations to be done in a particular
way. It is important that human operators can use their
initiative if problems arise.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide27

Legacy systems

Socio-technical systems that have been developed using


old or obsolete technology.
Crucial to the operation of a business and it is often too
risky to discard these systems

Bank customer accounting system;


Aircraft maintenance system.

Legacy systems constrain new business processes and


consume a high proportion of company budgets.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide28

Supportsoftware

Runson

System
hardware

IanSommerville2004

Uses

Runson

Embeds
knowledgeof
Application
software
Uses

Businesspolicies
andrules

Uses

Application
data

SoftwareEngineering,7thedition.Chapter2

Constrains

Business
processes

Slide29

Legacy system components

Hardware - may be obsolete mainframe hardware.


Support software - may rely on support software from
suppliers who are no longer in business.
Application software - may be written in obsolete
programming languages.
Application data - often incomplete and inconsistent.
Business processes - may be constrained by software
structure and functionality.
Business policies and rules - may be implicit and
embedded in the system software.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide30

Sociotechnicalsystem
Businessprocesses
Applicationsoftware
Supportsoftware
Hardware

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide31

Key points

Socio-technical systems include computer hardware,


software and people and are designed to meet some
business goal.
Emergent properties are properties that are characteristic
of the system as a whole and not its component parts.
The systems engineering process includes specification,
design, development, integration and testing. System
integration is particularly critical.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide32

Key points

Human and organisational factors have a significant


effect on the operation of socio-technical systems.
There are complex interactions between the processes of
system procurement, development and operation.
A legacy system is an old system that continues to
provide essential services.
Legacy systems include business processes, application
software, support software and system hardware.

IanSommerville2004

SoftwareEngineering,7thedition.Chapter2

Slide33

Anda mungkin juga menyukai