Guest View: The Horizontal Tool Integration Imperative



Email    print   
January 15, 2008 —  (Page 1 of 3)
While vertical tool integration might be good for vendors—stickiness equals revenue, equals lock-in, equals more revenue—consequences for customers aren’t all that positive. What are we solving for: vendor profitability or better software, faster and cheaper? Certainly vertical integration means at least some tools might work together, in some form or fashion, but no one has cornered the market on brain cells in today’s world, which is why a diverse portfolio of tools and applications will always be necessary.

Baby steps get you nowhere. It’s time to start thinking about how to deliver step-function improvements in quality—and this will require horizontal integration, or tools that talk to tools across vendor boundaries—i.e., time to play nice together. Expose those APIs and internal data formats. Add capabilities for data export and import.

I recently looked across our own development environment and was shocked to see what a significant contribution we are making to Intel and AMD’s top-line growth, not to mention global warming. We have a somewhat standard continuous integration environment that compiles code every five minutes if changes in our source code management system have been detected, integrates nightly, runs regression tests and a bunch of the other well-known tools.

The hitch is that most of these tools spend most of their time doing the same things: a compiler (parses source, builds an abstract syntax tree [AST]…), PMD for static analysis (parses source, builds an AST...), FindBugs for static analysis (parses byte code, builds an internal structure…), Dependency Finder for interdependency mapping (parses byte code, builds an internal structure…), Ounce Labs for source code security (parses source, produces internal representation…), SWaudit for continuous software quality audits (parses source, produces internal representation…), EMMA for line coverage (instruments bytecode…), Cobertura for branch coverage (instruments byte code…), Infrared for performance profiling (instruments byte code…)…well, you get the picture.

Streamlining the Process
So let’s think about how to streamline this. Parse source once, create “openly available and published abstract syntax tree” once, analyze many. Parse byte code, create “openly available and published internal structure” once, analyze many. Instrument for all data that can be collected at the same time via an “openly available and published” instrumentation framework, collect as much as possible in a single run, then repeat as appropriate (e.g., for performance profiling, footprint analysis, etc.).




Pages 1 2 3 


Share this link: http://sdt.bz/31648
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Integration Watch: The quickly changing market for continuous integration
Continuous integration is gaining more acceptance, but as a consequence it means that some platforms will be the focus Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb