Subscribe in a reader

Folge Hypermodelling auf Twitter

IDE video Print E-mail

This picture shows the various views in eclipse. From each of those views, elements can be dragged and dropped into the query (A).


Also read about what Hypermodelling can be used for

A paper decribing the prototype can be found here.

The usage of Data Warehouse Technology is described here: 

First the basic usage of the tool is shown and a query is composed for elements that belong to the service layer. 

A developer can compose a query to uncover elements that are
belonging to the service layer. Therefore, he composes code slices that belong to this
layer together in a query. When he executes the query he can see results like working
sets in the package explorer. The slices in the query can be for example: (1) Classes that
are annotated by typically in the service layer appearing annotations, like @Service; (2)
Classes that have parent classes or interfaces that belong to the service layer, like
controller classes; (3) Classes that contain strings that are typical for service layer, like
“service” or “controller”. This way a query would reveal all source code that belongs to
the different concern slices. Additionally, concern slices that belong to a layer can be
offered as a group in the pre-defined concerns view. This way, a developer could just
drag and drop a layer query from the pre-defined concerns view without having the need
to assemble the query himself.

Dim lights Embed Embed this video on your site

A video showing how to uncover elements of the persistancy layer out of structural information:

Dim lights Embed Embed this video on your site

Revealing unsecured methods

Another challenge is to uncover unsecured publicly accessible methods to
identify potential security leaks. A developer can compose a query for those with the
Hypermodelling tool. With Hypermodelling a developer can query for classes that inherit a
framework class that makes them publicly available. Additionally, he can exclude the
secured classes in the query. Excluding secured classes is possible, because applications
are normally secured via Aspects or annotations. This structural information can be
added as excluded slice to the query. Hence, all publicly accessible methods that are not
secured can be uncovered easily. With other tools a complex query building process and
result representation in standard views is not possible.

Dim lights Embed Embed this video on your site

Deprecated method consumer.

Its really a not much liked job for developers. Elements of libraries they use get marked deprecated in the ndew version of the library. Developers face the challenge to gather all the artifacts that use such deprecated elements via the error and warnings view. This video shows howto reeval them with the hypermodelling approach. Furthermore, also other code slices can be added to exclude elements that consume deprecated methods that are not of interest for a developer.

Dim lights Embed Embed this video on your site

This video is just a short visualisation what could be possible in the IDE.

The audio quality is bad - thus this video is superseded. Its just online cause it shows many capabilities what could be possible. But it is not about a scenario.

Dim lights Embed Embed this video on your site