Modeling Information Systems in UML (original) (raw)
Related papers
Role of UML Class Diagram in Object-Oriented Software Development
Scientific Journal of Riga Technical University. Computer Sciences, 2011
Role of UML Class Diagram in Object-Oriented Software DevelopmentUML is an industrial standard for object-oriented software specification which offers a notation for class modeling during object oriented software development. Since the UML class diagram is a so-called "bridge" between software specification at the user side and software realization at the developer side, it requires strong guidelines for identification of class objects from the problem domain and notational conventions for modeling of the class diagram for its further usage in system coding. This paper presents a discussion on problematic stages and possible element transformations into software components. Several conclusions are drawn on potential usage of the class diagram in industry.
Connection between UML use case diagrams and UML class diagrams: a matrix proposal
International Journal of Computer Applications in Technology, 2023
In recent years, the UML language has been one of the most used to conduct information system analysis and design. Being an object-oriented technique, UML provides a vast set of diagrams, in order to represent the various abstractions of the system, of which the most used are the use-case diagram and the class diagram. Often, in the modelling of less complex systems, only these two diagrams are used, where one represents the functionalities of the system (use case diagram) and the other the static structure of the system (class diagram). However, it is often difficult to make the connection between the two diagrams, and mainly, it is difficult to verify when one matches the other. In order to solve this problem, a matrix is proposed that links the two diagrams, using a case study to verify the utility of the matrix.
A Tool for Generation of the UML Class Diagrams
2012
Object-oriented system modeling enables the sharing of responsibilities between system objects at a high level of system abstraction. The UML class diagram is the central part of the object-oriented system model and serves as a "bridge" between the information about the problem domain at the customer's side and the software components at the developer's side. However, UML is not a methodology for how to model the system, but just a notation for "drawing" of model elements. This paper demonstrates the functionality of the BrainTool, which enables the generation of the UML class diagram from the so called two-hemisphere model, where the problem domain is presented as a concatenation of the problem domain processes, incoming and outgoing information flows and their types. BrainTool is developed using Visual Studio .NET for modeling of the two-hemisphere model, the Python programming language for definition of transformation rules and XMI for model interchange with Sparx Enterprise Architect.
The assessment of object oriented modelling elements of the UML 1.1
1998
The UML 1.1. as released in September 1997 represents an improved version of the previous document by giving revised definitions of many modelling elements and including well-formedness rules, defining its four layered architecture and organisation by package, and including an Object Constraint Language Specification used within well-formedness rules. In this paper we analyse and critically assess some modelling solutions with observations regarding types, interfaces and classifiers, and problems of associations semantics and notation. Well formedness rules, their format and role are also analysed. Use case modelling is assessed through their role in eliciting user's requirements, and dealing with the functionality of the system. Some examples show the potential danger of using use-cases as a replacement for functional decomposition. This could result in some important abstractions in the system not being revealed and not seeing use cases as a representation of collective functionality where their components act as collaborations between objects.
Diagramming the Class Diagram: Toward a Unified Modeling Methodology
The object-oriented class is, in general, the most utilized element in programming and modeling. It is employed throughout the software development process, from early domain analysis phases to later maintenance phases. A class diagram typically uses elements of graph theory, e.g., boxes, ovals, lines. Many researchers have examined the class diagram layout from different perspectives, including visibility, juxtaposability, and aesthetics. While software systems can be incredibly complex, class diagrams represent a very broad picture of the system as a whole. The key to understanding of such complexity is use of tools such as diagrams at various levels of representation. This paper develops a more elaborate diagrammatic description of the class diagram that includes flows of attributes, thus providing a basic representation for specifying behavior and control instead of merely listing methods.
Communications in Computer and Information Science, 2015
UML offers a very large set of constructs for each of its diagram types, however many of them seem scarcely used or even their existence is not known. Here, we decided to present a precise view of the usage levels of the constructs of activity and use case diagrams by means of a document and tool analysis study, covering preliminarily: books, courses, tutorials, and tools about UML. Results of the study show that, among the 47 activity diagrams constructs, a large majority of them seem to be scarcely used, while, only nine result widely used, whereas only two of the nine constructs of the use case diagrams seem scarcely used. This work is part of a larger project aimed at investigating the usage level of the UML diagrams and their constructs, also by means of a personal opinion survey intended for UML users.