Buzz about Lattix
db4objects, Inc. writes about Lattix in latest newsletter
Modularity with Lattix-- We were looking for a better way to analyze and modularize the db4o architecture. We found a great tool called Lattix.
Lattix enables us to create dependency models of all the modules in db4o so that we can analyze the dependencies within our architecture in detail, set objectives for how the architecture should evolve, and then measure improvements over time. In essence, Lattix supports our effort to keep the code as modular as possible. Why is that important? Because it promotes:
- higher quality code
- higher productivity
- better knowledge transfer
- better collaboration in distributed environments
- contributions from the community
Our long term objective is to have a framework that can grow a rich feature set over time without growing in complexity, very much like what Eclipse has turned out to be. We believe that Lattix is going to help us obtain that objective."
Read the full newsletter here...
Ralf Westphal blogs about his analysis of the .NET Framework architecture using Lattix LDM
"Have you ever thought about the quality of your code? Well, I bet. Have you ever strived for a sound architecture of your software solutions? Well, I hope. Do you have a process in place to constantly monitor the quality of your software´s architecture and code? Well, you should. But not only should you. Every single software team should. Planning for quality and constant qualitiy monitoring should be the fundamental activities in any software project.
...The other day, though, I stumbled over yet another software quality assessment tool: Lattix LDM. And what impressed me immediately was it´s easy to understand output based on the intuitive concept of the Dependency Structure Matrix (DSM)."
Read the full blog here...
David Berlind of ZDNet Interviews Lattix for "Why innovative tool makers ride the Eclipse horse first"
Given my recent bet with Sun's Tim Bray, I'm definitely a bit more sensitized to anything that's related to NetBeans or Eclipse. So, when yesterday's announcement by development toolmaker Lattix entered my inbox bearing the title Lattix LDM for Eclipse Now Available, I figured why not give them a call to find out what the tool was for, if the company was supporting NetBeans as well, and why it picked Eclipse first.
Read the interview here..
Jukka Zitting's Analysis of Apache Jackrabbit
"Tim Bray pointed to David Berlind who pointed to the Lattix company. Lattix makes a tool called Lattix LDM that uses a Dependency Structure Matrix to work with software architecture. I watched the nice Lattix demo and decided to try the software out."
Read the full blog here...
Mike Milinkovich, Executive Director, Eclipse Foundation:
"I've been trying to find the time to write this posting ever since I got back from EclipseWorld. Obviously, in this job I get to see a lot of demos of tools built with Eclipse. A lot of them are pretty cool. Everyone once in a while I see something that just blows my socks off."
Read the full blog here...
Jean-Jacques Dubray, ebPML.org blog:
"Some of the people I was privileged to work with at Eigner are launching their startup after about 18 months of hard work. This is one of the best engineering team I worked with in terms of quality, vision and speed of execution (not to mention camaraderie). So I was not surprised when I tried their latest product. Lattix is applying a relatively old engineering methodology (DSM) to software architecture. Design Structure Matrices have been applied successfully to a wide variety of engineering disciplines but this is the first time it is applied to software construction via some work done at MIT. An introduction on DSM can be found here.
Lattix lets you analyze, visualize and constrain the layering of your code. Its parses your project (or jars) to create the DSM automatically. Software, unlike other engineering discipline, does not give us the luxury to "visualize" easily what is being build as Mark Masterson posted recently.
As you build a house you get a good feel if it was "architected" right. Lattix is the first tool that allows me to "visualize" what is being built and somehow constrain it by specifying architectural rules. That's new and that's fresh. Lot's of us have tried UML and understand its limitation when the number of artifacts becomes large. DSMs are very different, they scale relatively well (I say relatively, because I am not sure the matrix notation is necessarily optimal here, maybe there are more compact ways to represent hollow matrices, but still Lattix is designed from the get go to work with very large projects). DSMs are about understanding the layering of a project and enforcing it. If you are working on a Java project I encourage you try for yourself, it takes about 30 minutes to get started. I will not be surprised if this tool becomes a must have next to Together, OptimizeIt and JMeter."
