Seeking a true "tool-chain"

Question

I just posted this as part of a reply to a question about the "best" bug-tracking software...

---

Well, a tool on its own is just a tool. And while all speak of a toolchain, most just mean a loose collection of tools. Why not look for a problem tracker that "plays well with other children"? That is to say, interfaces well with your IDE, your build tool, your version control system ...

In fact, I think I'll go now and ask a question about the best linked toolchain ...

---

So, any comments? I would prefer replies for developing C/C++ on Linux and using FOSS.

I use

• Eclipse - for coding and debugging, also its plugins for
  • Doxygen for auto code-documentation
  • Splint and CppCheck for static code analysis
  • CppUnit for automated testing
  • Bugzilla, et all for bug tracking
  • CVS, Subversion, etc, for version control
• Hudson - for automated builds, with plugins for
  • Doxygen for auto code-documentation
  • CppCheck for static code analysis
  • CppUnit for automated testing
  • Bugzilla, et all for bug tracking
  • CVS, Subversion, etc, for version control

I seem to be missing a tool for project management which interfaces with other "links" in the toolchain. How complete can we make it, end to end, and is there a "best" chain (or, at least, one with the most links)?

Edit: Let's not forget requirements tracking and project planning & tracking - end Edit

And has anyone every diagrammed the relationship between various tools?

Answer 1

G'day,

In my experience, I have found that trying to come up with a "definitive" tool chain can cause problems.

One of the worst is that it tends to force people into the "everything looks like a nail" approach to projects. That is, You've done the work to select the tools you think are suitable and you now have your tool suite.

In my experience, it is very difficult to get people to change their "canonical set" of tools for other projects once that tool set has been selected and annointed as such.

I've been doing this for over twenty years now in a variety of projects that ranged from on-board submarine sonar simulators to air-traffic control display systems to helicopter control systems. Even within the same company, different projects need different tool sets to address the various problems that are going to be encountered.

You might think that once you've selected a tool for a particular purpose then you can re-use that tool for all projects, e.g. your selection of BugZilla for bug tracking. But what if there is no suitable SMTP server available because you've got a distributed team and your mail server is internal, locked down, secure, for example.

I'd suggest that it would be better to establish a suite of possible tools from which you can select your project's tool suite from. For example, adding Trac or FogBuzz as a possible bug tracking mechanism.

A lot of things can affect your choice of tools. Off the top of my head I've got:

• geographical distribution of teams,
• internal lock down, i.e. no public access, of servers e.g. email, source repository, test platform, etc,
• having to interface to some existing system because of a desire to reuse aspects of that system, e.g. previous teams had had VisualSourceSafe inflicted upon them,
• customer insistence on the use of a particular platform,
• the management team for a new project having requirements that differ from the previous management team for regular management type reports,
• etc.

Having a suite of possibilities minimises the effect of "trying to squeeze a square peg into a round hole".

Anyway, you might find that you're able to trim down your suite of possibilities after a while because you can demonstrate a successful approach and so get enough traction within the company for the support of doing things the way you've previously done them.

HTH

Answer 2

Well its not FOSS but Rational supplies a complete tool chain (except for the compilers!),

You get IDEs, Class diagrams, use cases, requirements tracking, test tools, problem logging tools which integrate well all for a few thousand (or hundreds of) dollars.

None (aprt from the modeling tools) is best of breed, but, they are all pretty good and integrate well with each other.

Disclaimer:- My "toolset" of choice is vim,make, ddd, gmail and a moleskin notebook for modeling.