To specify Activity Parameter Node type by using the Specification window The type is specified for a Activity Parameter Node. In the Create As dialog, select element kind. Do one of the following: - Select an existing element from the Select Type menu.Click on the smart manipulator toolbar.Select the Activity Parameter Node shape.To specify Activity Parameter Node type by using the Specify Type button You can also create an Activity Parameter Node by drawing an Object Flow directly to or from the Activity diagram frame.Īfter the Activity Parameter Node is created, you can specify it's type. If a parameter with an inout direction is selected for the Activity Parameter Node creation, then two Activity Parameter Nodes are created on the diagram frame. parameters that have assigned parameters that are also owned by the same activity.parameters that are owned by the same activity as the activity diagram.parameters that are not displayed on the diagram frame.In the menu, the following Activity Parameter Nodes are listed: When creating an Activity Parameter Node on a diagram frame, click on the diagram frame to open the menu. The direction of the parameter is set according to the Object Flow direction, otherwise you can set it manually by simply right-clicking the activity parameter, and selecting the preferred direction. The parameter name, type, and multiplicity are synchronized with the pin or Object Node from which/to which the Object Flow was created. The parameter for the Activity Parameter Node is created automatically. Specify the parameter, and click Close.Select Edit New Parameter to specify the parameter.The Activity Parameter Node is created, and its shortcut menu opens. In the Activity diagram palette, click the arrow next to the Object Node button to expand the list, then select Activity Parameter Node.In the evaluation and analyzing the suitable integration method, we applied the different methods on homogeneous mobile applications and found that using ontology increased the detection percentage approximately by 11.3% in addition to guaranteed consistency. The results showed that there was a high positive relation between Modelio and Protégé which implies that the combination between both increases the accuracy level of the detection of anti-patterns. The results also showed the correlation between the selected tools which we used as Modelio, the Protégé platform, and the OLED editor of the OntoUML. "The anti-patterns in the class group" is the most group that has the maximum occurrences of anti-patterns and "The anti-patterns in the operation group" is the smallest one that has the minimum occurrences of the anti-patterns which are detected by the proposed method. The proposed method introduced a new classification of the anti-patterns divided into four groups. Results The proposed method detected 15 semantic and structural design anti-patterns which have appeared 1,262 times in a random sample of 29 mobile applications. We demonstrate a semantic integration method to reduce the incidence of anti-patterns using the ontology merging on mobile applications. Selecting a browser is not a criterion in this method because the proposed method is applied on a design level. We choose 29 mobile applications randomly. We present and test a new method that generates the OWL ontology of mobile applications and analyzes the relationships among object-oriented anti-patterns and offer methods to resolve the anti-patterns by detecting and treating 15 different design's semantic and structural anti-patterns that occurred in analyzing of 29 mobile applications. The proposed method is via reverse-engineering and ontology by using a UML modeling environment, an OWL ontology-based platform and ontology-driven conceptual modeling. Methods We proposed a general method to detect mobile applications' anti-patterns that can detect both semantic and structural design anti-patterns. Additionally, it guides developers to refactor their applications and consequently enhance their quality. Thus, the automatic detection of anti-patterns is a vital process that facilitates both maintenance and evolution tasks. However, catering to these imperatives may bring about poor outline decisions on design choices, known as anti-patterns, which may possibly corrupt programming quality and execution. Applications must be produced rapidly and advance persistently in order to fit new client requirements and execution settings. Abstract : Background Portable-devices applications (Android applications) are becoming complex software systems that must be developed quickly and continuously evolved to fit new user requirements and execution contexts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |