In this documentation, we will use this UML model to illustrate the search features.

Search elements

The search feature of Papyrus helps the user to find elements in the models. The user can choose between a text search and an OCL search.

As it is shown in the following image the user chooses the query kind he wants to use:

Text search

The user can do a simple search or an advanced search. The user makes his choice in the A area of the following image which represents the text search dialog.

Simple search

The following image illustrates a simple text search dialog:

• The user can specify the string pattern he/she is looking for in the A area.
  • Check the "Case sensitive" if case must be considered.
  • The user may also want to use regular expression to express the query. Then check "Regular expression" button. The regular expression must respect Java Regex.
• The user chooses whether he wants to search only in the name attribute of instances of UML::NamedElement or in all string attributes of instances of UML metaClasses, in B area.

For instance, the following search:

will provide the following results:

The comment is not returned because we were note looking for all string attributes.

However, this search:

will return :

Advanced search

The following image shows the advanced text search dialog.

• As in the simple search the user can specify the string pattern he/she is looking for, and may indicate if he uses regular expression or if he wants to consider case, in the A area.
• The user can filter the types of elements to search the string pattern in by selecting the UML metaClasses in area B . and stereotypes in area C.The user can also choose in which attributes he wants to do the research. The stereotypes displayed in the C area are the stereotypes which are actually applied to elements from model(s) in the the selected scope. For example if the selected scope is "Selected resources" only the stereotypes actually applied to elements of the current model will be displayed. But if the selected scope is "Workspace" the stereotypes applied in all models, from the current workspace, will be displayed.
• The user can specify, in the D area, if he wants to search for model elements with all and only the selected stereotypes applied. Forexample enforcing that only elements stereotyped <<Requirement>>and <<Block>> will not return elements with only the <<Requirement>> stereotype, or elementsstereotyped <<Requirement>>, <<Block>>, but also some other stereotype.The user can also specify, in area D, if he wants at least one of the selected stereotypesto be applied. For example if <<Requirement>> is selected, any element stereotyped <<Requirement>>, nomatter its other stereotypes, will be part of the search result.
• In the E area, the user can select all subelements of the actual selected element (UML metaClass), with the "Select Subelements" button.For example, if the user selects "NamedElement" and clicks on "Select subelements",all metaClasses which inherit of UML::NamedElement will be checked. If the name attribute of "NamedElement" is checked and the user selects "NamedElement" and then clicks on "Select subelements", all instances of UML::NamedElement and their name attribute will be checked. The user may also use self-explanatory buttonsto select/deselect all elements in both the UML elements and stereotypes lists.Finally, if the user changes the selected scope he should click on the "Refresh Lists" button. This will update the list of stereotypes displayed.

In the following image we search the pattern "my" in the attribute body of the metaClass "Comment". The research will give us all the instances of "Comment" having an attribute body matching with the string pattern.

The result will be

If the user select a stereotype or an UML metaClass without indicating a string pattern, the research will give him all the instances of the metaClasses he checked and all the elements having the applied stereotypes he checked.

For example the result of this research:

will be

If the user enforces that all and only selected stereotypes are applied, like in the following example:

Then the result will be the following:

If the user enforces that at least one selected stereotype is applied, like in the following example:

Then the result will be the following:

The user may also search attributes of elements or stereotypes, while enforcing stereotype application.

OCL search

The following image shows an OCL search dialog

The user writes his OCL query in the A area. The scope must be "Selected resources" if the user wants to do this kind of query.

Replace String

Should the user want to replace the matches of your search with another string, he/she may click on the "Replace" button in the search dialog. A new dialog will popup:

More details about the refactoring tool in the Model Refactor Wizard page.

Filter

The user can filter the results of the search by selecting the types of the elements he/she wants to show.

For instance, on the following search (we use the model 1):

the user may filter the results by clicking on the icon identified in a red rectangle in the following picture:

this will open a new dialog where the user can select the metaclasses he/she want to show:

then, the result page will show only the matches of the selected type:

If the user wants to remove this filtering, he/she may click on the Filters button as illustrated in previous picture. This will open the following dialog:

This work is developed by CEA LIST and sponsored by Ericsson in the context of Polarsys http://wiki.eclipse.org/Polarsys