Context-Based Technology Evaluation Collection
• Collection
Publisher
Software Engineering Institute
Topic or Tag
Abstract
To determine the fit between a system and a technology, it is necessary to evaluate the technology in the context in which it will be used. We've reported on our investigation of several technologies, including those in this collection.
Business Process Execution Language (BPEL)
Description of Technology: Composition languages allow business processes available through web services to be combined into new processes. BPEL is the most popular composition language.
Context of Investigation: Can different business process management tools exchange process definitions? Can business process management tools hide the complexity of process orchestration, or does IT staff have to be trained in business process management concepts? How easy will it be to change deployed business processes in case of a merger?
Model Driven Architecture (MDA)
Description of Technology: MDA literature, and some MDA tool vendors, claim that the MDA approach (1) reduces development time, and (2) frees the developer to focus on business logic rather than on target platform and infrastructure details. Aside from being a valid and beneficial approach to software development, this should allow quick and easy deployment of applications, as target platforms and underlying infrastructure change. If realized, these advantages would significantly benefit interoperability.
Context of Investigation: A military human resources system (Military personnel are often reassigned to new locations, which triggers additional processes such as the actual reassignment, payroll adjustments, and flight booking.)
Open Grid Services Architecture (OGSA)
Description of Technology: Computing power in terms of processing power, storage capability, and bandwidth has continuously increased; however, computing needs have become even more demanding. Grid computing, as implemented through OGSA, possibly provides a solution to some challenges by allowing collaboration and resource sharing between organizations.
Context of Investigation: A large volume of data is generated from a continuous data source, needs to be stored and retrieved to be processed, and used by data consumers once processed.
OWL Web Ontology Language for Services (OWL-S)
Description of Technology: OWL-S provides developers with a strong language to describe the properties and capabilities of web services for interpretation by a computer system in an automated manner. The goal of OWL-S is to enable applications to discover, compose, and invoke web services dynamically.
Context of Investigation: Map services—available in a diverse selection of classifications and formats, with distinct and meaningful coordinates
Web Services
Description of Technology: It is claimed that web services are easy to implement and can integrate systems between platforms and that numerous web services are available from public repositories.
Context of Investigation: A back-office system
Web Services Security (Single-Sign-On)
Description of Technology: Many organizations have legacy software systems that are difficult to integrate with other applications because they were developed as stand-alone applications. One solution is provide interfaces and expose them as web services. However, this approach can force users of an application that uses the web services created for the legacy systems to have to log in separately to each system. The goal of single-sign-on (SSO) is to avoid this situation.
Context of Investigation: Which combination of technologies should be chosen to implement SSO? How much effort will it take to develop an SSO solution? What is the impact on execution time of the SSO solution? How can access control be realized when using SSO?
Collection Items
T-Check in Technologies for Interoperability: Business Process Management in a Web Services Context
• Technical Note
By Fabian Hueppi, Lutz Wrage, Grace Lewis
This technical note presents an investigation of the Business Process Execution Language, a popular BPM technology used to describe, analyze, execute, and monitor business processes.
ReadModel Problems in Technologies for Interoperability: Model-Driven Architecture
• Technical Note
By Grace Lewis, Lutz Wrage
This 2005 report looks at Model-Driven Architecture (MDA) as one of many technologies for accomplishing interoperability.
ReadT-Check for Technologies for Interoperability: Open Grid Services Architecture (OGSA)—Part 1 Parent SEI Program
• Technical Note
By Soumya Simanta, Grace Lewis, Lutz Wrage
This report investigates Open Grid Services Architecture (OGSA), one of the many technologies for accomplishing interoperability, using the T-Check technique.
ReadModel Problems in Technologies for Interoperability: OWL Web Ontology Language for Services (OWL-S)
• Technical Note
By Chris Metcalf C., Grace Lewis
This 2006 report presents the results of applying the model problem approach to examine the feasibility of using OWL-S to allow applications to automatically discover, compose, and invoke services in …
ReadModel Problems in Technologies for Interoperability: Web Services
• Technical Note
By Grace Lewis, Lutz Wrage
This 2006 report presents the results of applying the model problem approach in an initial investigation of the potential of Web services to enable interoperability.
ReadT-Check in Technologies for Interoperability: Web Services and Security—Single Sign-On
• Technical Note
By Lutz Wrage, Soumya Simanta, Grace Lewis, Saul Jaspan
This technical note presents the results of applying the T-Check approach in an initial investigation of two Web services standards, WS-Security and SAML, to create an SSO solution that works …
Read