ONTOLOGICAL FRAMEWORK FOR OBJECT-ORIENTED ANALYSIS AND DESIGN

The 1990s saw an insurgence in the use of object‐oriented (OO) technologies. Along with this shift has been an increase in the demand for metrics to aid in evaluating the processes and the products associated with these new technologies. OO measurement focuses primarily on those metrics that have been specifically developed to be used with OO technologies and products. Many traditional metrics are paradigm neutral and, therefore, can still be used in the OO paradigm to answer certain kinds of questions. As a trivial example, lines of code is as valid a size metric in the OO paradigm on which to base an estimate of the amount of paper needed to print out a software package as it is in the procedural paradigm. New language constructs, however, imply significant differences in OO program structure. Thus, metrics specifically developed for OO technologies are often required. In particular, measurements associated with classes and class structure take on significant importance in OO products. For example, measurements of reuse via class inheritance are not found in traditional procedural paradigm metric sets. Besides the change in language constructs, the OO development process frequently differs from traditional processes in several ways. Much greater emphasis is often placed on more formal documentation during the early phases of development, such as the use of UML (Unified Modeling Language); and a clearer, more direct component to component relationship can be seen across the artifacts of the system through requirements, design, coding, and testing. This increase in visibility at the earlier phases of development has resulted in a greater desire for and emphasis on metrics for measuring the products of the early phases, particularly OO requirements and design.

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.

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.

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.

From a software engineering perspective, agent systems are a specialization of object-oriented (OO) systems, in which individual objects have their own threads of control and their own goals or sense of purpose. Engineering such systems is most naturally approached as an extension of object-oriented systems engineering. In particular, the Unified Modeling Language (UML) can be naturally extended to support the distinctive requirements of multi-agent systems. One such requirement results from the increasing emphasis on the correspondence between multi-agent systems and social systems. Sociological analogies are proving fruitful models for agent-oriented constructions, while sociologists increasingly use agents as a modeling tool for studying social systems. We combine several existing organizational models for agents, including AALAADIN, dependency theory, interaction protocols, and holonics, in a general theoretical framework, and show how UML can be applied and extended to capture constructions in that framework.

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.

Although the Unified Modeling Language (UML) is by now accepted as a standard and is widely used as an object-oriented modeling language, some languages such as Z or VDM are preferred to formally specify reference models. Here, we present a reference model for hypermedia systems in UML. It is an object-oriented and Dexter-based approach that uses UML to provide an intuitive graphical representation of the model. The class diagrams are supplemented with formal constraints in the Object Constraint Language (OCL), adding invariants on elements as well as preconditions and postconditions on operations. The result is an easily extendable reference model for describing specific hypermedia systems, for example, like adaptive or mobile systems. Our contribution shows how formal and semiformal object-oriented techniques can be integrated in the metamodeling process.

The unified modeling language (UML) designs come in a variety of different notations. UML designs can be quite large and interactions between various notations and the models they define can be difficult to assess. During the design phase, and between successive releases of systems, designs change. The impact of such changes and the resulting effect on behavior can be non-obvious and difficult to assess. This survey article explores techniques for such re-evaluation that can be classified as regression testing and suggests regression testing criteria for designs. These might vary depending on testing objectives and include both selective and regenerative regression testing approaches. The article provides a concise overview of regression testing approaches related to various UML design notations including use cases, class diagrams, sequence diagrams, activity diagrams, and statecharts, as well as combinations of these models. It discusses UML-related techniques involving cost and prioritization during selective regression testing. Finally, it evaluates these techniques with respect to inclusiveness, precision, efficiency, generality, accountability, and safety. An example is used throughout to illustrate how the techniques work. Copyright © 2009 John Wiley & Sons, Ltd. This survey article explores techniques for regression testing with UML designs and suggests regression testing criteria for designs. These might vary depending on testing objectives and include both selective and regenerative regression testing approaches. The article provides a concise overview of regression testing approaches related to various UML design notations including use cases, class diagrams, sequence diagrams, activity diagrams, and statecharts, as well as combinations of these models. Copyright © 2009 John Wiley & Sons, Ltd.

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.

Unified modelling language (UML) 2.0 introduced in 2002 has been developing and influencing object-oriented software engineering and has become a standard and reference for information system analysis and design modelling. There are many concepts and theories to model the information system or software application with UML 2.0, which can make ambiguities and inconsistencies for a novice to learn to how to model the system with UML especially with UML 2.0. This article will discuss how to model the simple software application by using some of the diagrams of UML 2.0 and not by using the whole diagrams as suggested by agile methodology. Agile methodology is considered as convenient for novices because it can deliver the information technology environment to the end-user quickly and adaptively with minimal documentation. It also has the ability to deliver best performance software application according to the customer's needs. Agile methodology will make simple model with simple documentation, simple team and simple tools.

The Unified Modeling Language (UML) has been widely accepted as the standard object-oriented (OO) modeling language for modeling various aspects of software and information systems. The UML is an extensible language, in the sense that it provides mechanisms to introduce new elements for specific domains if necessary, such as web applications, database applications, business modeling, software development processes, data warehouses and so on. Furthermore, the latest work of the Object Management Group (OMG) on UML [1] resulted in a larger and more complicated specification, with even more diagrams for some good reasons. Although providing different diagrams for modeling specific parts of a software system, not all of them need to be applied in most cases. Therefore, heuristics, design guidelines, and lessons learned from experiences are extremely important for the effective use of UML and to avoid unnecessary complication.

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.

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.