ENTRY MODEL PROCESSING
Sparx Systems Enterprise Architect is a visual modeling and design tool based on the OMG UML. The platform supports: the design and construction of software systems; modeling business processes; and modeling industry based domains. It is used by businesses and organizations to not only model the architecture of their systems, but to process the implementation of these models across the full application development life-cycle. (source : Wikipédia)
Rational Rose is an object-oriented Unified Modeling Language (UML) software design tool intended for visual modeling and component construction of enterprise-level software applications. (source :https://searchmicroservices.techtarget.com/definition/Rational-Rose)
UML class diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects. (source : Wikipedia)
XMI input module
The XMI input module receives data structures in the XMI format, and maps is to a proprietary XML format developed by Pulsar. Such model (XMI format) are generated for example by the
XML input module
blabla : + de détail à propos du module XML. Il prend les fichiers XML qui sortent de Rational Rose par rexemple Pulsar has defined a proprietary XML format for storing model information. This format is used as input to MODEL BINDER for any generation operation.
UML diagram class input module
An optional module allows you to correct the airworthiness information in the UML model beforehand.
The mapper variable contains all the information of the model considered in a structure of the entity collections are grouped by package / namespace.
Entities can be linked according to two kinds of parent-child relationships:
1. "Children" entities are derived from a base entity, which may or may not be an abstract class.
2. "Related" entities have attributes whose type is defined by another entity.
The two entities at the ends of an Association are each linked to a role.
An association class is encoded as an Entity whose Association is marked by the "isLink" property.
Key word output module
This module should simply be used to list the entities of the model. This list may include aliases, for example by transforming the "camelCase" script into a series of words separated by spaces.
The result is an XML file that can then be used by a program to locate the names of the entities in a text. This list can then be used by MY MODEL MAPPER in other output modules , to add navigation hyperlinks between the definition texts and the entities mentioned in these texts.
Word output module
Word output module is a specific module for producing a data dictionary in Word.
Voir exemple p.133
XAR output module for xWiki
XAR output module is a module that generates an XAR file to import into an xWiki.
The goal is to display in a Wiki a documentation of the model considered by organizing the information: one page per class, one page per diagram. Hyperlinks allow you to navigate from the description of a class to another class mentioned in the page, or to click on a class represented in a diagram to reach the description page of this class.
The information to display for each class includes:
its name, its stereotype, its full path, its definition
the list of its attributes with their definition and type, specifying whether they are inherited from another class, with a link to the class defining their type
the list of relations whose class is either the source or the destination, with the role and the cardinality of the class in this relation, as well as the name and the definition of the relation, in specifying whether this relation is inherited from another class
the list of more general or more specific classes in an inheritance relation
the list of diagrams in which the class appears
The goal is to be able to quickly generate simple pages for all the entities of the considered model. These pages could then be integrated into a web application that implements the actions of creation, modification or deletion of data. This assumes that the data will itself be stored in a database structure directly derived from the model under consideration.
Voir p.132 exemples
HTML output module for documentation
SVBR output module
SVBR output module is a help module for the edition of business rules versus the data model considered, in particular according to the specifications of the SBVR standard (semantics of business vocabularies and business rules) developed by the OMG (Object Management Group).
The following functions have been successfully tested in this pre-prototype:
give a list of entities whose names begin with a certain string (ignoring the differences between upper and lower case)
once an entity has been selected, give its definition
Once an entity has been selected, list its attributes and filter this list in the same way, as and when typed if possible, keeping only the attributes whose name starts with the string characters already entered
Once an entity has been selected, list the associated entities and filter this list, as and when typed if possible, keeping only the associated entities whose name begins with the string of characters already Entrance ; then complete its role as well as the name of the relationship (if the relationship is named in the model)
Automatically format the strings already entered by recognizing their type according to the SBVR taxonomy.
To date, the input model stored in memory is used directly by a module developed in ReactJS to display elements of the model in relation to each other.
The first function allows you to select a class and choose an element from the list of its attributes, by retrieving the definition of the class and attribute: Figure 4 - function helping to find the attributes of a class
The second function makes it possible to select associated classes by recovering their definition as well as the details of their relation: Figure 5 - function helping to find associations
The third function allows to build a rule according to a predefined pattern by selecting elements that correspond to certain categories: Figure 6 - function to help write a rule by instantiating categories
The fourth function allows you to type a rule whose elements are automatically recognized and categorized: Figure 7 - function that helps writing a rule
The next step will be to insert the use of the first two functions in the fourth to allow the user to easily find the elements that can be associated in the rule that he is writing.
(attention, voir p.20 et p.27 dossier sophie)
HTML output module for Graphic Interface