Use of UML for modeling non-functional aspects (original) (raw)

2001

This paper introduces a proposal for representing non-functional aspects by using UML. Our purpose is to apply UML-concepts in combination with OCL in order to describe the non-functional aspects of software systems by resorting to the NoFun notation formulated by [7]. On one hand, we make use of the UML concepts for defining stereotypes, class compartments and stereotyped dependencies to represent the non-functionality. On the other hand, the OCL language is used for representing the constraints imposed on the implementations of software components .

Free PDF

UML Formalisation Literature Survey

2001

The Unified Modelling Language (UML) is considered a significant step in the development of Object-Oriented (OO) notations in that it is based on some of the best OO modelling experiences. However, the lack of firm semantics for the modelling notations used makes, among others, the identification of requirements problems difficult. One approach to making UML more precise and amenable to rigorous analysis is to integrate it with suitable formal notations. The following is a literature survey for most current works on ...

Free PDF

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.

Free PDF

Semantic Rules of UML Specification

— Modeling of a system is an essential process in software development lifecycle (SDLC). It will produce a system artifact called a system model. In object– oriented based software development, a system model can be developed by using Unified Modeling Language (UML). UML is a modeling language for specifying, constructing, and documenting the artifacts of systems. It consists of 13 diagrams that can be used to describe the different views of a system. Each diagram has its own syntax and semantics. The syntax or abstract syntax is the notations for each element of the diagrams, whereas the semantics is the meaning of the notations. The huge complexity of UML specification that content multi diagrams and notations, and lack of formal semantics decrease the quality of system models produced. It will lead to wrong interpretations and inconsistency between models. Therefore, a precise meaning of UML diagrams is very important in order to have a common understanding of their meaning. Formalization of the semantics of UML specification is important in order to provide the consistency of the system models. This paper provides an overview of the semantics rules of UML specification and suggests an approach to formalize these semantics rules.

Free PDF