Chapter 2 Socio-technical Systems _Computer-based System Engineering__1_

Document Sample
Chapter 2 Socio-technical Systems _Computer-based System Engineering__1_ Powered By Docstoc
					                Chapter 2
     Socio-technical Systems
    (Computer-based System Engineering)




1
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.



2
                Objectives
• To introduce the concept of emergent
  system properties such as reliability and
  security

• To explain system engineering and system
  processes


  3
           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

  4
    What is a system? Cont…


• System is more than simply the sum of its
  parts!

• It has a properties of the system as a whole.
  (emergent properties)



5
             System categories
• Socio-technical systems
    – Systems that include technical systems
      but also operational processes and people
      (knowledge) who use and interact with the
      technical system.

    – Socio-technical systems are governed by
      organizational policies and rules.



6
      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.

7
    System categories , cont…
• Technical computer-based systems
    – Systems that include hardware and
      software but where the operators are not
      normally considered to be part of the
      system.

    – The system is not self-aware (Power point
      is not aware that is it being used to
      present Software Engineering course) .


8
      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
  9
       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
  10
         Examples of emergent
             properties

• The reliability of the system
  – This depends on the reliability of system
    components and the relationships between the
    components.
• The usability of a system
   – This is a complex property which depends on
     the system operators and the environment
     where it is used.
  11
       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.


  12
     Types of emergent properties
• 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.
13
       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.



  14
           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
   15
      an error?
               Reliability relationships
• Hardware failure can generate a non genuine
  signals

• Software errors can cause alarms to be activated
  which cause operator stress and lead to operator
  errors
• The environment in which a system is installed can
  affect its reliability( a system design to operate in temp
  between 0 and 10 degrees will feel if the air condition
  broke, components will behave in unpredictable way)

   16
• 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


   17
  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:



  18
     The system engineering process
• 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
  - interdisciplinary involvement- 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.
19
         The system engineering
                process
Requirements                                                                   System
 definition                                                                decommissioning


               System                                               System
               design                                              evolution


                        Sub-system                    System
                        development                 installation


                                        System
                                      integration
20
     Inter-disciplinary involvement
            Air traffic control
  Software       Electronic    Mechanical
 engineering    engineering    engineering



  Structural    ATC systems    User interface
 engineering     engineering      design



    Civil        Electrical
                               Architecture
 engineering    engineering
21
Before a software can be engineered, the system
in which it resides must be understood.

To accomplish this, the overall objective of the
system must be determined;
the hardware, software, people, databases,
procedures, and other system elements must be
identified.

system requirements must be elicited, analyzed,
specified, modeled, validated, and managed. All
the above activities are the foundation of system
engineering.
22
Quote: the hardest part of building a
software system is deciding what to build

Advice: be sure you have assessed overall
feasibility before you expend effort and time
eliciting detailed requirements.

Advice: if different customers cannot agree
on requirements, the risk of failure is very
high.
  23
     System requirements definition
• System requirements
   – A structured document setting out detailed descriptions of
      the system services. Written as a contract between client
      and contractor
• Three types of requirement defined at this stage
   – Abstract functional requirements.
   The basic functions that the system must provide are defined
      in an abstract way
   – System properties.
     Non-functional requirements for the system in general
      are defined (availability, performance)
   – Desirable and Undesirable characteristics.
   24Unacceptable system behaviour is specified (what the
      system must not do)
Also, the system requirement must define overall
organizational objectives which the system should
meet.
Example:
Consider a system for an office building to provide for
fire protection and intruder detection.
A statement of objective might be:
• 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




25
   System requirements problems:
• Complex systems are usually developed to
  address wicked problems
   – Problems that are not fully understood;
   Example : earthquake

  Can tackle the problem after it has happened




  26
     The system design process, 1


  Partition                                                     Define sub-system
requirements                                                        interfaces

                 Identify                       Specify sub-system
               sub-system s                        functionality


                              Assign requirements
                                to sub-systems




27
    The system design process
• Partition requirements, organize
  requirements into related groups , HW Req.
  , SW Req.
• Identify sub-systems, identify a set of sub-
  systems which collectively can meet the
  system requirements

• Assign requirements to sub-systems,
  causes particular problems when are
  integrated , happen when purchase any
   28
  sub-system.
The system design process, cont…

• Specify sub-system functionality
  and relationships between them

• Define sub-system interfaces, if the
  interface has been agreed then a
  parallel sub-system development
  becomes possible.

29
           System design 1 problems:
• As a problems appear you often have to redo work
  done in earlier stages.




• Solution : Using spiral process , each round on
  the spiral may add more detail to design.




  30
     Spiral model of requirements and design
                Spiral process 2




31

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:10
posted:8/9/2011
language:English
pages:31