Importance and Impact of Class Diagram in Software Development

Revista Brasileira de Computação Aplicada, 2019

Background. Modeling architectural aspects of the system is an essential activity in software development. Inthis context, developers work in parallel, and collaborate to define application software models, such as classdiagrams. Problem. Although many software modeling tools have been proposed, there is a lack of distributed collaboration features. Solution. This study proposes C-SAMT, a web tool for collaborative modeling of UML class diagrams. Developers can benefit from using C-SAMT when performing modeling tasks, such as creating domain models in parallel, and collaboratively. Evaluation. We recruited 20 industry professionals to perform a qualitative evaluation of the tool through a questionnaire. Results. Majority of Industry professionals (85%, 17/20) reported that totally agree that the communication channel of the tool worked properly, they also (80%, 16/20) totally agreed the models generated collaboratively with C-SAMT had small numbers of conflicts, and they also (90%, ...

British Journal of Mathematics & Computer Science, 2015

_______________________________________________________________________________ Abstract The Unified Modeling Language (UML) is a general-purpose visual modeling language for specifying software-intensive systems. More precisely, it is a graphical language for visualizing, specifying, constructing and documenting the artifacts of software-intensive systems. UML is a key enabling technology for Software Developers and Software Engineers who seek to transition from traditional, human-intensive, code-centric software development processes to Model-Driven Development (MDD) processes that are requirements-driven and architecture-centric. However, Due to the lack of skills by developers and general purpose nature of UML diagrams, many developers abuse it by drawing diagrams that did not match particular activities or scenarios in the software project. This study makes a review of how UML is abuse and also makes a simple representation of UML diagrams.

Proceedings of the 3rd International Workshop on Model-Driven Architecture and Modeling-Driven Software Development

System modeling is one of the important tasks to be solved during software development. As more complex software systems become as higher requirements are defined for demonstrative presentation of the system to be developed. To solve this task the main attention is devoted to the transparency of the model elements within the graphical presentation of the system. The paper defines the classification of different types of UML diagrams, which are created during development of the software system. This classification is based on the different combinations of nodes and arcs of the diagram graph. The UML class diagram is selected for deeper analysis to the elements' layout. Authors offer to use main principles of the genetic algorithm to automate the replacement of the diagram created in the manual way. Current results are quite theoretical yet and authors will continue the research based on the issues defined in this paper. Galapovs A. and Nikiforova O.. Several Issues on the Definition of Algorithm for the Layout of the UML Class Diagrams.

The Journal of Object Technology, 2005

The demand for increased software quality has resulted in quality being more of differentiator between products than it ever has been before. For this reason, software developers need objective and valid measures for use in the evaluation and improvement of product quality from the initial stages of development. Class diagrams are a key artifact in the development of object-oriented (OO) software because they lay the foundation for all later design and implementation work. It follows that emphasizing class diagram quality may significantly contribute to higher quality OO software systems. The primary aim of this work, therefore, is to present a survey, as complete as possible, of the existing relevant works regarding class diagram metrics. Thus, from works previously published, researchers and practitioners alike may gain broad and ready access to insights for measuring these quality characteristics. Another aim of this work is to help reveal areas of research either lacking completion or yet to undertaken. A SURVEY OF METRICS FOR UML CLASS DIAGRAMS 60 J OURNAL OF OBJECT TECHNOLOGY V OL. 4, NO. 9 Recently, paradigms such as Model-Driven Development [Atkin03] and the Model-Driven Architecture [OMG02] have emphasized the importance of "good" models from the beginning of the life cycle. For that reason, the main focus must be on the quality of models obtained in these "early" stages. In the OO paradigm one of the key artifacts is the class diagram. The class diagram constitutes the backbone of the OO development and provides a solid foundation for the design and the implementation of software. Therefore, class diagram quality has great influence over the system that is ultimately implemented. Quality in software products is characterised by the presence of different external attributes 1 such as functionality, reliability, usability, efficiency, maintainability and portability [ISO01]. But these attributes can only be measured late in the OO software development life cycle. Therefore, it is necessary to find early indicators of such qualities based, for example, on the structural properties of class diagrams [Briand00a]. This is the context where software measurement is fundamental, because measures can allow us to evaluate class diagram quality characteristics in an objective way, thus avoiding a bias in the evaluation process. Measuring class diagram quality allows OO software designers: • to identify weak design spots when it costs less to improve them, rather than repair consequent errors at later implementation phases. • to choose between design alternatives in an objective way. • to predict external quality characteristics such as, maintainability, reusability, etc., and improve resource allocation based on these predictions. Although in the OO software measurement arena the need for measures that can be applied in the early phases of the development process is emerging, up until a few years ago the work done in this sense was scarce because most software measurement researchers focused on the measurement of code and advanced design [Zuse98; Hende96; Fento97; Etzko99; etc.). The aim of this work is to present a broad survey of the existing literature of OO measures that can be applied to measure internal quality attributes of class diagrams, considering the following proposals: Chidamber and Kemerer [Chida91; Chida94], Li and Henry [Li93b], Brito e Abreu and Carapuça [Brito94], Lorenz and Kidd [Loren94], Briand et al. [Brian97], Marchesi [March98], Harrison et al. [Harri98], Bansiya et al. [Bansi99; Bansi02]; Genero et al. [Gener00; Gener02]. In a previous work El-Emam [El-Em01] presented an interesting state-of-the-art of OO metrics and aspects related to their theoretical and empirical validity, but he only focused on one quality characteristic, faultproneness. Card et al. [Card01] also published a broad survey of the literature that assesses the state-of-the-art and practice in OO measurement and modelling, and maps the information collected onto the Practical Software Measurement framework (PSM), specially focusing on the view of quality as functional correctness. The objective of the current work is to some extent wider, covering other quality aspects [ISO01]. More 1 Internal quality attributes are those that can be measured purely in terms of the product (e.g., complexity, coupling, cohesion, etc.). In other words, an internal attribute can be measured by examining the product on its own, separate from its behaviour [Fento97]. External quality attributes are those that can be measured only with respect to how the product relates to its environment. Here, the behaviour of the product is more important than the product itself.

International Journal of Advanced Computer Science and Applications, 2016

Lots of Organizations before they are setup survey the maintainability of programming frameworks. To give quality program design there exists a critical strategy called Object-Oriented Framework. Object-Oriented estimations might be utilized to study the judgment skills suite of a class diagram's structure particularly programming valuations and how the models have been developed and portrayed. The UML Class Diagram metrics maintain the Object-Oriented software. It is maintained through the investigation of the association among object oriented metrics and maintainability. This paper shows the effects of a scientific evaluation of software maintainability forecast and metrics. The research aims at the software quality attribute of maintainability as opposite to the method of software maintenance. It also aims to find out the vital correlation between structural complexity metrics and maintenance time. Several investigators have done copious in it, got lots of theoretical outcomes, and subsequently established a chain of practical uses. Due to dynamic changes in object-oriented technology, in today's scenario the class diagram is an essential UML model, as, researcher must first get to know the use of software in a scientific manner. It is an affordable strategy which has had an exceptional result in recent times. This paper is related to UML class diagram metrics through which a way is provided to maintain UML class diagram complexity weights. UML Class diagram's qualities will efficiently and technically show the complexity of Object-Oriented Software. A more specific research study has shown that the technique is associated with individual's experience and also can be useful to improve software quality.