Arquitectura Orientada a Servicios La 'Arquitectura Orientada a Servicios' (en inglés Service Oriented Architecture), es un paradigma de arquitectura para diseñar y desarrollar sistemas distribuidos. Las soluciones SOA han sido creadas para satisfacer los objetivos de negocio las cuales incluyen facilidad y flexibilidad de integración con sistemas legados, alineación directa a los procesos de negocio reduciendo costos de implementación, innovación de servicios a clientes y una adaptación ágil ante cambios incluyendo reacción temprana ante la competitividad.  Permite la creación de sistemas de información altamente escalables que reflejan el negocio de la organización, a su vez brinda una forma bien definida de exposición e invocación de servicios (comúnmente pero no exclusivamente servicios web), lo cual facilita la interacción entre diferentes sistemas propios o de terceros. SOA define las siguientes capas de software: Terminología[editar] Diseño y desarrollo de SOA[editar] Lenguajes de alto nivel[editar]
Business Process Execution Language for Web Service Messaging and Transaction Coordination : General reference document on standards related to coordination of messages/transactions, as well as choreography, workflow, and business brocess modeling, especially in the Web Services arena. [January 14, 2008] OASIS announced that consortium members have submitted a charter proposal for a new WS-BPEL Extension for People (BPEL4People) Technical Committee. Companies sponsoring the proposal include Active Endpoints, Adobe, BEA, IBM, Oracle, SAP, Software AG, and Sun Microsystems. The designated TC Convenor is Jeff Mischkinsky (Oracle). This Technical Committee proposal follows a June 2007 statement from a group of six technology vendors, including Active Endpoints, Adobe, BEA Systems, IBM, Oracle, and SAP AG, announcing that the two-part BPEL4People specification would be submitted to OASIS in the near future. [November 28, 2007] "Transactional BPEL Processes with AO4BPEL Aspects." [November 09, 2005] "WS-BPEL Language Basics."
Software Product Lines A software product line (SPL) is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. Software product lines are emerging as a viable and important development paradigm allowing companies to realize order-of-magnitude improvements in time to market, cost, productivity, quality, and other business drivers. Software product line engineering can also enable rapid market entry and flexible response, and provide a capability for mass customization. We are working to make software product line practice a dependable low-risk high-payoff practice that combines the necessary business and technical approaches to achieve success. Benefits Product lines can help organizations overcome the problems caused by resource shortages. Learn More
Go Flow » Blog Archive » BPMN, XPDL and BPEL in your spare time I got the chance to participate on a panel session at the BPM Think Tank in Arlington VA on May 24 2006 on the subject of BPM Standards. Richard Mark Soley was on one end representing OMG and the BPMN standard. John Evdemon from Microsoft was on the other end representing BPEL for which he is the TC Co-Chairman. I was between them representing XPDL from WfMC. BPEL is an “execution language”. XPDL is a process design format. The goal of BPEL is to provide a definition of web service orchestration, the underlying sequence of interactions, the flow of data from point to point. The goal of XPDL is to store and exchange the process diagram. The different usage is best represented the diagram below. The XPDL file can provide this design interchange because it offers one for one representation of the original BPMN process diagram; it can be written, and re-read to recover the original diagram. The importance of process design interchange will increase as the market matures. Like this:
Service - Oriented Architecture See also the client-server model, a progenitor concept A Service-Oriented Architecture (SOA) is a design pattern in which software/application components provide services to other software/application components via a protocol, typically over a network and in a loosely-coupled way. The principles of service-orientation are independent of any vendor, product or technology. A service is a self-contained unit of functionality, such as retrieving an online bank statement. By that definition, a service is a discretely invokable operation. However, in the Web Services Definition Language (WSDL), a service is an interface definition that may list several discrete services/operations. Services can be combined to provide the complete functionality of a large software application. A SOA makes it easier for software components on computers connected over a network to cooperate. Definitions The Open Group's definition is: Overview SOA framework Design concept
Open SOA Collaboration If you feel you have reached this page in error, please contact the web site owner: It may be possible to restore access to this site by following these instructions for clearing your dns cache. If you are the web site owner, it is possible you have reached this page because: The IP address has changed.There has been a server misconfiguration.The site may have been moved to a different server. If you are the owner of this website and were not expecting to see this page, please contact your hosting provider. Note: Although this site is running cPanel, WebHost Manager, and Apache software it almost certainly has no other connection to cPanel Inc. or the Apache Group. About cPanel: cPanel is a leading provider of software for the webhosting industry. About Apache HTTP Server: The Apache HTTP Server is an open source web server which powers many of the world's web sites.
Dificultades de la MDA ¿Por qué un Modelo? Conceptual model (computer science) This is often used for defining different processes in a particular Company or Institute. Fowler, Martin: Analysis Patterns, Reusable object models, Addison-Wesley Longman, 1997. ISBN 0-201-89542-0.Stewart Robinson, Roger Brooks, Kathy Kotiadis, and Durk-Jouke Van Der Zee (Eds.): Conceptual Modeling for Discrete-Event Simulation, 2010.
Round-trip engineering Round-trip engineering (RTE) is a functionality of software development tools that synchronizes two or more related software artifacts, such as, source code, models, configuration files, and other documents. The need for round-trip engineering arises when the same information is present in multiple artifacts and therefore an inconsistency may occur if not all artifacts are consistently updated to reflect a given change. For example, some piece of information was added to/changed in only one artifact and, as a result, it became missing in/inconsistent with the other artifacts. Round-trip engineering is closely related to traditional software engineering disciplines: forward engineering (creating software from specifications), reverse engineering (creating specifications from existing software), and reengineering (understanding existing software and modifying it).
Unified Modeling Language The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system. It was created and developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software during 1994–95 with further development led by them through 1996. In 1997 it was adopted as a standard by the Object Management Group (OMG), and has been managed by this organization ever since. In 2000 the Unified Modeling Language was also accepted by the International Organization for Standardization (ISO) as an approved ISO standard. Since then it has been periodically revised to cover the latest revision of UML. Overview A collage of UML diagrams The Unified Modeling Language (UML) offers a way to visualize a system's architectural blueprints in a diagram (see image), including elements such as: History History of object-oriented methods and notation Before UML 1.x 
Estado Actual del Modelado Framework-specific modeling language A framework-specific modeling language  (FSML) is a kind of domain-specific modeling language which is designed for an object-oriented application framework. FSMLs define framework-provided abstractions as FSML concepts and decompose the abstractions into features. The features represent implementation steps or choices. A FSML concept can be configured by selecting features and providing values for features. Applications FSMLs are used in model-driven development for creating models or specifications of software to be built. the creation of the models from the framework completion code (that is, automated reverse engineering)the creation of the framework completion code from the models (that is, automated forward engineering)code verification through constraint checking on the modelautomated round-trip engineering Examples Eclipse Workbench Part Interaction FSML   References Jump up ^ M. See also