|
|
 |
SOL UML Debugger |
|
|
|
Features: See briefly what it is all about
Technical characteristics: System requirements and other technical data
Short presentation: Look at how it works (Zipped PowerPoint presentation with animations)
Trial version, pricing, licensing, and purchasing: Available at Gentleware's site
Support: Send an email to info@sol.co.yu, with the subject "UML Debugger Support" and stating your license key
|
|
SOL UML Debugger is a tool that helps the developers test and debug their UML models and the target Java applications obtained from those models within the same integrated environment.
|
|
Features
Automatic detection of common object referencing bugs
Visualization of runtime Java object structure in UML
Available as a plug-in for Poseidon for UML by Gentleware AG
Debugging the structure and behavior of the real target application by its execution, not by interpretation of the (partially informal or incomplete) UML model. Therefore, the debugging process gives the real picture of the application’s structure and behavior.
Debugging at a higher level of abstraction - in UML, with an integrated view on the target application’s object structure. Therefore, the application’s structure is manipulated from within the UML model, not by digging into the target code.
Support for taking and archiving snapshots of object structure during testing scenarios, archiving testing scenarios, and replaying them. Therefore, regression testing is now enabled within one single integrated UML modeling environment.
No limitations on the kind of applications - all applications that are modeled in UML and implemented in Java can be tested and debugged. Therefore, the development of new systems as well as the maintenance of legacy systems can benefit from using SOL UML Debugger.
In more details, the features include:
Modeling of test object structures using UML object diagrams. There is no more need to write clumsy code for creating complex test structures – now they can be simply depicted in object diagrams.
Automatic creation of the test object structures in the target application, including invocation of objects’ constructors.
Invocation of operations of objects from the UML modeling tool. This includes passing of arguments of built-in data types, as well as references to objects in the model.
Browsing the target application’s object structure from the UML modeling tool, represented at the model level (using links of associations, not references).
Automatic reverse engineering of the target application’s object structure - update of the UML object model from the target application’s object structure.
Verification of UML modeling constraints on associations in the target application’s object structure and reporting of usual bugs, such as unsynchronized mutual references, illegal cardinalities, and violations of uniqueness.
Manual corrections of target application’s object structure by manipulating the UML object model.
Taking snapshots of object structures for archival purposes.
Replay of testing scenarios.
Automatic comparison of snapshots during replayed test scenarios with the archived correct ones, as a support for regression testing.
Generating Java code for replaying and reusing test scenarios.
Possibility to debug the model and the target application in a combined environment with the classical Java IDE and Java debugger.
Although SOL UML Debugger is not constrained to that particular kind of applications, its features are particularly useful and literally priceless in testing and debugging applications or their parts that have structure-intensive functionality, meaning that it predominantly manipulates with structures of objects (as instances of classes) and links between them (as instances of associations) and that its effect (regular or irregular, in presence of bugs) is manifested on complex object structures.
Technical Characteristics
It is a plug-in for Poseidon for UML modeling tool. Therefore, modeling, testing, and debugging can be accomplished in a single integrated modeling environment.
It is aimed for debugging target applications implemented in Java.
It does not require any additional hardware or software resources others than those required by Poseidon for UML.
|
|
|
