Paradigms in Software Architectures

Paradigms in Software Architectures

1. A programming paradigm is a fundamental style of computer programming that deals with how solutions to problems must be formulated in a programming la nguage

   • A programming paradigm is a fundamental style of computer programming that deals with how solutions to problems must be formulated in a programming la nguage
     • Approaches for integrating development paradigms
       • Active object-oriented model
         • Object-oriented and agent.oriented combination
         • Which represents an object that conceptually runs on its own thread and provides an asynchronous execution of method invocations
       • Agent-oriented and component-based combination
         • Try to extebd the agent-oriented paradigm with the concepts and mechanism of the component-based paradigms
         • These adaptation points allow for service selection at runtime according to the specifications of the functional and non-functional properties in the model
       • Combine the agent-oriented paradigm with SOA
         • It's primarily motivated by the need for dynimic service compotition where agents are used to dynamically search and select servicer during the execution
         • These approaches deal mainly with aspects linked to the semacntic description and research of services
   • A programming paradigm is a fundamental style of computer programming that deals with how solutions to problems must be formulated in a programming la nguage
     • A programming paradigm is a fundamental style of computer programming that deals with how solutions to problems must be formulated in a programming la nguage

2. Object-oriented paradigm

   • It consists of the definition and interaction of software modules called onjects
     • An object represents a concept, an idea or any entity in the physical world
     • It is able to communicate with other objects
   • Is to represent these objects and their relationships
   • Object-oriented approach is considered as the reference model for other approaches

3. Component based paradigm

   • The component-based approach extends the onject-oriented paradigm by stressing the importance of reuse
   • It is highly advantageos to able to reuse an existing code in the form of a component
   • The component-based approach, aclear distinction is made between the development of a component and that of a system.

4. Agent.oriented paradigm

   • In these models, an agent is treated as a self-contained entity with certain capabilitues that enable it to carry out its services or use the services of another agent throught interaction
     • In the agent model, communication is usually asynchronous
       • Agent can initiate an internal or external autonomous behavior at any time, and not only when it recives a message
   • Agents can be classified in two categories
     • Reactive agents
     • Proactive agents
   • Software agents have their owm control thread, encapsulating not only their code and state, but their invocation too

5. Service-oriented paradigm

   • Inspired by real-world organization methods in trade between multinationals, and is based on the classic notion of service
     • The serice is a software entity that represents a specific function.
   • Withstand increasingly volatile and heterogeneous envirom¿nmn¿ents
     • Coarsed-granied
       • Operations offered by a service encapsulate several funcionts and operate on a wide range of data
     • Interface
       • A service can implement several interfaces and several services can implement a common interface
     • Architecture
       • Each service is described by an architecture that enables us to understand what it does
     • discoverable
       • Before a service can be called (invoke), it has to be found (look-up)
     • Single instance
       • Unlike components that are instantiated on demand and can have multiple instances at the same time, it is a single service
     • Loosely coupled
       • Services are connected to costomers and other services via standarsds
     • SOA is essentially a collection of services that interact and communicate with each other

6. Software Architecture

   • A good software architecture desing can lead to a product that meets customer needs and can easily be updated
     • Object-oriented software architecture
       • Modeling creates diagrams, text specifications and a programming cource code based on object-oriented conceots to describe a software system
         • UML
       • Is used to describe a system as a collection of classes
     • Component-based software architecture
       • Describe systems as a set of components that communicate with each other via connectors
       • Interactions are separate from the calculations
       • The overall description of system architecture can be specified before completing the construction of its components
     • Agent-oriented software architecture
       • MAS is a paradigm for understanding and building distributed systems
       • The social capacity for cooperation, coordination and negotiation between agents is one of their main characteristics
       • A role is an abstraction of an agent
     • Service-oriented architecture
       • Organize the construction of application based in services
       • Supports distribution as well as the management of non-functional properties
       • it Does not support the aspect of competition

7. Conceptual dofferences

   • This approach facilities incremental development and exploitation of knowledge
     • Difference in utilization and owner's responsibility
     • Difference in coupling
     • Difference in granularity
     • Difference in cooperation and problem-solving