Poll: What tools do you use for specs?

Do you use specialized, general purpose, or process-driven tools for application specs? Answer this question by taking our poll.

I recently had a conversation with someone about how the code developers write reflects the specs we're given. Most of the time that I deal with specs, they are generated in various apps in the Microsoft Office suite or in similar general purpose tools. There are many more tools for creating application specs, ranging from specialized tools that do not enforce a particular process to process-driven tools like the IBM Rational suite. I'm curious to hear what tools TechRepublic readers use for application specs.


Keep your engineering skills up to date by signing up for TechRepublic's free Software Engineer newsletter, delivered each Tuesday.


Justin James is the Lead Architect for Conigent.


I've been using (and promoting to my colleagues) DOORS, formerly a Telelogic product but now part of the IBM Rational suite. I'm not familiar with the other IBM Rational tools, but DOORS was not process-specific. In fact, I was part of a team at Procter and Gamble IT that developed our own methodology/documentation framework, and DOORS was the perfect tool to implement it.

Mike Page
Mike Page

I like using Word to create a project plan. I can share it with the customer, have them make changes going back and forth until both sides are in agreement. Then I design the code using a UML tool followed by implementation. It is a process I've used for more than a decade and it has proven itself to work well.

Slayer_ 1 Like

That way, there is no evidence when it all goes wrong :)


The base artifacts are from the Office suite, but enhanced with images from both modeling tools (for diagrams) and general purpose image tools (UI mockups). The general philosophy is to communicate as clearly as possible without drowning in text or unnecessary boilerplate.

Editor's Picks