• Blog
  • Contact
Home
  • Products
    • Modules
      • ActionScript
      • Ada
      • C/C++ (with BSC, Doxygen, Klocwork, and Understand)
        • Klocwork
      • Delphi Pascal
      • Fortran
      • Java (with Spring and Hibernate)
      • JavaScript
      • .NET
      • Oracle
      • SQL Server
      • Sybase
      • UML/SysML (with XMI, IBM Rhapsody, SparxEA)
        • Rhapsody
      • LDI (with Excel)
    • LDM/LDV
      • Features
    • LDC
    • LattixWeb & Repository
    • Licensing & Pricing
    • FAQ
      • Installation
      • Approach
      • Howtos
      • Java Specific Issues
      • C/C++ Specific Issues
      • .NET Specific Issues
      • Database Specific Issues
      • Hibernate and Spring Specific Issues
  • Solutions
    • Embedded Systems
    • Enterprise Systems
    • Complex Systems
    • Case Studies
  • Services
    • Consulting
    • Training
    • Deployment/Integration
  • Technology
    • Analyzing Architecture
    • Example: A Dependency Model for ANT
    • Dependency Models and UML
  • News/Events
    • Lattix News
    • Events
    • Lattix Live Demos
      • What's New in Lattix 7.0
    • Buzz about Lattix
  • About
    • Partners
    • Management
    • Advisors
    • Corporate Fact Sheet
Lattix Demo
Watch Now
Attend a
Live Demo
Read our
Whitepapers

Lattix presents at the 7th International DSM Conference

Seattle, WA 4 Oct, 2005Lattix presented 3 separate papers at the 7th International DSM Conference:

Results of DSM Analysis of Software Systems in Industrial Applications

Managing System Architectures

New Techniques for Leveraging Hierarchy in DSMs

These presentations report the results of applying DSM to analyze and improve the architecture of existing software systems in a variety of industrial applications, including financial services, data storage systems, semiconductor equipment, and software. In an example of forward engineering, we will also show how the Dependency Model approach was used to develop the Lattix DSM product (Lattix LDM), from its conception to second major release.

The companies who utilized the Lattix approach did so for a variety of reasons: most were seeking to gain visibility to the architecture, several needed to replace large parts of a system, some wanted to improve the ability to customize and assess the impact of change, and finally all wanted to find ways to improve quality and efficiency of testing.

As a result of these projects, we learned that the critical visibility of the architecture could be achieved very quickly (often within days) by leveraging the existing hierarchy and reviewing the DSM with the designers to formalize their design intent. Furthermore, the DSM enabled us to prioritize remediation and to identify which to pursue in the short and long term. By monitoring the implementation continuously, the architecture of the first system remained clean even after one year of distributed development. 

Back to top

Lattix | North Reading MA 01864 | +1.978.664.5050 | copyright 2012