Lattix has released version 4.5 of re-architecting software. This version includes new functionality to enable architects anada developers to visualize, re-architect, test, and communicate the architecture of a complex software system during development lifecyle, including design and modeling with UML or SysML.

New to Lattix 4.5 is support for UML and SysML which enables the Dependency Structure Matrix (DSM) approach to be applied to system models. With the new UML/SysML module in Lattix 4.5, it is now possible to easily construct a DSM that unites the various perspectives of UML and SysML systems modeling approaches into a scalable big picture view. Because UML and SysML diagrams contain requirements, use case scenarios and design information, the DSM can now be used to unite these different perspectives into a single view so that the impact of changes to requirements can be more readily understood.

"With this new module and more capabilities in Lattix 4.5 for re-architecting complex software systems , we continue to increase the value of the DSM approach across the development lifecycle," explains Lattix's Neeraj Sangal. "Now during the earliest stages of design, it is possible to identify undesirable interdependencies and expose key design decisions for the entire team."

In addition to the new UML/SysML module, Lattix 4.5 contains these new features and enhancements:

• Improvements to the Conceptual Architecture Diagram, including enhanced editing capabilities and setting of layering rules
• New Partitioning Algorithms provide more ways to explore different structures and groupings of system elements
• Improved Cycle Report that lists all dependency cycles between subsystems at all levels of the system hierarchy for quick identification of problemmatic dependencies
• Enhancements to the Understand for C++ module include the ability to navigate to the location of a dependency in the source file

Lattix's Dependency Structure Matrix (DSM) approach uses dependencies to create the most accurate and scalable blueprint of software applications, databases and systems. Architects and developers can analyze their systems in detail, edit the structure to create what-if scenarios, and specify design rules, allowing them to formalize and communicate the intended architecture to the entire organization.