Common Representation through UEML — Requirements and Approach

The Unified Enterprise Modelling Language (UEML) aims to become a hub for integrated use of enterprise and information systems (IS) models expressed using different languages. The paper explains how central constructs from UML's class and activity diagrams have been incorporated into UEML. As a result, the semantics of UML's central constructs for representing classes and activities have become more precisely defined in terms of the common UEML ontology. Through their ontology images, the two diagram types are also on the way to become interoperable with other enterprise and IS modelling languages in UEML.

Nowadays, one of the important subjects of research in the enterprise modelling domain is the development of a unified language, often called UEML (Unified Enterprise Modelling Language). This paper is focused on one of the more illustrating points about UEML: the comparison of the constructs of the enterprise modelleling language. In previous work we have put in evidence few situations which can occur when we want to compare some modelling con-structs belonging to different languages. We investigate more in detail this problem of comparison in using a formal approach based on the set theory.

Interoperability in enterprise modelling: requirements and roadmap

Summary form only given. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages

The main purpose of this paper is to present knowledge-based Enterprise model (EM) sufficiency as data repository for Unified Modelling Language (UML) models generation. UML models are one of the most usable modelling languages in system lifecycle design stage, despite the problem domain of the system. UML models can be generated from Enterprise Model by using particular transformation algorithms presented in previous researches. Generation process from Enterprise model is represented by certain Hospital Information Management process example. Generated UML dynamic Use Case, Activity, Sequence and State models of different perspectives of Hospital Information Management process prove sufficiency of stored information in Enterprise model.

The importance of improving understanding and communication between users and system developers in order to develop a structured description of the business, its information system needs and objectives through enterprise modelling approaches, has been increasingly recognized. Many enterprise modelling schemas are yielded to represent the different dimensions of the enterprise and different user views. These schemas must be integrated in order to produce a global, consistent view of the application domain. However, little attention has been paid to integration of enterprise modelling views, in particular, to the incorporation of integration issues in enterprise modelling methods. We propose a restricted enterprise model, the Objectives Focused Enterprise Modelling (OFEM) framework, which gives additional support both to the goal modelling orientation, and to integration considerations in enterprise modelling. We intend to investigate in depth goal similarity and conflict issues that occur in the process of enterprise modelling, and its schema integration.

To meet the demands of the enterprise models for the various application systems, an enterprise modelling method supporting model extension is proposed in this paper. In this method, first, the model is classified into three meta-model levels: core level, basic level and application level. The core-level meta-model describes some core conceptions of enterprise modelling. The basic-level meta-model extends the core level on the base of the some current modelling methods to meet the generic needs of the application system. The application-level model can build the elements and their attributes extensions to meet the needs of the different systems according to extension mechanism. The model of each level and the extension mechanism are discussed in detail. Furthermore, a method is given to guarantee the consistency of the extended model. Also the modelling process of this method is specified. This method is flexible and can meet the various modelling demands. An application example is provided to confirm the validity and feasibility of this method.

Summary form only given. Since its adoption in 1997, the unified modeling language (UML) has proved very popular with software engineers and has become the de facto standard as a visual modeling language for software engineers. However, this software focus of UML has discouraged many systems engineers from adopting it in earnest. Those who did adopt UML developed strategies to cope with its shortcomings. A common approach was to model additional systems engineering concepts in other modeling tools. This made it difficult to integrate the different viewpoints and achieve traceability. Fortunately, with the release of UML 2.0 and the ensuing extensions to it in SysML - the soon-to-be adopted systems modeling language - the systems engineering community has a real alternative to systems modeling that provides a more integrated approach to systems and software engineering. Since its inception in 1997, ARTiSAN has endeavored to bridge the gap between systems and software engineering modeling by adding systems engineering extensions to the UML and, as a key member of the SysML initiative, is well poised to support these emerging standards for systems and software modeling. This presentation will provide a brief overview of the major extensions proposed by SysML, and will summarize how ARTiSAN's latest release of its flagship product Studio (version 6.0) takes the lead in supporting these concepts.

We have developed an OWL ontology for the geologic timescale, derived from a Unified Modeling Language (UML) model that formalized the practice of the International Commission for Stratigraphy (ICS) (Cox and Richard 2005). The UML model followed the ISO/TC 211 modeling conventions, and was the basis for an XML implementation that was integrated into GeoSciML 3.0. The OWL ontology is derived using rules for generating OWL ontologies from ISO-conformant UML models, as provided in a (draft) standard from ISO/TC 211. The basic ontology is also aligned with SKOS to allow multilingual labels, and to enable delivery through a standard vocabulary interface. All versions of the International Stratigraphic Chart from 2004 to 2014 have been encoded using the ontology. Following ICS practice, the elements of the timescale retain the same identifiers across the multiple versions, though the information describing each geochronologic unit evolves with the versions of the timescale. The timescales are published through multiple web interfaces and APIs.

FORM 아키텍처 모델은 소프트웨어 프로덕트 라인 내의 제품 개발에 재사용될 수 있는 아키텍처로서 FORM 방법론의 핵심적인 역할을 한다. 하지만 기존의 FORM 아키텍처 모델을 실무에 적용할 때 다음과 같은 문제점들이 있다. 첫째, UML(Unified Modeling Language)과 같이 표준화된 모델이 아니므로, 이 모델을 작성하기 위해서는 고유한 모델링 도구가 필요하다. 둘째, FORM 아키텍처 모델은 휘처모델과의 대응 관계를 통해 가변성을 관리만 할 뿐, 아키텍처의 가변성을 명시적으로 나타내지 않았다. 본 논문에서는 이러한 FORM아키텍처 모델의 문제점을 해결하기 위해서, 먼저 FORM 아키텍처 모델을 UML 모델로 표현할 수 있는 방법을 개발하였다. 이는 FORM 아키텍처 모델링에 다양한 UML모델링 도구를 이용할 수 있는 장점이 있다. 또한, 휘처모델과의 대응관계를 통해서 FORM 아키텍처 모델의 가변성을 효과적으로 관리할 뿐만 아니라 표현 할 수 있는 방법을 개발하였다. FORM(Feature-Oriented Reuse Method) is one of representative product line engineering methods. The essence of FORM is the FORM architecture models, which can be reused in the development of multiple products of a software product line. The FORM architecture models, however, have the following problems when applied in practice. First, they are not standardized models like UML(Unified Modeling Language) and therefore they can be constructed only through a specific modeling tool. Second, they do not represent architectural variability explicitly. Instead their variability is only managed through a mapping from a feature model. To address these two problems, we developed at first a method for representing the FORM architecture models using UML, which enables the FORM architecture models to be constructed through various available UML modeling tools. Also, we developed an effective method for representing as well as managing the variability of the FORM architecture models through a mapping from a feature model.

To remain competitive in dynamic environment, enterprises need to make effective and efficient decisions in response to changes. Good modeling tools and analysis support is a necessity in this regard. Such modeling and analysis tools should to be able to visually model and programmatically analyze several descriptive and prescriptive modeling languages in concert. We recount our experience with visual modeling editor and ontological representation for both descriptive and prescriptive models for enterprise decision making. Starting with purposive modeling tools, we shifted to integrated modeling environment where all relevant models of enterprise coexist and are analyzed together. Our ongoing research suggests that apart from integrated modeling environment, scalable modeling facilities for better interaction between modelers and domain experts are also necessary to make modeling and analysis of enterprise models more streamlined.

The unified modeling language (UML) is one of the most commonly used modeling languages in the software industry. It simplifies the complex process of design by providing a set of graphical notations, which helps express the objectoriented analysis and design of software projects. Although UML is applicable to different types of systems, domains, methods, and processes, it cannot express certain problem domain needs. Therefore, many extensions to UML have been proposed. In this paper, we propose a framework for integrating the UML extensions and then use the framework to propose an integrated unified modeling language-graphical (iUML-g) form. iUML-g integrates the existing UML extensions into one integrated form. This includes an integrated diagram for UML class, sequence, and use case diagrams. The proposed approach is evaluated using a case study. The proposed iUML-g is capable of modeling systems that use different domains.

Knowledge systems are increasingly used to support globally distributed work. Projects are a natural means of designing and deploying such systems. There is plenty of literature on the management of information systems design projects and some literature on information systems deployment projects. However, knowledge systems are typically more complex organizationally and socially than most traditional information systems. For example, enterprise resource planning systems typically must be used to get the work done whereas many knowledge systems are voluntary to use. It is reasonable to assume that project management involved in the design and deployment of knowledge systems differs from the project management involved in traditional information systems projects. Examples abound in the literature about knowledge systems deployment efforts that failed because (1) the business cultures did not encourage and reinforce knowledge sharing and (2) the necessary organizational change could not be implemented. Such failures could often have been avoided if (1) more balanced efforts between the design and deployment of knowledge systems had been implemented and (2) the design and deployment efforts had been managed through coordinated design and deployment projects. Deployment projects have a crucial role in implementing organizational and social changes. Yet, deployment is often considered only as a phase in larger design-driven projects. This minitrack calls for research contributions in domains where large economic, organizational, and social benefits can be obtained from the effective management of knowledge systems design and deployment projects. Contributions should span the dualism between knowledge system design and deployment research and/or the dualism between the design project and deployment project research, helping individuals and organizations design and use work systems and enabling knowledge systems holistically. For example, when the routines of people using knowledge systems unexpectedly break down, people typically devise workarounds, potentially changing their work practices or using the knowledge systems in unintended ways. Sooner or later, workarounds become ineffective and new holistic work system and knowledge system redesign projects are needed to devise lasting solutions. Theory-based normative advice is needed to answer questions such as why, when, and how to devise new holistic work system and knowledge system designs (1) to deal with the encountered breakdowns and (2) to leverage and appropriately institutionalize the knowledge embedded in the improvised workarounds. In 2012, this minitrack consists of two papers. The paper of Laddawan Kaewkitipong investigates the reasons for and the lessons to be learnt from the failure of Google Wave, a shared space on the web where people can collaborate using multiple media and artifacts. Kaewkitipong conducted content analysis of secondary data from several online forums, which discussed the failure of Google Wave, and primary data collected from interviews with early adopters who had discontinued using Google Wave. Complexity and a lack of relative advantage were found the most frequently cited reasons for failure. The exclusivity of Google Wave through the invite-only policy was also cited as a reason for failure. Designers and vendors of web-based knowledge systems thus need to be able to (1) balance between delivering all-in-one systems and keeping the systems easy to understand and use and (2) understand the dynamics of decision making within social networks in which single actors can seldom decide which systems the networks should adopt. According to Koivulahti-Ojala and Kakola enduser training is complicated to implement in global software development organizations where development work is distributed across multiple sites that may leverage a development tool for very different purposes. Web-based Virtual Meeting Tools (VMT) enable synchronous communication and provide potentially a cost effective way to train even complex topics to large numbers of people in global settings. Few industrial experiences from the design and use of VMT-based training innovations have been reported. The paper draws upon a case study in a global corporation to describe the design, implementation, and evaluation of a VMT-based training innovation for delivering a set of courses to support the global deployment of a Unified Modeling Language (UML) modeling tool and to develop UML modeling skills. The innovation proved successful in improving skills, knowledge, and motivation and learners were satisfied with it. Other organizations may benefit from using VMT to train people to use similar complex information systems. 2012 45th Hawaii International Conference on System Sciences

Increasing numbers of software developers are using the Unified Modeling Language (UML) and associated visual modeling tools as a basis for the design and implementation of their distributed, component-based applications. At the same time, it is necessary to test these components, especially during unit and integration testing. At Siemens Corporate Research, we have addressed the issue of testing components by integrating test generation and test execution technology with commercial UML modeling tools such as Rational Rose; the goal being a design-based testing environment. In order to generate test cases automatically, developers first define the dynamic behavior of their components via UML Statecharts, specify the interactions amongst them and finally annotate them with test requirements. Test cases are then derived from these annotated Statecharts using our test generation engine and executed with the help of our test execution tool. The latter tool was developed specifically for interfacing to components based on COM/DCOM and CORBA middleware. In this paper, we present our approach to modeling components and their interactions, describe how test cases are derived from these component models and then executed to verify their conformant behavior. We outline the implementation strategy of our TnT environment and use it to evaluate our approach by means of a simple example.

Unified Modeling Language (UML) has emerged as the software industry’s dominant modeling language. It is the de facto modeling language standard for specifying, visualizing, constructing, and documenting the components of software systems. Despite its prominence and status as the standard modeling language, UML has its critics. Opponents argue that it is complex and difficult to learn. Some question the rationale of having nine diagramming techniques in UML and the raison d’être of those nine techniques in UML. Others point out that UML lacks a comprehensive methodology to guide its users, which makes the language even more convoluted. A few studies on UML can be found in the literature. However, no study exists to provide a quantitative measure of UML complexity or to compare UML with other object-oriented techniques. In this research, we evaluate the complexity of UML using complexity metrics. The objective is to provide a reliable and accurate quantitative measure of UML complexity. A comparison of the complexity metrical values of UML with other object-oriented techniques was also carried out. Our findings suggest that each diagram in UML is not distinctly more complex than techniques in other modeling methods. But as a whole, UML is very complex–2-11 times more complex than other modeling methods.