Database modeling functionality in version 3.0 applies only to Oracle databases. Lattix expects to add capabilities for other databases such as Microsoft SQL Server and IBM DB2 in the future. Dependency models can be captured between database schemas, tables, stored procedures, and triggers.

A user of LDM 3.0 said he is using the product to eliminate redundancies in an Oracle database and examine object behaviors.

"We're trying to normalize one database that's going to be about 30 million to 100 million records," said user David Bell, staff programmer for the state of California in Sacramento.

Lattix LDM uses modules to parse files built around Java, C/C++, Oracle or the Hibernate object-relational mapping tool. Dependencies are represented via use of these modules. New in version 3.0 is a general-purpose LDI (Lattix Data Import) module that represents a user's specific Web services dependencies. LDI is an XML specification for loading dependency information from different languages, configuration files, and proprietary tools.

The product is effective at addressing complexity in software architectures, Bell said. "It gives me a bird's eye view of the data and a lot of its complexities in one shot, which I really like," he said.