 |
 |
|
|
 |
The <CRUDEL> tag identifies if it is necessary to implement all CRUDEL methods or not
Usability:The <CRUDEL> tag is a boolean type. If it is set to true it means that the system implements all CRUDEL method for the entity class; otherwise if it is set to false, the system does not implements the CRUDEL method. The CRUDEL tag must be set only in a Focus or Manager class.
Effect:If the <CRUDEL> tag is set true, the system, automatically, generate the CRUDEL method. The system generates a method in all the tiers ; in the user tier it generates the user interface to interact with a CRUDEL method, so the user can Create, Read, Update, Delete, verify if a particular data object Exist and List the data; into a workspace and resource tier it generates methods that delegates to the lower tier, and, into a resource tier it generates all CRUDEL method for persist the data.
The CodeAndParameter (<CandP>) stereotype for a business component contains classes to manage "code and value" data. The CodeAndParamenter component has relationships with all the other business components, it is a very simple class without much logic; normally it manages simple data types consisting of plain attributes with no relations. There is not a Prime class inside: all classes are prime. The Manager class manages all the classes defined in the business component. This component does not depends on other functional business components. Examples of CandP data types are:
zip-Code: it contains two attributes code and description
customer type: it contains two attribute code and description
payment type: it contains two attributes code and description
Usability:This stereotype is applicable to any component.
Effect:The system generates a separate package for the CodeAndParameter package, into this package there are some entity class (the code and value data) and only one Manager class; through the manager class all the other business components can access the data type and manage its objects.
The <Create> stereotype identifies an insert operation; it defines that the target method creates and persists data.
Usability: This stereotype is applicable only to methods of classes of typeor . Inside these classes there will be normally only one method; the method must have one input parameter (the data object to create) and one output parameter (the persistence id)
Effect: The system generates the code to create a new data object. In the resource tier, JunoMDA(TM) generates the code to insert an object using the target persistency technology (e.g.. the SQL statements for a relational database). In the enterprise and workspace tier, it generates a method that delegates to the lower tier. In the user tier, it generates the appropriate users-interface to manage the business object creation.
The <Delete> stereotype identifies a delete operation, it defines that the target method deletes and persists data.
Usability: This stereotype is applicable only to methods of classes of typeor . Inside these classes there will be normally only one method; the method must have one input parameter (the id of data object to deleted).
Effect: The system generates the code to delete a data object into the database. In the resource tier, JunoMDA(TM) generates the code to delete an object using the target persistency technology (e.g. the SQL statements for a relational database). In the enterprise and workspace tier, it generates a method that delegates to the lower tier. In the user tier,it generates the appropriate users-interface to manage the business object creation.
The <Entity> stereotype identifies a business data type.
Usability:The Entity stereotype is to be assigned to classes that represent business information (e.g. “invoice”, “contract”, “order”). Its focus class will manage it.
Effect: JunoMDA(TM) generates for all business objects with stereotype entity the class into the resource, workspace and enterprise tier. The class into resource tier contain the attribute to interact with a persistency technology. The class into enterprise tier contain the attribute for represent the business object into the user tier and for resolve the business relationship The class into workspace tier, it is able to convert the enterprise class into resource class and vice-versa.
Define the tier. For future implementation.
The <Exist> stereotype identifies an operation that it tests if a data object exist.
Usability: This stereotype is applicable only to methods of classes typeor . Inside these classes there will be normally only one method; the method must have one input parameter (the id of data object) and one output parameter (a boolean value).
Effect: The system generates the code to check if a data object exist into the database. In the resource tier, JunoMDA(TM) generates the code to verify if an object exist using the target persistency technology (e.g. the SQL statements for relational database). In the enterprise and workspace tier, it generates methods that delegates to the lower tier In the user tier,it generates the appropriate users-interface for print out the test of the exist operation.
The <Focus> stereotype identifies the focus class of the tier.
Usability: inside each tier there is only one Focus class; it is the one that manages the data types owned by the business component. The focus class implements the business rules, the CRUDEL operations and other methods to resolve relationship between the entities. In the focus class it is necessary to add a CRUDEL tag, for defining if the system must implements or not all the CRUDEL methods.
Effect:The system generates a control class with all the methods for managing the owned data types. Inside the Focus class JunoMDA(TM) generates the CRUDEL methods for all business objects; it creates then automatically for all entity business object except for the prime; in case of the Focus class has the tag CRUDEL set to true, JunoMDA(TM) generates the CRUDEL methods also for the prime business object. In the user tier, it generates appropriate user interface for manipulating the prime business object and the its relationship. In the enterprise and workspace tier, it generates a method that delegates to the lower tiers. In the resource tier, it generates all the methods for interacting with the persistency layer.
The <List> stereotype identifies an operation that return a list of data objects, it returns a list of objects satisfying a particular requirement.
Usability: This stereotype is applicable only to methods of classes typeor . Inside these classes there will be normally only one method; the method must have one input parameter (the data object that contains the requirements) and one output parameter (the list of data object).
Effect: The system generates the code to return a list of data objects given . In the resource tier, JunoMDA(TM) generates the code to find the data into the persistence (e.g. the SQL statements for the read a record from a relational database). In the enterprise and workspace tiers, it generates methods that delegates to the lower tier In the user tier, it generates the appropriate users-interface to manage the business object creation
The <Lookup> stereotype identified which fields are visible in a lookup response; it represent the attribute that they will be visible into a user interface after a lookup question. (e.g. If the application propose a field that contains a list of customers information, inside it will be only the attribute with a lookup stereotype)
Usability: The attributes that have a lookup stereotype will be visible in into user tier with a response of a list operation.
Effect: The system generates in the workspace tier method that retrieve data, from the persistency throw the enterprise tier, and display, into the user tier, only the attribute with lookup stereotype.
The <Manager> stereotype identifies the focus class of a CodeAndParameter business component.
Usability: This stereotype is applicable only to one single class of CodeAndParamter. This class is the only one that can manage the entities defined inside the CodeAndParameter component, it implements all the methods for reading, modifying and deleting the data. In this business component it is necessary define a CRUDEL tag. This tag states that the system must implement all the CRUDEL methods.
Effect: The system generates a main class with all method for mange the CandP entity. In the user tier, it generate a main class with the particular user interface to manipulate the single entity In the enterprise and workspace tier, it generate delegator methods for communicating with the lower tier. In the resource tier, it generate methods for interacting to the persistency layer. If there is a CRUDEL tag set to true, the system implements, in all the tier, the CRUDEL method for all the entity defined into the package.
The <Primary key>stereotype identifies a unique key.
Usability: The attribute with a primary key stereotype represents the unique key for the business object. there is only one primary key inside a business object. This attribute normally is a string data type and it is impossible to insert or modify the data value; into the user tier the relative field it is disabled, it set to read only, it is calculated automatically into the enterprise tier runtime during the application,
Effect: JunoMDA(TM) uses the attribute, with a stereotype primary key, as input parameter in all method, where it is necessary to identified a particular data value or it is necessary to retrieve a data object from a persistency layer.
The <Prime> stereotype identifies a main business object
Usability:The prime class is the main business object of the package; all methods, classes or what else inside the business component, are designed to solve the business problems of the prime class.
Effect:When, into a focus class, the tag CRUDEL is set to true, the system generate the CRUDEL method for the class with prime stereotype; into the create and update method the input parameter will be a prime class; into list and read method the output parameter will be a prime class; into the persistence tier the system refer to a prime class to identify the correct persistence representation. In user tier it uses the prime class for designed the user interface.
The <Read> stereotype identifies an operation that retrieves data.
Usability: This stereotype is applicable only to methods of class typeor . Inside these classes there will be only one method; the method must have one input parameter (the persistence id of the data object to retrieve) and one output parameter (the data object)
Effect: The system generates the code to retrieve a data object. In the resource tier, it generates the code to retrieve an object using the target persistency technology (e.g. using SQL statements for a relational database). In the enterprise and workspace tier, it generates methods that delegates to the lower tier. In the user tier, it generates the appropriate users-interface to manage the business object creation. If the object to be read is a composed object (the composition association is used) also the component objects will be retrieved.
The <Update> stereotype identifies a change operation, it permits to modify a data into the persistency.
Usability: This stereotype is applicable only to methods of classes of typeor . Inside these class there will be normally only one method; the method must have one input parameter (the data object to be modified).
Effect: The system generates the code to modify a data object. In the resource tier, JunoMDA(TM) generates the code to modify an object using the target persistency technology (e.g. the SQL statements for a relational database), all the attributes of the data object will be modified. In the enterprise and workspace tier, it generates a method that delegates to the lower tier. In the user tier, it generates the appropriate users-interface to manage the business object creation. If the object to be update is a composed object (the composition association is used) also the component objects will be updated.