Scribd
Upload
117 views21 pages

Coupling and Systems

Coupling refers to the interdependence between software modules or systems. There are three main types: tight coupling, loose coupling, and decoupled. Tight coupling means strong interdependence, where a change in one module likely affects other modules. Loose coupling means minimal interdependence through well-defined interfaces. Hierarchical systems divide tasks according to function between different computers or levels, like DDC, sequence control, and supervisory control. Distributed systems have many computers performing similar tasks in parallel for flexibility and reliability.

Uploaded by

Gurpreet Kaur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
117 views21 pages

Coupling and Systems

Coupling refers to the interdependence between software modules or systems. There are three main types: tight coupling, loose coupling, and decoupled. Tight coupling means strong interdependence, where a change in one module likely affects other modules. Loose coupling means minimal interdependence through well-defined interfaces. Hierarchical systems divide tasks according to function between different computers or levels, like DDC, sequence control, and supervisory control. Distributed systems have many computers performing similar tasks in parallel for flexibility and reliability.

Uploaded by

Gurpreet Kaur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 21

Coupling and Systems

Coupling
• the degree to which each program module relies on
other modules, and is also the term used to describe
connecting two or more systems.
• broken down into loose coupling, tight coupling, and
decoupled.
• Coupling is also used to describe software as well as
systems.
• Also called dependency.
Tight Coupling
• Tight coupling (or tightly coupled) is a type of coupling that describes a system in
which hardware and software are not only linked together, but are also dependent upon
each other.
• In a tightly coupled system where multiple systems share a workload, the entire system
usually would need to be powered down to fix a major hardware problem, not just the
single system with the issue.
• In software, the term tight coupling is used to define software that will work only in one
part of a specific type of system and the software is dependent on other software.
• For example, an operating system would be considered tightly coupled as it depends on
software drivers to correctly install and activate the system's peripheral devices.
• Also called heavy coupling.
Loose Coupling
• Loose coupling (or loosely coupled) is a type of coupling that describes how multiple
computer systems, even those using incompatible technologies, can be joined together
for transactions, regardless of hardware, software and other functional components.
Loosely coupled systems describe those systems that work on an exchange relationship where
little input is needed from each of the additional systems.
In a loosely coupled system, hardware and software may interact but they are not dependent on
each other to work.
Computers in a network are considered loose-coupled systems as a client machine may request
data from the server, but the two systems also work independently of each other.
In software terminology, loosely coupled refers to software where routines, modules, functions,
and similar components are executed only as needed, and do not run at the launch of the software
application and while it is being used. Web services are a type of software application that uses
loose coupling.
Also called light coupling.
Loosely Coupled System
• It is a concept of system design and computing where loosely
coupled system is one in which every individual component
has no knowledge of the definitions of other components.
• In a loosely coupled system, hardware and software may
interact but they are not dependent on each other.
Loosely Coupled System - Characteristics
1. It uses distributed memory concept so high space in this architecture.
2. Contention is low in loosely coupled
3. It has high scalability
4. Data rate in loosely coupled system is low
5. Cost of loosely coupled system is low
6. It has static interconnection network
7. It operates on Multiple Operating System
8. In loosely coupled system, each process have its own cache memory
9. Throughput is low in loosely coupled
10. Security is low in loosely coupled
11. Power consumption is higher than tightly coupled system
12. Reusable in the case of flexibility
Tightly Coupled System
•It is a concept of system design and computing
where every hardware and software components
that are linked together in such manner that each
component is dependent upon each other.
•Tightly coupled architecture promotes
interdependent applications and code.
•Tightly coupled architecture is fragile as the minor
issue in one segment can bring the whole system
down.
Tightly Coupled System - Characteristics
1. It uses shared memory concept. Hence Low space in this architecture
2. Contention is high in tightly coupled
3. It has low scalability
4. Data rate in tightly coupled system is high
5. Cost of tightly coupled system is high
6. It has dynamic interconnection network
7. It operates on Single Operating System
8. In tightly coupled system cache memory assign according to the need of
processing
9. Throughput is high in tightly coupled
10. Security is high in tightly coupled
11. Power consumption is lower than loosely coupled system
12. Not reusable in the case of flexibility
Concept Tightly Coupled Loosely coupled
Memory Shared, low space Distributed, high space
Contention High Low
Scalability Low High
Data rate High Low
Cost High Low
Interconnection network Dynamic Static
Operating System Single Multiple
Cache memory of a process Assigned acc. to need Independent
Throughput High Low
Security High Low
Power Consumption Low High
Reusability No Yes
Hierarchical Systems
Centralized Computer System:
• Most of the 1960s computer control systems implied the use of one
central computer for the control of the whole plant. The reason for
this was largely financial (computers were expensive).
• By 1970 the cost of computer hardware had reduced to such an
extent that it became feasible to consider the use of dual computer
systems.
• Automatic failure and change-over equipment when used becomes a
critical component.
• The continued reduction of the cost of hardware and the
development of the microprocessor has made multi-computer systems
feasible.
Multi – Computer Systems
• Several computers can be configured for real-time computer
control applications.
• These include dual computer systems to increase reliability,
and distributed and hierarchical configurations.
1. Hierarchical Systems: tasks are divided according to
function, for example; one computer performing DDC, other
performing sequence control, other performing supervisory
control..
2. Distributed Systems: many computers perform essentially
similar tasks in parallel.
Multi – Computer Systems
•Direct Digital Control (DDC) is the
automated control of a condition or process by a
digital device.
• DDC takes a centralized network-oriented
approach.
•All instrumentation is gathered by various analog
and digital converters which use the network to
transport these signals to the central controller.
Hierarchical Decision Making
Hierarchical System - Example
• A typical example of a hierarchical system is the batch
system given below.
• It has three levels; Manager, Supervisor, and unit Control.
• It is assumed that single computers are used for manager
and supervisor functions, and that for each processing unit a
single unit control computer is used.
Hierarchical System - Advantages
•Natural way to organize
•Not intrinsically rigid
• Not intrinsically inefficient – not the
same as centralized planning –
priorities and goals are clear, therefore
efficient
Distributed System
• Each unit is carrying out essentially similar tasks to all the other units.
• In the event of failure or overloading of a particular unit all or some of
the work can be transferred to other units.
• Advantages:
1. Sharing of tasks between μCs.
2. More flexible than using one μC.
3. Failure of a unit will cause less disruption.
4. It is easier to make changes .
5. Linking by serial highway means that the computer units can be
widely dispersed .

You might also like