Enterprise Architecture Executable Patterns: Enterprise Architecture - Replacing Models with Executable Patterns

0Citations
Citations of this article
9Readers
Mendeley users who have this article in their library.
Get full text

Abstract

Using executable Enterprise Architecture patterns replaces the traditional engineering approach of using models to guide software development. This is accomplished by combining Enterprise Architecture principles, ontology reasoning, and Service Component Architecture into an executable environment. Creating this environment is the motivation for the OTTER project (Ontology Technology That Executes Real-time). This environment sets the Enterprise Architecture as the foundation for component service development and execution. In using this environment, Enterprise Architecture cannot be overlooked or bypassed during information systems development. This results in reducing the complications of application integration and data-sharing which reduces costs and problems. Protégé is used to define the layers of the Enterprise Architecture. These layers are mapped to Service Component Architecture standards to provide real-time execution of processes. Information access and service component access are both provided by OTTER using OWL data expressions. This use of OWL data expressions is an alternative to using XML web services for service access and SQL for relational database access. © Springer-Verlag Berlin Heidelberg 2013.

Cite

CITATION STYLE

APA

Tinsley, T. A. (2013). Enterprise Architecture Executable Patterns: Enterprise Architecture - Replacing Models with Executable Patterns. In Communications in Computer and Information Science (Vol. 348, pp. 294–306). Springer Verlag. https://doi.org/10.1007/978-3-642-37186-8_19

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free