Analysis of Distributed Models: Client-Server and Master-Slave

This report delves into the realm of distributed models in software engineering, analyzing two key architectures: client-server and master-slave. It begins by contrasting these models, detailing the structure and functionality of each. The client-server model, with its thin-client and fat-client implementations, and the master-slave model are examined for their roles in managing and distributing tasks across a network. The report then presents a comparative analysis, highlighting the advantages and disadvantages of each architecture. For the client-server model, benefits such as efficient processing and flexible interfaces are balanced against drawbacks like network congestion. The master-slave model's strengths, including multiprocessor capabilities, are weighed against the potential for master processor overload. Finally, the report offers a rationale, emphasizing how distributed object-oriented frameworks and the benefits of client-server technology contribute to the development of scalable systems. The analysis is supported by references to academic research in the field.

Running Head: SOFTWARE ENGINEERING DISTRIBUTED MODELS
SOFTWARE ENGINEERING DISTRIBUTED MODELS
Name of the Student
Name of the University

1SOFTWARE ENGINEERING DISTRIBUTED MODELS
Introduction
Most of the computer-based systems are distributed systems, the processing of
information over several computerized machines in place of a single machine (Khan and Sayed
2017). Thus, distributed models in software engineering have become a vital part of the
enterprise computer system which includes Databases, file systems, operating system and the
internet. Here, we are choosing two main distributed architecture Client-server architectures and
Master/slave architecture.
1. Compare and Contrasting Distributed Models
In the Client Server Architecture/Model the application process has been divided
into different services in the network where each of the network process is either a server or a
client. These services are provided by the servers and the clients. The two main implementation
of this architecture are Thin-client here the servers completes the processes and then manages the
data, this model allows to store the data centrally, the information and applications are efficiently
distributed to the clients and Fat-Client model servers are only responsible for managing and
maintaining the data. The applications and interaction with the system that manages the system
software are executed by the software residing on the client machine (Robi, Mostafa and Khan
2016).
In the Master Slave Architecture/Model, the master sends the task and the slave picks up
the job and then processes them. The pattern balances the system sinec the workers distributes
the load.

2SOFTWARE ENGINEERING DISTRIBUTED MODELS
2. Advantages and Disadvantages
Advantages of Client server Model:
 Thin clients are able to have inexpensive computing boxes.
 Provides way to build hybrid architecture
 The client server environment allows the organization to maximize the benefit of the
micro technology.
 At the fraction of the cost of mainframes the PCs can deliver extraordinary power.
 Facilitates efficient processing and thus processing are done close t the data sources.
 Facilitates use of interfaces.
Disadvantage of Client server Model:
 Congestion in Network
 Not as robust as a P2P
 It is very expensive to install and manage
 Needs professional IT people to maintain the servers
Advantage of Master Slave Model:
 There are multiprocessor in the system, and all the processors are on the same level, there
has no master-slave class
 All processors can process and interrupt and tasks
Disadvantage of Master Slave Model:
 The master processor gets overloaded

3SOFTWARE ENGINEERING DISTRIBUTED MODELS
 The operating system run by the master processor, could fall behind the processors
running users applications
3. Rationale
The distributed object-oriented framework designs client/server advancements. Despite
the fact that customer/server frameworks are by and large described by their segments, they
should serve basic capacities keeping in mind the end goal to meet the requests of arrange
figuring. customer/server frameworks have developed more powerful, the figuring group has
recognized their numerous unmistakable preferences. Conveyed objects guarantee to alter the
development of scalable customer/server frameworks by giving modularized programming that
highlights tradable parts. Circulated objects mix the dissemination preferences of client/server
innovation with certifiable data contained in object-oriented models.
References
Khan, M.Y.A. and Sayed, M.A., 2017. A Simple Software Engineering Environment for Coming
Decades. no. January, pp.46-53.
Robi, F.R.H., Mostafa, V. and Khan, M.Y.A., 2016. A Novel Idea of Software Engineering
Environment for Coming Decades. International Journal of Engineering Science, 2411.
Perry, D.E., 2015. A framework for exploring unifying theories of empirical software
engineering. Science of Computer Programming, 101, pp.99-123.