Lecture 6 New
Lecture 6 New
6th Semester
Software Engineering Department
Sir Syed University of Engineering & Technology
Table of Content
02
• Purposefulness
• Feedback and
Control
System • Complexity
• Dynamics
• Equifinality
03
Purposefulness
• Ackoff [1] termed these purposeful systems. Because the enterprise is purposeful
there is a rationale that explains its actions.
• A goal-seeking system cannot change its goal. Goal-seeking systems have all
the capabilities of state-maintaining systems.
5
Feedback & Control
6
Feedback & Control
• The objective of control is to reduce the deviation between a desired state of the
system and the actual state of the system.
• In order to maintain the desired state, feedback control is implemented as
follows:
• A system parameter indicative of the desired system state is measured and
monitored.
• A reference level that describes the desired value for the system parameter
is set.
7
Feedback & Control
8
Feedback & Control
9
Feedback & Control
• In the model of Figure 2.1, the manager fulfills the role of the decision-making
function.
• The actuator is the set of actions the manager can take to correct any deviations
between the system’s desired performance and its actual performance.
10
Complexity
• The more parts a system has, then the more complex that system is. Many
enterprises are large, consisting of many different parts, so an enterprise would
be considered complex.
• Complexity arises from not only the number of parts in the system, but also from
the interrelationships of the system parts and the emergent behavior that cannot
be predicted from the individual system parts.
11
Dynamic
• An enterprise changes over time; it grows, shrinks, adds parts, removes parts,
and changes its parts and the relationships between those parts.
12
Equifinality
• Enterprises exhibit the property of equifinality, which means the enterprise can
accomplish its objectives with different inputs and with different internal processes to
reach the enterprise’s goal.
• The enterprise analyst needs to be aware that a best practice in one organization might
not be transferable to another organization because of the mismatch between the
practice and the organization’s culture.
13
System
Dynamics
Introduction
014
System Dynamics -- Introduction
• System Dynamics was started at MIT by Forrester, and is derived from ideas in
computer simulation, control theory, and decision-making.
• System Dynamics provides two tools that are useful in the study of enterprise
systems: causal loop diagrams and stock and flow simulation models.
015
Causal Loop Diagram
• The variables are system elements of interest that are connected by arcs denoting
relationships.
• The purpose of the diagram is to depict beliefs about the causal structure of the
system.
• Figure 2.2 shows the notation for three types of relationships. Each node, shown as
text, is a system variable.
• The arcs show relationships between variables. Relationships are either positive
(shown as +) or negative (shown as -).
016
Causal Loop Diagram
18
Causal Loop Diagram (Example)
• A stock and flow diagram views the system as consisting of stocks that accumulate
things and flows that show the movement of things in the system.
• The “things” that flow and are accumulated can be:
• Materials. This can be any physical object such as products, raw materials, or
inventory.
• Money. This can be money in any of its forms such as a savings account, income
from the sales of a product, or taxes.
• Information Objects. This can be any non-physical object that flows in the system
such as customer orders, reservation requests, or purchase orders.
• People. This can be any group of people such as customers, employees, or
patients.
020
Stock and Flow Diagrams
021
Summary
022