scholarly journals USING SERVICE-ORIENTED ARCHITECTURE APPROACH FOR MULTIPLE USER INTERFACE SOFTWARE DEVELOPMENT

2016 ◽  
Author(s):  
Roman Arefev
Keyword(s):  
User Interface ◽  
Software Development ◽  
Service Oriented Architecture ◽  
Multiple User ◽  
Service Oriented

Design and Development of a Multi-Agent E-Learning System

2016 ◽  
pp. 390-447
Author(s):  
Terje Kristensen ◽  
Marius Dyngeland
Keyword(s):  
Software Development ◽  
Service Oriented Architecture ◽  
Learning System ◽  
Agent Architecture ◽  
Quality Requirements ◽  
Client Server ◽  
Dynamic Content ◽  
Service Oriented ◽  
E Learning ◽  
Multi Agent

In this paper the authors present the design and software development of an E-learning system based on a multi-agent (MAS) architecture. The multi-agent architecture is established on the client-server model. The MAS architecture is combined with the Dynamic Content Manager (DCM) model of E-learning developed at Bergen University College, Norway. The authors first present the quality requirements of the system before they describe the architectural decisions taken. They then evaluate and discuss the benefits of using a multi-agent architecture. Finally, the MAS architecture is compared with a pure service-oriented architecture (SOA) to observe that a MAS architecture has a lot of the same qualities as this architecture, in addition to some new ones.

Design and Development of a Multi-Agent E-Learning System

2015 ◽  
Vol 7 (2) ◽  
pp. 19-74 ◽  
Author(s):  
Terje Kristensen ◽  
Marius Dyngeland
Keyword(s):  
Software Development ◽  
Service Oriented Architecture ◽  
Learning System ◽  
Agent Architecture ◽  
Quality Requirements ◽  
Client Server ◽  
Dynamic Content ◽  
Service Oriented ◽  
E Learning ◽  
Multi Agent

In this paper the authors present the design and software development of an E-learning system based on a multi-agent (MAS) architecture. The multi-agent architecture is established on the client-server model. The MAS architecture is combined with the Dynamic Content Manager (DCM) model of E-learning developed at Bergen University College, Norway. The authors first present the quality requirements of the system before they describe the architectural decisions taken. They then evaluate and discuss the benefits of using a multi-agent architecture. Finally, the MAS architecture is compared with a pure service-oriented architecture (SOA) to observe that a MAS architecture has a lot of the same qualities as this architecture, in addition to some new ones.

scholarly journals Técnicas para la Enseñanza de Desarrollo de Software en Alumnos de Educación Superior

2019 ◽  
pp. 1-6
Author(s):  
Josue Martínez-Mireles ◽  
Marco García-Márquez ◽  
Porfirio Espejel-Flores ◽  
Jazmín Rodríguez-Flores
Keyword(s):  
Software Development ◽  
Learning Styles ◽  
Learning Style ◽  
Undergraduate Students ◽  
Service Oriented Architecture ◽  
Neurolinguistic Programming ◽  
Undergraduate Level ◽  
Development Methodology ◽  
Key Factor ◽  
Service Oriented

Undergraduate level education has become more complex, due to the environments where the undergraduate students have grown, they develop several kinds of learning styles, generating heterogeneous groups. Software development teaching is very difficult because of that, specifically, it becomes complex because not everyone has the same skills. The study was developed at the Polytechnic University of Pachuca, analyzing the results in two groups of students of the Service Oriented Architecture course. It consisted in the organization and monitoring of software development projects, different techniques were implemented, such as: the software development methodology, project administration formats, learning style diagnosys, based on the application of Neurolinguistic Programming Instruments (NLP) to students of third year. The time invested by each student with respect to the total time ratio of the development team, is a key factor to be considered during project assignment and assessment. It’s shown the results of the application of differents teaching techniques during the learning process.

scholarly journals DevOps-Driven Approach to Development in Cloud

2021 ◽  
Author(s):  
Anita Nair
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Service Oriented Architecture ◽  
Architectural Style ◽  
Time To Market ◽  
Development Life Cycle ◽  
Service Oriented ◽  
Software Development Life Cycle ◽  
Waterfall Model ◽  
The Way

<div> <p>DevOps, a prevalent terminology in organizations today, has evolved as a paradigm that once was SDLC. From the mammoth concept of the “WaterFall Model” to the more recent Agile Framework and the emerging DevOps methodology, the Software Development Life Cycle saw a huge business win in “Time to market”, over several other advantages like risk aversion, flexibility, requirement readjustments, collaboration etc. to name a few. This whitepaper elaborates on the various salient features of DevOps that shapes the way software releases are made today. DevOps is most suited to Cloud and this paper explains the way the two technologies synergize. Service Oriented Architecture is an architectural style that is essential in simplifying the business and this paper explains how DevOps facilitates creation of granular services that ultimately helps in attaining flexibility and agility of development and operations in Cloud.</p> </div>

scholarly journals EDSOA: An Event-Driven Service-Oriented Architecture Model For Enterprise Applications

2011 ◽  
Vol 14 (3) ◽  
Author(s):  
Karina Hauser ◽  
Helgi S. Sigurdsson ◽  
Katherine M. Chudoba
Keyword(s):  
Software Development ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Architecture Model ◽  
Software Complexity ◽  
Enterprise Applications ◽  
Event Driven ◽  
Service Oriented

Enterprise Applications are difficult to implement and maintain because they require a monolith of code to incorporate required business processes. Service-oriented architecture is one solution, but challenges of dependency and software complexity remain. We propose Event-Driven Service-Oriented Architecture, which combines the benefits of component-based software development, event-driven architecture, and SOA.

Coordination of a Service Oriented Architecture

2011 ◽  
pp. 157-162
Author(s):  
Jason Nichols ◽  
Andrew Chen
Keyword(s):  
Software Development ◽  
Software Reuse ◽  
Return On Investment ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Development Stage ◽  
Service Orientation ◽  
Client Server ◽  
Coordination Costs ◽  
Service Oriented

As e-commerce models and applications have been widely employed in today’s business environment, a new movement to so-called dynamic e-business has been urged to advance e-commerce applications to the next level: simplifying business interaction over the Web through effective and widely accepted messaging and data encapsulation standards (Chen, Chen, & Shao, 2003). Gisolfi (2001) defined dynamic e-business as the next generation of e-business focusing on the integration and infrastructure complexities by leveraging the benefits of Internet standards and common infrastructure to produce optimal efficiencies for intra- and inter-enterprise computing. Infrastructure for both inter- and intra-organizational computing has undergone a significant maturation process from centralized mainframe computing to early distributed client/server environments, and most recently taking on a service orientation (Roure, 2003). Service-oriented architecture (SOA) represents the framework for the latest generation of service-based computing where once proprietary and monolithic applications are broken down into components and exposed through open standards for use by both internal and external enterprise partners. The SOA paradigm is argued to include in its list of benefits a higher return on investment, increased software reuse, and the capability to support dynamic service assembly (Stevens, 2005). An increased return on investment is achieved through the componentization of application capabilities. The argument goes that the usefulness of a component (defined here as bounded by its functional capabilities to one distinct business domain) outlives the usefulness of an application (since applications are developed to support a subset of processes in a domain while a component is not constrained, by definition, to any particular process set). Within the SOA paradigm, the development of applications to support a set of business processes is replaced with the connecting of components from distinct business domains in order to address the computational needs of a particular process. It is clear, then, that SOA has a positive impact on software reuse as components are leveraged across many configurations to address the specific computational needs of many different processes. To this end, one can map the reusability of components in an SOA context to the third argued benefit—dynamic service assembly. Dynamic service assembly means that components are not developed with the complete set of application scenarios in mind. Instead, components are created to exemplify the information and computational contribution of a specific business domain. The choice of how these components are used later on is therefore not limited to assumptions of usage made at the development stage. Indeed, it is possible that the most valuable use for any given component may not exist at the time of component development. As business processes evolve dynamically over time and business needs for information and computational support change, a service orientation leveraging components that are developed in the absence of constraints for how they might be utilized allows for dynamic reconfiguration of services in order to adapt to changes in the business processes themselves. This ability to reconfigure increases reuse and extends the lifetime (from a value perspective) of the components that are developed. This, in turn, feeds back to an increased return on the investment in software development which is typically the primary motivation for buy-in to the SOA paradigm. Similar to the shift from a mainframe to a client/server architecture (Malone & Smith, 1988), however, the shift to a service-oriented architecture requires consideration of costs associated with coordinating activities in this new environment. Management of these coordination costs will be necessary in order to preserve the purported increases in return on investment. Put simply, if the return on investments in software development increases but the costs associated with leveraging the developed information technology artifacts for business value also increases, then it is possible that the value created will be diminished or even overrun by the operational expense of coordinating use. In order to ensure that this is not the case, this article leverages a coordination theory approach to first understand the impact that a shift to service-oriented architecture will have on the cost of coordinating activity both within and across the firm, and second to make recommendations for how these coordination costs can be addressed to preserve the return on investment from a shift to service-oriented architecture.

Sign in / Sign up

Export Citation Format

Share Document