功能亮點(diǎn)：

顯示調(diào)用上下文:在序列圖中，當(dāng)鼠標(biāo)在調(diào)用上懸停的時(shí)候，就會彈出提示框，顯示出調(diào)用方法的參數(shù)和返回值。

顯示運(yùn)行時(shí)SQL：不管是哪種JDBC框架，MaintainJ都能夠捕獲到發(fā)送到數(shù)據(jù)庫實(shí)際雨欣的SQL語句以及其中的參數(shù)。

支持多JVM的應(yīng)用程序：用戶可以跟蹤運(yùn)行多個(gè)JVM上的應(yīng)用程序，并且能夠在單獨(dú)的序列圖中看到端到端的調(diào)用流程。

大綱視圖：序列圖的大綱視圖會顯示出用例中的所有類和調(diào)用能夠一次選中并刪除多個(gè)包、類或者調(diào)用。并且在序列圖中添加了一個(gè)選項(xiàng)。可以把所有g(shù)etter和setter方法篩選掉。

響應(yīng):節(jié)約時(shí)間40%！

優(yōu)化：節(jié)約時(shí)間20%！

響應(yīng):節(jié)約時(shí)間40%！

 
（注：左右圖為使用MaintainJ前后的結(jié)果）

文檔工作：節(jié)約時(shí)間90%！

---

新項(xiàng)目啟動：節(jié)約時(shí)間75%！

How does MaintainJ help users？

• Using MaintainJ, Java developers can quickly analyze, understand, document and enhance large Java code bases。
• MaintainJ generates detailed runtime sequence and class diagrams for a single use case。The arguments and return value of the call are shown in the sequence diagram. The runtime SQL calls made during a use case, regardless of the database frameworks used, are shown. All these details help developers to quickly troubleshoot a problem or to analyze and enhance the application。
• MaintainJ supports tracing applications deployed across multiple JVM's。The call trace captured on different JVM?s can be merged to view the end-to-end call flow across JVM?s。
• MaintainJ supports runtime impact analysis。
• Users can filter out the unwanted details from the MaintainJ generated diagrams and then export the diagrams as UML2 model files。
• Any UML diagrams generated at runtime can be verbose and difficult to read. MaintainJ provides simple user interface to dynamically explore the sequence diagrams. Users can also search for a class, method or database table or field used in the use case。
• MaintainJ offers various options to filter out unwanted details from the generated diagrams and to view them at the level of abstraction that the user want。
• Users can easily troubleshoot multi-threaded applications using MaintainJ - The sequence diagram shows the runtime interactions between threads in different colors. This helps developers to quickly troubleshoot a multi-threaded application, which would be hard to do using a traditional debugger。
• MaintainJ integrates seamlessly with JUnit - Users can generate a sequence diagram for every test case and check the sequence diagram for any troubleshooting later。
• MaintainJ saves lot of effort for teams that maintain large Java applications。

Why should developers be interested?

Any developer who has ever tried to change a large Java application should not need much persuasion. For the remaining few, here are a few reasons :

Dynamic Binding - Dynamic or runtime binding in Java makes understanding code more difficult. Developers often need to understand the runtime object interactions for a specific use case either to debug or enhance the application. Dynamic binding helps in building very flexible systems but, at the same time it increases the time to understand the system. It is also common to employ multiple levels of dynamic binding, like a Vector containing another Vector, which further complicates the issue.

Observer Pattern - Many enterprise applications follow Observer Pattern for flexibility, where 'listener' (or observer) objects change model state besides 'listening' (or observing) for the state changes. When many such listener objects, which are often determined at runtime, change the model, it becomes hard to understand and debug a large application.

Multi-threaded Applications - Multi-threaded applications are always difficult to code and debug. Using MaintainJ, one can see the sequence of method calls happening in each thread in a neat sequence diagram. This makes debugging multi-threaded applications much easier.

Externalized Data and Rules - Externalizing configuration data as well as rule based logic to XML files is very commonly found in the present day Java applications. Very often, the logic to determine the runtime classes is soft-coded in xml files. In a not so well documented large-scale system, it is very hard to understand how the xml file drive the system.

Poor Design - Designing robust and flexible systems at the same time is hard. Maintaining them as the systems evolve is harder. If poor design slips into this equation, it becomes very hard to understand a system after 2-3 years from initial launch.

Here are some other scenarios where MaintainJ helps developers.

Complements Debugger - MaintainJ complements debugger rather than replacing it. By generating the class and sequence diagrams for a use case, it reduces the time spent in debugger. Unlike other reverse engineering tools, MaintainJ offers uncluttered and focused UML  diagrams. For sequence diagrams, which get cluttered very easily, MaintainJ offers features like call folding to generate crisp diagrams.

During Code reviews - MaintainJ can also be used during code reviews. Rather than reviewing the entire source code, one can review the diagrams to find deviations from the design standards. Class diagrams showing the dependencies help to weed out unwanted dependencies.

For Agile Teams - For agile programming teams, MaintainJ provides always up-to-date documentation of the system. Useful UML diagrams can be generated whenever one needs them.