Automatic Generation of UML Class Diagrams for Object-oriented Design and Programing Course

UML Class diagram generation from textual requirements is an important task in object-oriented design and programing course.This study proposes a method for automatically generating class diagrams from Chinese textual requirements on the basis of Natural Language Processing(NLP)and mapping rules for sentence pattern matching.First,classes are identified through entity recognition rules and candidate class pruning rules using NLP from requirements.Second,class attributes and relationships between classes are extracted using mapping rules for sentence pattern matching on the basis of NLP.Third,we developed an assistant tool integrated into a precision micro classroom system for automatic generation of class diagram,to effectively assist the teaching of object-oriented design and programing course.Results are evaluated with precision,accuracy and recall from eight requirements of object-oriented design and programing course using truth values created by teachers.Our research should benefit beginners of object-oriented design and programing course,who may be students or software developers.It helps them to create correct domain models represented in the UML class diagram.

The Formal Semantics of an UML Activity Diagram

Due to lack of strictly defined formal semantics, an UML activity diagram is unsuitable for the tasks of formal analysis, verification and assertion on the system it describes. In this paper, Petri net is used to define the formal semantics of an UML activity diagram containing object flow states, laying a foundation for the precise description and analysis of a workflow system.

XML Schema Modeling through UML Class Diagram

A three-step XML Schema modeling method is presented, namely first establishing a diagram of conceptual modeling, then transforming it to UML class diagram and finally mapping it to XML Schema. A case study of handling furniture design data is given to illustrate the detail of conversion process.

UML Galaxy Diagram:An Approach of Conceptual Data Integration for OLAP

In e-commerce the multidimensional data analysis for OLAP (on-line analytical processing) based on the web data needs integrating various data sources such as XML (extensible markup language) data and relational data on the conceptual level. A conceptual data description approach of multidimensional data model was presented in order to conduct multidimensional data analysis of OLAP for multiple subjects. The UML (unified modeling language) galaxy diagram, describing the multidimensional structure of the conceptual integrating data at the conceptual level, was constructed. The approach was illuminated using a case of 2__roots UML galaxy diagram that takes one retailer and several suppliers of PC products into consideration.

Softw are Maintainability Prediction with UML Class Diagram

Software system can be classified into many function modules from the perspective of user. Unified modeling language( UML) class diagram of each function module was extracted,and design characteristic metrics which influenced software maintainability were selected based on UML class diagram.Choosing metrics of UML class diagram as predictors,and mean maintenance time of function module was regarded as software maintainability parameter. Software maintainability models were built by using back propagation( BP) neural network and radial basis function( RBF) neural network, respectively and were simulated by MATLAB. In order to evaluate the performance of models,the training results were analyzed and compared with leaveone-out cross-validation and model performance evaluation criterion. The result indicated that RBF arithmetic was superior to BP arithmetic in predicting software maintainability.

Event-Based Semantics of UML 2.X Concurrent Sequence Diagrams for Formal Verification

UML 2.X sequence diagrams(SD)are among privileged scenarios-based approaches dealing with the complexity of modeling the behaviors of some current systems.However,there are several issues related to the standard semantics of UML 2.X SD proposed by the Object Management Group(OMG).They mainly concern ambiguities of the interpretation of SDs,and the computation of causal relations between events which is not specifically laid out.Moreover,SD is a semi-formal language,and it does not support the verification of the modeled system.This justifies the considerable number of research studies intending to define formal semantics of UML SDs.We proposed in our previous work semantics covering the most popular combined fragments(CF)of control-flow ALT,OPT,LOOP and SEQ,allowing to model alternative,optional,iterative and sequential behaviors respectively.The proposed semantics is based on partial order theory relations that permit the computation of the precedence relations between the events of an SD with nested CFs.We also addressed the issue of the evaluation of the interaction constraint(guard)for guarded CFs,and the related synchronization issue.In this paper,we first extend our semantics,proposed in our previous work;indeed,we propose new rules for the computation of causal relations for SD with PAR and STRICT CFs(dedicated to modeling concurrent and strict behaviors respectively)as well as their nesting.Then,we propose a transformational semantics in Event-B.Our modeling approach emphasizes computation of causal relations,guard handling and transformational semantics into Event-B.The transformation of UML 2.X SD into the formal method Event-B allows us to perform several kinds of verification including simulation,trace acceptance,verification of properties,and verification of refinement relation between SDs.

DEVS and MBSE:A review

We review Discrete-Event system Specification(DEVS)in the context of Model-based Systems Engineering(MBSE)and discuss an application of DEVS methodology to MBSE.We outline support for an envisioned MBSE development cycle of DEVS top-to-bottom MBSE capability and offer an example of mapping UML activity diagrams into executable activity-based DEVS models.We close with conclusions and future research directions.