A UML-driven enterprise architecture case study
ABSTRACT The U.S. Capitol Police (USCP) are responsible for protecting the Capitol Hill complex encompassing the Senate and House office buildings and the Capitol building. Currently, the USCP operate numerous legacy systems, many of which exist as stovepipes. They are modernizing their suite of administrative and law enforcement systems. The USCP recognized that developing an enterprise architecture was an essential first step to ensure that the proper solution was selected, that key integration points between the individual systems were understood, and that a prioritized set of initiatives to remediate, renovate, or replace information systems could be planned and executed. We describe how to use standard UML models to capture architectural view information and some specific extensions that address areas in which UML is limited.
SourceAvailable from: Darius Silingas[Show abstract] [Hide abstract]
ABSTRACT: The idea of the enterprise architecture (EA) has been active since 1980-ies. However, enterprises still lack a clear approach and tools for implementing it in practice. In most cases, enterprise models are fragmental and use domain-specific frameworks that do not have appropriate support in industrial tools. We introduce a novel approach to customizing UML tools for domain-specific modeling needs. This approach was implemented in MagicDraw UML and has already started to gain enthusiastic adoption in industry. The possibility to customize UML makes it more suitable as a platform for EA. While simplifying complex UML language and focusing on domain modeling concepts, it enables modelers to reuse the powerful features of UML tools – standard-based model data repository, diagramming features, model elements relationships analysis and navigation, model comparison and merge, documentation engine. The presented ideas are illustrated by custom EA model samples.
[Show abstract] [Hide abstract]
ABSTRACT: Enterprise Architecture (EA) is regarded as one of the means to ensure information technology interoperability, standard and reuse within an organizational boundary. In the public sector, however, there rises another kind of issues on how to integrate agency EA practices into the whole of government view. The conception of Government-wide EA (GEA) is the results of this consideration, and how to implement GEA has become a major challenge among IT policymakers form many countries. The present article deals with the applied case of modeling EA in the public sector. More specifically the article focuses on the methods and applications of modeling information integration architecture at government-wide level. A meta-modeling approach is used to design GEA database and to communicate with agencies regarding how they should manage agency-level EA information. The article consists of brief history of the EA program of the Korean Government, introduction of the KGEA Meta-model and its evolutionary history, and current status with some major outcomes. Methodological and managerial implications are also discussed.Advanced Communication Technology (ICACT), 2013 15th International Conference on; 01/2013
Conference Paper: An analysis of the adoption and Usage of Enterprise Architecture[Show abstract] [Hide abstract]
ABSTRACT: A changing market demand and technological evolution has required that enterprise systems constantly be updated and reengineered. Enterprise Architectures (EAs) emerged as 'tools' to assist organisations with managing enterprise systems. The potential benefits obtained by the adoption of an EA programme has resulted in a steady increase in the interest in EAs and in a study of EA activity worldwide, South Africa was ranked 10th. However, EA is a challenging concept and a number of heterogeneous architecture definitions, interpretations and classifications have been developed. It is imperative that an EA programme is considered not only as an issue for the Information Technology (IT) function, but also as a strategic and organisational challenge. Organisations embarking on an EA programme are faced with many complex decisions regarding which EA framework to select, which models and modelling notations to use, as well which technology strategies to adopt. Some organisations are embracing these programmes and are obtaining many benefits, others are faced with an abundance of challenges. This study investigates three popular EA frameworks and proposes an EA component classification map. Several medium to large South African organisations are investigated to validate and update elements of the classification map.2013 Enterprise Systems Conference (ES); 11/2013