ContextUML: A UML-Based Modeling Language for Model-Driven Development of Context-Aware Web Services Development

PurposeIn the last decade, web services have become a major technology to implement loosely coupled business processes and perform application integration. Through the use of context, a new generation of web services, namely context‐aware web services (CASs), is currently emerging as an important technology for building innovative context‐aware applications. Unfortunately, CASs are still difficult to build. Issues like lack of context provisioning management approach and lack of generic approach for formalizing the development process need to be solved in the first place for easy and effective development of CASs. The purpose of this paper is to investigate the techniques on developing CASs.Design/methodology/approachThe paper focuses on introducing a model‐driven platform, called ContextServ, and showcasing how to use this platform to rapidly develop a context‐aware web application, Smart Adelaide Guide. ContextServ adopts a model‐driven development (MDD) approach where a Unified Modeling Language (UML)‐based modeling language – ContextUML – is used to model web services and its context‐awareness features.FindingsThe paper presents novel techniques for efficient and effective development of CASs using a MDD approach. The ContextServ platform is the only one that provides a comprehensive software toolset that supports graphical modeling and automatic model transformation of CASs.Practical implicationsThe proposed approach has been validated in practice by developing various CASs. The experimental study demonstrates the efficiency and effectiveness of the approach.Originality/valueThe paper presents a novel platform called ContextServ, which offers a set of visual editing and automation tools for easy and fast generating and deploying CASs.

Web service technologies are becoming increasingly important for integrating systems and services. There is much activity and interest around standardization and usage of Web service technologies. Contemporary Web services are described in the Web Service Description Language (WSDL). However, WSDL documents can be difficult to understand for service developers. This article recommends a model-driven process for Web service development combining the graphical modeling language UML with WSDL. The Unified Modeling Language (UML) is developed by Object Management Group. In the proposed process, Web service descriptions (in WDSL) are converted to UML; their UML models are integrated to form composite Web services; and then the new Web service descriptions are exported. The main contribution of this article is a “pure UML” modeling strategy supported by implementation of two-way conversion rules between the UML models and the WSDL documents.

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.

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.

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 Web Services Choreography Description Language (WS-CDL) is a specification developed by the W3C and can be viewed as a blueprint for the development of end-point services. Consequently, it is worth providing a systematic approach for its modeling, analysis and verification. The Unified Modeling Language (UML) is an industry standard for modeling. Applying UML to model WS-CDL is obviously a promising solution to bring together academics and practitioners through a unique standard language. In this paper, we propose to use different UML diagrams to model WS-CDL. UML Component Diagram is used to model the underlying structure of WS-CDL. UML Sequence Diagram is utilized to model the activities in WS-CDL. UML State Machine Diagram is utilized to model the behaviors of each role participating in a WS-CDL specification. We then enrich the UML State Machine Diagram with data by the use of UML Class Diagram. Given the UML specification of WS-CDL, we then provide a systematic way of formally analyzing and verifying WS-CDL against desired properties. Some experiments show that our approach can verify structural, behavioral and data properties in a middle-scale data-enriched WS-CDL specification.

Software product line (SPL) is a software engineering paradigm for software development. A software product within a product line often has specific functionalities that are not common to all other products within the product line. Those specific functionalities are termed “variant features” in a product line. SPL paradigm involves the modeling of variant features. However, little work in SPL investigates and addresses the modeling of variant features specific to user interface (UI). Unified Modeling Language (UML) is the de facto modeling language for object-oriented software systems. It is known that UML needs better support in modeling UIs. Thus, much research developed UML extensions to improve UML support in modeling UIs. Yet little of this work is related to developing such extensions for modeling UIs for SPLs in which variant features specific to UI modeling must be addressed. This research develops a UML extension -Web User Interface Modeling Language (WUIML) to address these problems. WUIML defines elements for modeling variant features specific to user interfaces for Web-based SPLs. The model elements in WUIML extend from the metaclass and BasicActivity of the UML2.0 metamodel. WUIML integrates the modeling of variant features specific to user interfaces to UML. For example, in a Web-based patient registration software product line, member products targeting British users may use British date format in the user interface, while member products targeting United States users may use United States date format in the user interface. Thus, this is a variant feature for this product line. WUIML defines a model element, XOR, to represent such exclusive or conditions in a product line user interface model. WUIML would reduce SPL engineers’ efforts needed in UI development. To validate the WUIML research outcome, a case study was conducted. The results of this empirical study indicate that modeling UIs for Web-based SPLs using WUIML is more effective and efficient than using standard UML.

In this chapter, we provide the essential theory and practical details of employing the principles of Object Orientation (OO) in system architecture modeling. We do not attempt to provide an exhaustive OO tutorial, since there exists a very large literature on this subject (see the references to this chapter). Our goal, instead, is to give the reader the level of understanding needed to master the MBSAP methodology and apply it to practical system architecting challenges. First, we present the rationale for OO and define the essential concepts and terminology, stressing the benefits it delivers in dealing with complex entities. Although we use the Systems Modeling Language (SysML) as the basis for this book, we begin by discussing and illustrating the primary diagrams of the Unified Modeling Language (UML), which is the root language standard for OO. This is then followed by a description of the changes to UML introduced by the SysML, which is defined as a Profile of UML. The reality is that a large part of the SysML is taken directly from the UML language specification. We believe understanding of this material is enhanced by first considering the parent UML and then explicitly showing how UML modifies and extends the language. We include generic UML and SysML diagrams that illustrate important principles and syntax and that can serve as format samples in developing real architecture models. Appendices A and B are concise references to UML and SysML, respectively, intended to give readers a quick and easy way to look up the details. Chapter objective: the reader will be able to create and read UML and SysML diagrams and to describe the role of each.

As a powerful and object-oriented graphical modeling language, Unified Modeling Language (UML) has been introduced into the design and development of safety-critical computer systems. However, UML model is difficult to reflect the concurrency and consistency of constraint rules between objects and impossible to completely demonstrate the dynamic behavior characteristics of a system. Further, it cannot be directly expressed and analyzed by mathematical tools. Petri net modeling technology uses graphical element place and transition to clearly describe the internal interactions of a system. Meanwhile, Petri net has mature mathematical analysis methods. We have proposed to combine these two tools for designing and analyzing a system with a set of transformation rules from UML statecharts to Petri net. In this paper, an automatic conversion tool is introduced. The tool performs the transformation with three steps as follows: (1) Transforming UML model into XML document, which makes information extraction of the UML model become easier. (2) Analyzing semantics of UML model and Petri net model, then designing data structure for transformation, and completing the transformation based on the transformation rules. (3) Analyzing the transformed Petri net model to verify the characteristics of the UML model. The transformation rules and the tools are developed based on a new railway interlocking system.

To most in the software community, "modeling" is drawing pictures, something much different than "coding". While programming languages must be specified precisely enough to be executable, this has not necessarily been the case for modeling languages. Indeed, the well-known Unified Modeling Language (UML) has for years had a specification that is far from precise. However, precise models are quite common in other engineering disciplines, and there has been a minority even in software engineering that have created models that are precise enough to be, themselves, executable. Over the last decade, the UML community has more generally come to realize the benefits of having at least a subset of UML specified with precise execution semantics. While not all models need to be executable, executable models can support early testing and analysis of the design of critical software systems, as well as supporting simulation for communities using UML for modeling beyond just software (such as SysML for systems engineering). As a result, there has been a great deal of work in recent years toward the standardization of precise, executable semantics for UML models - the "meaning" behind the pictures: Foundational UML (fUML), the Action Language for fUML (Alf) and the recently completed Precise Semantics for UML Composite Structures. These new specifications provide the promise of widespread support for executable modeling across the many UML tools now on the market.

Efficient and high-quality design of the substation automation systems has always been a real challenge. The problem of identification and location of information in the system and the description of information processing activities is a significant design problem. Information modeling is aimed at resolving it. An efficient approach to information modeling can significantly improve substation automation system development process. In this paper we propose the usage of the Unified Modeling Language (UML) as a main modeling language for expressing substation information models. UML was specified by Rational Software Corporation in 1997. Today, UML is adopted by the Object Management Group as an object-oriented modeling language with formally defined syntax and semantics. As expected, UML could be widely accepted in various industries (software, telecommunications, medicine, electro-industry, aero-industry etc.). The modeling approach is explained on one typical small-range 35 kV/10 kV distribution substation. Modeling steps: system usage specification, system structure specification, and behavior and constraints specification are described together with explanation of usage of some UML diagrams and modeling concepts.

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.

Web services facilitate agile development and deployment of new services in e-Government systems. Due to their distributed nature, Web services as well as e-Government systems must be secured against various cyber attacks and ensured that only authorized users can have access to valuable and sometimes sensitive information and resources. However, correct and efficient security engineering for Web service-based e-Government systems is not a trivial task. Model-driven security (MDS) is considered to be a promising approach to reduce complexity and increase efficiency in the design and development of secure Web services for e-Government systems. Nevertheless, the practicability of MDS has yet not been fully assessed. In a recent pilot project, we have applied MDS to the design and development of Web services for the actual e-Government system in Austria. Our work shows that despite extensive research work, several aspects of MDS need to be adapted and further developed such that one can really benefit from such an approach in practice. Our work on addressing these aspects provides realistic assessment and valuable insights on the application of MDS to Web services in the real world.

In this chapter, we introduce you to the concepts of the Unified Modeling Language (UML). Our intention with this chapter is to give you a clear understanding of what UML really is, its historical background, and how it’s used. UML is a modeling language, meaning that it’s a language or concept for how to model and describe real-world objects and how they interact. The difference between UML and a normal programming language is that UML is a graphical language that uses graphics to describe objects. UML is also used to describe design patterns,1 which you can apply to your .NET environment.

The emergence of Unified Modeling Language (UML) as a standard for modeling systems has encouraged the use of automated software tools that facilitate the development process from analysis through coding. The UML state machine diagram is used for modeling the dynamic aspects of systems and includes many concepts that are not present in most popular programming languages, like Java or C++. There exists a gap between high level modeling language and a programming language. This paper proposes an approach to narrow the gap between multiple UML models and an implemented system. The narrowing of gap is achieved by generating compact and efficient Java code directly from UML state machine having sequential and concurrent substates. The code generation is achieved by creating a mapping between UML behavior and the Java programming language. Our model can work as a basis for automatic code generation for object-oriented systems.