108,388 research outputs found

    Enterprise Architecture Modeling, Design and Transformation: Defining the Missing Links

    Get PDF
    Outline - • Propose a unifying conceptual framework guiding the “front-end” of planned enterprise change (transformation) management process • Enterprise architecture design process (enterprise architecting) • Choice of enterprise architecture for emphasis • Enterprise architecture modeling strategies • Transition moves available for enterprise transformation • Show how the framework links together a number of the key design decisions that need to be considered simultaneously, under alternative combinations of major contingency condition

    An enterprise modeling and integration framework based on knowledge discovery and data mining

    Get PDF
    This paper deals with the conceptual design and development of an enterprise modeling and integration framework using knowledge discovery and data mining. First, the paper briefly presents the background and current state-of-the-art of knowledge discovery in databases and data mining systems and projects. Next, enterprise knowledge engineering is dealt with. The paper suggests a novel approach of utilizing existing enterprise reference architectures, integration and modeling frameworks by the introduction of new enterprise views such as mining and knowledge views. An extension and a generic exploration of the information view that already exists within some enterprise models are also proposed. The Zachman Framework for Enterprise Architecture is also outlined versus the existing architectures and the proposed enterprise framework. The main contribution of this paper is the identification and definition of a common knowledge enterprise model which represents an original combination between the previous projects on enterprise architectures and the Object Management Group (OMG) models and standards. The identified common knowledge enterprise model has therefore been designed using the OMG's Model-Driven Architecture (MDA) and Common Warehouse MetaModel (CWM), and it also follows the RM-ODP (ISO/OSI). It has been partially implemented in Java(TM), Enterprise JavaBeans (EJB) and Corba/IDL. Finally, the advantages and limitations of the proposed enterprise model are outlined

    Enterprise architectonics as a conceptual device to support a fundamental understanding of enterprise architecture

    Get PDF
    Evidence of the interest in enterprise architecture (EA) is seen in the number of enterprise architecture frameworks (EAF) in existence. An EAF is responsible for the realisation of an EA, and therefore acts as a container for the terminology of EA. The lack of acceptance of terms and definitions, coupled with the phenomenon of the large number of EAFs, indicate a silo type understanding of what EA is, which leads to a lack of clarity in the conceptual foundations of EA. By following a design science research (DSR) approach, a conceptual artefact (an enterprise architectonic (EAt)) is created to address the lack of clarity in the conceptual foundations of EA thinking and practice. The EAt serves as a conceptual device to represent the fundamental understanding of EA in terms of concepts and their relationships. The content of the EAt is derived from applying a structured interpretation method (SIM) to three prominent EAFs (The Open Group Architecture Framework, the Department of Defense Architecture Framework and the Zachman Framework for Enterprise Architecture). The SIM’s results are an EA understanding that consists of an EA claim: EA is similar in intent to the enterprise as a worldview is to the world. It is supported by six EA propositions: Proposition 1: EA’s underlying theoretical knowledge is in a pre-suppositional state. Proposition 2: EA is a description of the structure of the systems of an enterprise. Proposition 3: EA represents the enterprise in time-oriented architectures such as an as-is, to-be and has-been architecture. Proposition 4: EA translates the values/strategy of the enterprise into operational systems appropriate to the information society. Proposition 5: EA provides a means to manage decisions about the IT/IS management and implementation in the enterprise. Proposition 6: EA captures a representation of the enterprise in the form of a model or set of models. The six EA propositions are analysed through the lens of Heidegger's equipment analysis, to produce a set of architectonic elements. These elements are arranged in the EAt to create a conceptual device to support the fundamental understanding of EA.Centre for Applied Information and CommunicationPh. D. (Information Systems

    Propuesta de arquitectura empresarial para el grupo de perforación de Ecopetrol usando el marco de referencia TOGAF

    Get PDF
    Enterprise architecture allows to harmonize a company’s technological components by defining a north star accord-ing to corporate goals and strategies.  Ecopetrol-ICP’s geomechanics group needs to have elements to support software development for real time drilling monitoring. This work presents a conceptual framework for enterprise architecture focused on the optimization of information flow to support strategic decision-making by creating a soft-ware development roadmap to ease IT management for ICP’s geomechanics research group. In the Enterprise Architecture design with TOGAF the first six phases of the ADM cycle were implemented. La arquitectura empresarial permite armonizar los componentes tecnológicos de una organización definiendo un norte acorde con los objetivos y estrategias corporativas. En el grupo de geomecánica del ICP se quiere contar con elementos que sean de apoyo para generar desarrollos de herramientas software que permitan monitorear la perforación de pozos petroleros en tiempo real. Este trabajo presenta un marco conceptual de arquitectura empresarial enfocado en la optimización del flujo de información para apoyar la toma de decisiones estratégicas, generando una hoja de ruta de desarrollo de herramientas software que faciliten la gestión de información para el grupo de geomecánica del ICP. En el diseño de la arquitectura empresarial se trabajó en las seis primeras fases de la metodología ADM que proporciona TOGAF.   Enterprise architecture allows to harmonize a company’s technological components by defining a north star accord-ing to corporate goals and strategies.  Ecopetrol-ICP’s geomechanics group needs to have elements to support software development for real time drilling monitoring. This work presents a conceptual framework for enterprise architecture focused on the optimization of information flow to support strategic decision-making by creating a soft-ware development roadmap to ease IT management for ICP’s geomechanics research group. In the Enterprise Architecture design with TOGAF the first six phases of the ADM cycle were implemented.&nbsp

    Contextual Components of an Enterprise Architecture Framework for Pan-European eGovernment Services

    Get PDF
    Enterprise Architecture (EA) frameworks provide a wide range of architecture components. Contextual EA components provide the necessary guidance to design specific architectures in a given context e.g. for Pan-European Government Services (PEGS). Contextual EA components help to describe the background and scope of architecture work and provide a ground to tackle architecture challenges in an agreed way. The main contribution of this conceptual paper is to connect existing theoretical models as a basis to examine contextual components of an EA framework for PEGS. Three aspects are elaborated using a model-based approach: a Critical Success Factor Model, a Strategy Management Model and a Stakeholder Engagement Model. The identified models are aligned with EA standards and provide guidance to empirical research and to programs, projects and initiatives that wish to create interoperability architectures

    Distance support in-service engineering for the high energy laser

    Get PDF
    The U.S. Navy anticipates moving to a shipboard high-energy laser program of record in the fiscal year 2018 and achieving an initial operational capability by 2020. The design of a distance support capability within the high-energy laser system was expected to assist the Navy in reaching this goal. This capstone project explored the current Navy architecture for distance support and applied system engineering methodologies to develop a conceptual distance support framework with application to the high-energy laser system. A model and simulation of distance support functions were developed and used to analyze the feasibility in terms of performance, cost, and risk. Results of this capstone study showed that the implementation of distance support for the high-energy laser system is feasible and would reduce the total ownership cost over the life of the program. Furthermore, the capstone shows that moving toward the team’s recommended distance support framework will address current gaps in the Navy distance support architecture and will provide a methodology tailored to modern enterprise naval systems.http://archive.org/details/distancesupporti1094545248Approved for public release; distribution is unlimited

    An Integrated Enterprise Architecture Framework for Business-IT Alignment

    Get PDF
    When different businesses want to integrate part of their processes and IT, they need to relate their enterprise architecture frameworks. An enterprise architecture framework (EAF) is a conceptual framework for describing the architecture of a business and its information technology (IT), and their alignment. In this paper we provide an integration among some well-known EAFs (Zachman, Four-domain, TOGAF and RM-ODP) and produce an integrated EAF (IEAF) that can be used as common framework to communicate about EAFs of differrent businesses and relate them to each other

    A goal-oriented requirements modelling language for enterprise architecture

    Get PDF
    Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain

    The impact of conceptual structures on transaction and enterprise architecture practices

    Get PDF
    This research hypothesises is Conceptual Structures using the Resource Event Agent (REA) ontology adds value when defining a Transaction Oriented Architecture (TOA) for Enterprise Systems. Enterprise Systems drive global economic growth through well-designed implementations that provide organisations with multiple benefits, including streamlined business processes, increased efficiencies, improved productivity and decreased costs. Conversely, poorly implemented Enterprise Systems can lead to poor operating results. Most Enterprise Systems still use traditional methods of storing economic data mirroring the double-entry bookkeeping system, which can cause several problems, including data loss and repetition. Enterprise Systems must capture transaction data in a format available to multiple business processes to fulfil their goals. This thesis provides an overview of the currently available frameworks for Enterprise Architecture design. It details the problems that are observed and experienced during the completion of real-world Enterprise System development projects. The basis of the Transaction Concept is then presented as the general solution, leading to a TOA for Enterprise Systems. The Transaction Pyramid describes TOA through three layers of transactions: Enterprise, Business, and Database. The Design Science Research Methodology (DSRM) is used as the primary research methodology to provide a framework to this research. Together with the secondary research method of Action Research to provide a more granular basis for DSRM Step 3 : "Design and development", which required multiple minor iterations of the cyclical process of Action Research to produce the required artefacts. The case study approach is used also as a secondary research method for empirical inquiry and investigation required for DSRM step 4: "Demonstration". A Knowledge Management System is defined to validate TOA, and artefacts are implemented for an Automated REA (AREA) based on Protégé Frames to underpin TOA as a Proof of Concept. AREA provides a fully- edged, TOA design tool for Enterprise Architecture using the REA ontology. AREA's Knowledge Repository uses Conceptual Structures through a) the ISO Common Logic standard's Conceptual Graph Interchange Format (CGIF) to store and transmit the TOA using an REA ontology, and b) Formal Concept Analysis (FCA) for validation. AREA is then demonstrated and evaluated using two industrial case studies as exemplars. These Findings support the research's hypothesis and its contribution to knowledge
    corecore