Objet-Oriented, Componet-Based, Agent Orientd and service-Orientd Paradigmas in software Architectures

Objet-Oriented, Componet-Based, Agent Orientd and service-Orientd Paradigmas in software Architectures

1. The appearance of new technologies and new paradigms have caused conflicts between terms and definitions. this is why it is necessary to clarify the limits of comparing the qualitative and quantitative variables between the paradigms

   • A software development paradigm has its own particular style of developing IT solutions, in terms of analysis, design and developmen
   • When a paradigm is well suited to an implementation issue, it reduces the need for a costly integration process and isolated solution tests by using a common conceptual framework
   • a top-down approach
     • These approaches will assist in clarifying the conceptual and technical misinterpretations of these different paradigms.

2. Object-oriented paradigm

   • It consists of the definition and interaction of software modules called objects: an object represents a concept, an idea or any entity in the physical world
     • has been completed with the remote method invocation (RMI) mechanism
       • is mainly based on the principle of object request broker
   • architecture is used to describe a system as a collection of classes (entities to be abstracted and the encapsulation of functionalities) that can have objects (instances) and communicate between themselves by sending messages

3. Component-based paradigm

   • The creatror implemented an infrastructure on Unix using pipeline components and filters
     • Used in response to the failure of the object-oriented approach to meet the requirements of reuse and composition
     • it is highly advantageous to be able to reuse an existing code in the form of a component
   • Component-based software architectures describe systems as a set of components (processing or storage units) that communicate with each other via connectors (interaction units)
     • Search build reusable off-the-shelf component-based heterogeneous systems

4. The agent-oriented paradigm

   • competing interactive autonomous entities
     • an agent is treated as a Agents are distinguished by their social ability to cooperate, coordinate and negotiate with each other
       • Agents can be classified into the following two categories
         • Reactive agents, which wait for an event to happen before responding to changes in their environment
         • Proactive agents, which take decisions on their own initiative in their environment
         • Software agents have their own control thread , encapsulating not only their code and state
   • the concept of software architecture is replaced by a further knowledge-driven concept called organization
     • is made up of a set of roles and relationships between these roles.

5. service-oriented

   • The service is a software entity that represents a specific function
     • It is also an autonomous building block that does not depend on any context or external service
       • that enables a range of services to communicate with each other
   • A conceptual framework to organize the construction of application based on services.
     • introduces the concepts of service providers and consumers
       • A service provider is the actor responsible for the development, deployment, execution and maintenance of the service when it is required.