ROLE OF ENTERPRISE ARCHITECTURE IN HEALTHCARE ORGANIZATIONS AND KNOWLEDGE-BASED MEDICAL DIAGNOSIS SYSTEM

Enterprise architecture (EA) is a tool that aligns organization’s business-process with application and information technology (IT) through EAmodels. This EA model allows the organization to cut off unnecessary IT expenses and determines the future and current IT requirements and boosts organizational performance. Enterprise architecture may be employed in every firm where the firm or organization requires configurations between information technology and business functions. This research investigates the role of enterprise architecture in healthcare organizations and suggests the suitable EA framework for knowledge-based medical diagnostic system for EA modeling by comparing the two most widely used EA frameworks. The results of the comparison identified that the proposed EA has a better framework for knowledge-based medical diagnostic system.

Where do we find services in enterprise architectures? A comparative approach

In recent years, enterprise architecture (EA) has captured growing attention as a means to systematically consolidate and interrelate diverse IT artefacts in order to provide holistic decision support. Since the emergence of Service-Oriented Architecture (SOA), many attempts have been made to incorporate SOA artefacts in existing EA frameworks. Yet the approaches taken to achieve this goal differ substantially for the most commonly used EA frameworks to date. This paper investigates and compares five widely used EA frameworks in the way they embrace the SOA paradigm. It identifies what SOA artefacts are considered to be in the respective EA frameworks and their relative position in the overall structure. The results show that services and related artefacts are far from being well-integrated constructs in current EA frameworks. The comparison presented in this paper will support practitioners in identifying an EA framework that provides SOA support in a way that matches their requirements and will hopefully inspire the academic EA and SOA communities to work on a closer integration of these architectures.

An organisational semiotics inspired information architecture: pervasive healthcare as a case study

Information architecture (IA) is defined as high level information requirements of an organisation. It is applied in areas such as information systems development, enterprise architecture, business processes management and organisational change management. Still, the lack of methods and theories prevents information architecture becoming a distinct discipline. Healthcare organisation is always seen as information intensive organisation, moreover in a pervasive healthcare environment. Pervasive healthcare aims to provide healthcare services to anyone, anywhere and anytime by incorporating mobile devices and wireless network. Information architecture hence plays an important role in information provisioning within the context of pervasive healthcare in order to support decision making and communication between clinician and patients. Organisational semiotics is one of the social technical approaches that contemplate information through the norms or activities performed within an organisation prior to pervasive healthcare implementation. This paper proposes a conceptual design of information architecture for pervasive healthcare. It is illustrated with a scenario of mental health patient monitoring.

Assessing the business risk of technology obsolescence through enterprise modelling

The problem of technology obsolescence in information intensive businesses (software and hardware no longer being supported and replaced by improved and different solutions) and a cost constrained market can severely increase costs and operational, and ultimately reputation risk. Although many businesses recognise technological obsolescence, the pervasive nature of technology often means they have little information to identify the risk and location of pending obsolescence and little money to apply to the solution. This paper presents a low cost structured method to identify obsolete software and the risk of their obsolescence where the structure of a business and its supporting IT resources can be captured, modelled, analysed and the risk to the business of technology obsolescence identified to enable remedial action using qualified obsolescence information. The technique is based on a structured modelling approach using enterprise architecture models and a heatmap algorithm to highlight high risk obsolescent elements. The method has been tested and applied in practice in two consulting studies carried out by Capgemini involving three UK police forces. However the generic technique could be applied to any industry based on plans to improve it using ontology framework methods. This paper contains details of enterprise architecture meta-models and related modelling.

Management practices and influences on IT architecture decisions: a case study in a telecom company

The study aims to analyze the IT architecture management practices associated with their degree of maturity and the influence of institutional and strategic factors on the decisions involved through a case study in a large telecom organization. The case study allowed us to identify practices that led the company to its current stage of maturity and identify practices that can lead the company to the next stage. The strategic influence was mentioned by most respondents and the institutional influence was present in decisions related to innovation and those dealing with a higher level of uncertainties.

Analisi della qualità dei dati in un’enterprise architecture utilizzando un sistema d’inferenza.

Lo scopo della tesi è definire un modello e identificare un sistema d’inferenza utile per l’analisi della qualità dei dati. Partendo da quanto descritto in ambito accademico e business, la definizione di un modello facilita l’analisi della qualità, fornendo una descrizione chiara delle tipologie di problemi a cui possono essere soggetti i dati. I diversi lavori in ambito accademico e business saranno confrontati per stabilire quali siano i problemi di qualità più diffusi, in modo da realizzare un modello che sia semplice e riutilizzabile. I sistemi d’inferenza saranno confrontati a livello teorico e pratico per individuare lo strumento più adatto nell’analisi della qualità dei dati in un caso applicativo. Il caso applicativo è caratterizzato da requisiti funzionali e non; il principale requisito funzionale è l’individuazione di problemi di qualità nei dati, mentre quello non funzionale è l’ usabilità dello strumento, per permettere ad un qualunque utente di esprimere dei controlli sulla qualità. Il caso applicativo considera dati di un’enterprise architecture reale ed è stato fornito dall’azienda Imola Informatica.

Value-oriented process modeling : integrating financial perspectives into business process re-design

Purpose – Financial information about costs and return on investments are of key importance to strategic decision-making but also in the context of process improvement or business engineering. In this paper we propose a value-oriented approach to business process modeling based on key concepts and metrics from operations and financial management, to aid decision making in process re-design projects on the basis of process models. Design/methodology/approach – We suggest a theoretically founded extension to current process modeling approaches, and delineate a framework as well as methodical support to incorporate financial information into process re-design. We use two case studies to evaluate the suggested approach. Findings – Based on two case studies, we show that the value-oriented process modeling approach facilitates and improves managerial decision-making in the context of process re-design. Research limitations / implications – We present design work and two case studies. More research is needed to more thoroughly evaluate the presented approach in a variety of real-life process modeling settings. Practical implications – We show how our approach enables decision makers to make investment decisions in process re-design projects, and also how other decisions, for instance in the context of enterprise architecture design, can be facilitated. Originality/value – This study reports on an attempt to integrate financial considerations into the act of process modeling, in order to provide more comprehensive decision making support in process re-design projects.

A comprehensive EA benefit realization model -- An exploratory study

Enterprise architecture (EA) management has be-come an intensively discussed approach to manage enterprise transformations. While there is a strong interest in EA frameworks and EA modeling, a lack of knowledge remains about the theoretical foundation of EA benefits. In this paper, we identify EA success factors and EA benefits through a literature review, and integrate these findings with the DeLone & McLean IS success model to propose a theoretical model explaining the realization of EA benefits. In addition, we con-ducted semi-structured interviews with EA experts for a preliminary validation and further exploration of the model. We see this model as a first step to gain insights in and start a discussion on the theory of EA benefit realization. In future research, we plan to empirically validate the proposed model.

The Three Drivers of Innovation

Innovation can be triggered by problems, constraints and opportunities. This paper discusses the different challenges related to these three drivers and how contemporary Business Process Management and Enterprise Architecture solutions can address these. A number of case studies show how proactive forms of innovation can be facilitated.

Model-driven service engineering in home telecare

Health care systems are highly dynamic not just due to developments and innovations in diagnosis and treatments, but also by virtue of emerging management techniques supported by modern information and communication technology. A multitude of stakeholders such as patients, nurses, general practitioners or social carers can be integrated by modeling complex interactions necessary for managing the provision and consumption of health care services. Furthermore, it is the availability of Service-oriented Architecture (SOA) that supports those integration efforts by enabling the flexible and reusable composition of autonomous, loosely-coupled and web-enabled software components. However, there is still the gap between SOA and predominantly business-oriented perspectives (e.g. business process models). The alignment of both views is crucial not just for the guided development of SOA but also for the sustainable evolution of holistic enterprise architectures. In this paper, we combine the Semantic Object Model (SOM) and the Business Process Modelling Notation (BPMN) towards a model-driven approach to service engineering. By addressing a business system in Home Telecare and deriving a business process model, which can eventually be controlled and executed by machines; in particular by composed web services, the full potential of a process-centric SOA is exploited.

Design theory for innovation of classroom-based information systems

This research used design science research methods to develop, instantiate, implement, and measure the acceptance of a novel software artefact. The primary purpose of this software artefact was to enhance data collection, improve its quality and enable its capture in classroom environments without distracting from the teaching activity. The artefact set is an iOS app, with supporting web services and technologies designed in response to teacher and pastoral care needs. System analysis and design used Enterprise Architecture methods. The novel component of the iOS app implemented proximity detection to identify the student through their iPad and automatically link to that student's data. The use of this novel software artefact and web services was trialled in a school setting, measuring user acceptance and system utility. This integrated system was shown to improve the accuracy, consistency, completeness and timeliness of captured data and the utility of the input and reporting systems.

Adequabilidade da arquitetura corporativa à gestão estratégica da Câmara dos Deputados

Analisa em que grau os elementos, métodos e artefatos preconizados pela arquitetura corporativa podem ser adequados ao processo de gestão estratégica na Câmara dos Deputados da República Federativa do Brasil. Essa adequabilidade se dá na medida em que houver o aproveitamento de esforço desprendido na implantação da gestão estratégica, em termos de criação de cultura organizacional, de aproveitamento de metodologias e artefatos já utilizados, e simultaneamente permitir sua evolução ao responder questões não atendidas pelo atual modelo. São descritos os principais conceitos relacionados à arquitetura corporativa e os modelos de referência Zachman e TOGAF 9.1, incluindo o processo de desenvolvimento da arquitetura - ADM (Architecture Development Method), bem como o Metamodelo de Conteúdos. Também são apresentados conceitos relacionados ao planejamento estratégico e formulação da estratégia, o Balanced Scorecard - BSC e o processo de Gestão Estratégica construído e utilizado na Câmara dos Deputados. Para se relacionar os elementos da Gestão Estratégica da Câmara dos Deputados com os elementos preconizados pelo modelo TOGAF 9.1, construiu-se uma tabela com a relação entre as entidades previstas no modelo TOGAF 9.1 e práticas da Gestão Estratégica da Câmara dos Deputados. Para avaliar o grau de contribuição da arquitetura corporativa para enfrentar questões ainda não resolvidas na gestão estratégica daquela instituição, elaborou-se um quadro contendo a relação entre as questões estratégicas e artefatos do modelo TOGAF 9.1 que endereçam essas questões. Para facilitar o entendimento das entidades do Metamodelo de Conteúdos, elaborou-se um glossário com os termos utilizados neste componente do TOGAF 9.1. Concluiu-se pela adequação da arquitetura corporativa ao processo de gestão estratégica da Câmara dos Deputados, de acordo com os critérios definidos previamente.

E-Learning as a shared service in shared services centers

Book Subtitle International Conference, CENTERIS 2010, Viana do Castelo, Portugal, October 20-22, 2010, Proceedings, Part II

Computational Systems

some resources on agile methods and enterprise architecture frameworks

Definition of an it project portfolio management methodology for a pharmaceutical company

Con la creciente popularidad de las soluciones de IT como factor clave para aumentar la competitividad y la creación de valor para las empresas, la necesidad de invertir en proyectos de IT se incrementa considerablemente. La limitación de los recursos como un obstáculo para invertir ha obligado a las empresas a buscar metodologías para seleccionar y priorizar proyectos, asegurándose de que las decisiones que se toman son aquellas que van alineadas con las estrategias corporativas para asegurar la creación de valor y la maximización de los beneficios. Esta tesis proporciona los fundamentos para la implementación del Portafolio de dirección de Proyectos de IT (IT PPM) como una metodología eficaz para la gestión de proyectos basados en IT, y una herramienta para proporcionar criterios claros para los directores ejecutivos para la toma de decisiones. El documento proporciona la información acerca de cómo implementar el IT PPM en siete pasos, el análisis de los procesos y las funciones necesarias para su ejecución exitosa. Además, proporciona diferentes métodos y criterios para la selección y priorización de proyectos. Después de la parte teórica donde se describe el IT PPM, la tesis aporta un análisis del estudio de caso de una empresa farmacéutica. La empresa ya cuenta con un departamento de gestión de proyectos, pero se encontró la necesidad de implementar el IT PPM debido a su amplia cobertura de procesos End-to-End en Proyectos de IT, y la manera de asegurar la maximización de los beneficios. Con la investigación teórica y el análisis del estudio de caso, la tesis concluye con una definición práctica de un modelo aproximado IT PPM como una recomendación para su implementación en el Departamento de Gestión de Proyectos.