Modeling the object-oriented software process: OPEN and the unified process

A short introduction to software process modeling is presented, particularly object-oriented modeling. Two major industrial process models are discussed: the OPEN model and the Unified Process model. In more detail, the quality assurance in the Unified Process tool (formally called Objectory) is reviewed

UML Class Diagram or Entity Relationship Diagram : An Object Relational Impedance Mismatch

It is now nearly 30 years since Peter Chen’s watershed paper “The Entity-Relationship Model –towards a Unified View of Data”. [1] The entity relationship model and variations and extensions to ithave been taught in colleges and universities for many years. In his original paper Peter Chen looked at converting his new ER model to the then existing data structure diagrams for the Network model. In recent years there has been a tendency to use a Unified Modelling Language (UML) class diagram forconceptual modeling for relational databases, and several popular course text books use UMLnotation to some degree [2] [3]. However Object and Relational technology are based on different paradigms. In the paper we argue that the UML class diagram is more of a logical model (implementation specific). ER Diagrams on theother hand, are at a conceptual level of database design dealing with the main items and their relationships and not with implementation specific detail. UML focuses on OOAD (Object Oriented Analysis and Design) and is navigational and program dependent whereas the relational model is set based and exhibits data independence. The ER model provides a well-established set of mapping rules for mapping to a relational model. In this paper we look specifically at the areas which can cause problems for the novice databasedesigner due to this conceptual mismatch of two different paradigms. Firstly, transferring the mapping of a weak entity from an Entity Relationship model to UML and secondly the representation of structural constraints between objects. We look at the mixture of notations which students mistakenly use when modeling. This is often the result of different notations being used on different courses throughout their degree. Several of the popular text books at the moment use either a variation of ER,UML, or both for teaching database modeling. At the moment if a student picks up a text book they could be faced with either; one of the many ER variations, UML, UML and a variation of ER both covered separately, or UML and ER merged together. We regard this problem as a conceptual impedance mismatch. This problem is documented in [21] who have produced a catalogue of impedance mismatch problems between object-relational and relational paradigms. We regard the problems of using UML class diagrams for relational database design as a conceptual impedance mismatch as the Entity Relationship model does not have the structures in the model to deal with Object Oriented concepts Keywords: EERD, UML Class Diagram, Relational Database Design, Structural Constraints, relational and object database impedance mismatch. The ER model was originally put forward by Chen [1] and subsequently extensions have been added to add further semantics to the original model; mainly the concepts of specialisation, generalisation and aggregation. In this paper we refer to an Entity-Relationship model (ER) as the basic model and an extended or enhanced entity-relationship model (EER) as a model which includes the extra concepts. The ER and EER models are also often used to aid communication between the designer and the user at the requirements analysis stage. In this paper when we use the term “conceptual model” we mean a model that is not implementation specific.ISBN: 978-84-616-3847-5 3594Peer reviewe

Rosen's (M,R) system in Unified Modelling Language

Robert Rosen's (M,R) system is an abstract biological network architecture that is allegedly non-computable on a Turing machine. If (M,R) is truly non-computable, there are serious implications for the modelling of large biological networks in computer software. A body of work has now accumulated addressing Rosen's claim concerning (M,R) by attempting to instantiate it in various software systems. However, a conclusive refutation has remained elusive, principally since none of the attempts to date have unambiguously avoided the critique that they have altered the properties of (M,R) in the coding process, producing merely approximate simulations of (M,R) rather than true computational models. In this paper, we use the Unified Modelling Language (UML), a diagrammatic notation standard, to express (M,R) as a system of objects having attributes, functions and relations. We believe that this instantiates (M,R) in such a way than none of the original properties of the system are corrupted in the process. Crucially, we demonstrate that (M,R) as classically represented in the relational biology literature is implicitly a UML communication diagram. Furthermore, since UML is formally compatible with object-oriented computing languages, instantiation of (M,R) in UML strongly implies its computability in object-oriented coding languages

A Microsimulation Approach to the Modelling of Urban Population and Housing Markets Within an Object-Oriented Framework

The structure of a city constantly changes, in accordance to the population’s housing demand and the city’s housing supply. Housing demand depends on several factors, such as changes in household structure caused by demographic events (e.g. mortality, fer

Software similarity measurements using UML diagrams: A systematic literature review

Every piece of software uses a model to derive its operational, auxiliary, and functional procedures. Unified Modeling Language (UML) is a standard displaying language for determining, recording, and building a software product. Several algorithms have been used by researchers to measure similarities between UML artifacts. However, there no literature studies have considered measurements of UML diagram similarities. This paper presents the results of a systematic literature review concerning similarity measurements between the UML diagrams of different software products. The study reviews and identifies similarity measurements of UML artifacts, with class diagram, sequence diagram, statechart diagram, and use case diagram being UML diagrams that are widely used as research objects for measuring similarity. Measuring similarity enables resolution of the problem domains of software reuse, similarity measurement, and clone detection. The instruments used to measure similarity are semantic and structural similarity. The findings indicate opportunities for future research regarding calculating other UML diagrams, compiling calculation information for each diagram, adapting semantic and structural similarity calculation methods, determining the best weight for each item in the diagram, testing novel proposed methods, and building or finding good datasets for use as testing material

Inside an Agent

When we discuss agent-based system construction with software developers or ask students to implement common agent architectures using object-oriented techniques, we find that it is not trivial for them to create an elegant system design from the standard presentation of these architectures in textbooks or research papers. To better communicate our interpretation of popular agent architectures, we draw UML (Unified Modeling Language) diagrams to guide an implementer\u27s design. However, before we describe these diagrams, we need to review some basic features of agents. The paper considers an architecture showing a simple agent interacting with an environment. The agent senses its environment, uses what it senses to choose an action, and then performs the action through its effectors. Sensory input can include received messages, and action can be the sending of messages. To construct an agent, we need a more detailed understanding of how it functions. In particular, if we are to build one using conventional object-oriented analysis and design techniques, we should know in what ways an agent is more than just a simple objec

A connecting system for cardiological lexicons

The purpose of this paper is to present the approach and the development of a software application ("lexicons connecting" system) to correlate effectively and unambiguously the correspondence between the specialist medical vocabulary and the familiar medical vocabulary for the cardiovascular domain. To investigate the question, the idea, the design, and the implementation of such system will be described. To this end, firstly, a number of research methodologies will be examined including domain ontologies development, database design and implementation. Then, the following implementation methodology and its results are presented. Finally, an example of the application use will be depicted and future work will be briefly described

Model dan Simulasi Perbandingan Prototype Rangkaian Digital Half Adder Alu Standar dengan Inovasi Rangkaian Digital Half Adder Alu

- This research was conducted to model and simulate the Half Adder system. This system is designed by analyzing the descriptive method, and the comparative method. After analysis, modeling is done with UML (Unified Modeling Language) and hardware design based on microcontroller can be programmed using CodeVisionAVR-C software. The results of this study are a standard prototype Half ALU ALTER Adder system that uses XOR, AND, OR gates with ALU Half Adder system innovation using NAND and NOR gates.Keywords - Half Adder, Prototype, XOR, AND, OR, NAND, NO

Modeling of Distributed Ledger Deployment View

The Distributed Ledger Technology (DLT) is a peer-to-peer model of sharing data among collaborating parties in a decentralized manner. An example of DLT is a blockchain where data form blocks in an append-only chain. Software architecture description usually comprises multiple views. The paper concentrates on the Deployment view of the DLT solution within the 1+5 architectural views model. The authors have proposed Unified Modeling Language (UML) extensibility mechanisms to describe the needed additional semantic notation to model deployment details. The paper covers both the network and node levels. The proposed stereotypes and tagged values have enriched the UML Deployment diagram. We have gathered those modeling elements in dedicated UML Profile for Distributed Ledger Deployment. We have applied the profile to model the Deployment view of a renewable energy management system that uses the R3Cordaframework. The system records information about inbound and outbound energy to/from a renewable energy grid