We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JIRA Issue: KIEKER-1300 Add signature/component abstraction filter Original Reporter: Andre van Hoorn
Currently, classes are mapped to components. However, sometimes logical components may be at certain levels of the package hierarchy.
Examples: 1. Current behavior: Signature a.b.C.d() -> Component a.b.C; operation d() 2. New (hierarchy level 2): a.b.C.d() -> Component a.B; operation c_d()
This functionality is already implemented in SLAstic including various tests. Different abstraction modes are supported.
The text was updated successfully, but these errors were encountered:
author nils-christian -- Mon, 28 Oct 2013 15:17:32 +0100
Aggregation techniques of traces are currently researched by Björn / Florian
Sorry, something went wrong.
avanhoorn
No branches or pull requests
JIRA Issue: KIEKER-1300 Add signature/component abstraction filter
Original Reporter: Andre van Hoorn
Currently, classes are mapped to components. However, sometimes logical components may be at certain levels of the package hierarchy.
Examples:
1. Current behavior: Signature a.b.C.d() -> Component a.b.C; operation d()
2. New (hierarchy level 2): a.b.C.d() -> Component a.B; operation c_d()
This functionality is already implemented in SLAstic including various tests. Different abstraction modes are supported.
The text was updated successfully, but these errors were encountered: