« Millions | Main | Animal Welfare »

Mar 19, 2005

How to Produce Good Software, Part 7

In part 6, I discussed the creation of a product roadmap. In this part, I list the various aspects of software development that I aim to cover in the next ten or so installments of this series.

Here are the aspects that come to mind:

  • programming language(s)
  • coding standards
  • development tools
  • development methodology
  • code and design reviews
  • API design
  • UI design
  • testing
  • documentation
  • installation
  • issue tracking
  • support
  • collaboration tools

If there is a topic that is missing that you'd like to hear my thoughts on, please let me know. Once all these topics have been covered, I will turn my attention to other aspects of producing software, such as building and maintaining a good software development team.

In the next part, I'll discuss specifics of the iterative development process.

Software_7

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/t/trackback/37578/2095284

Listed below are links to weblogs that reference How to Produce Good Software, Part 7:

» How to Produce Good Software, Part 8 from frankroast
Ping Back来自:blog.csdn.net [Read More]

» How to produce Good Software -(Part. 3) from frankroast
Ping Back来自:blog.csdn.net [Read More]

» How to produce Good Software -(Part. 3) from frankroast
Ping Back来自:blog.csdn.net [Read More]

» Enterprise Architecture and Anti-metaphors from Thought Leadership
David Snowden came up with several anti-metaphors that highly applicable to enterprise architecture. In my travels, I have found that good ole American's understand analogies pretty well but that they don't translate well to folks from India and Chin... [Read More]

Comments

I look forward to the obligatory debate about coding standards :-)

Hi Graham! Just thinking through the work streams of the MSF and RUP, the obvious things missing from your lists are requirements and architecture. I would love to hear your specific thoughts on how that fits in and how your views differ from the traditional idea of a whiteboard architect or an architecture-first practice. Also, how do you balance requirements gathering activities so you don't get analysis paralysis yet think ahead enough that you don't iterate forever, slowly arriving at what could have been easily conceived in a top-down mode of thinking?

Can you also cover any collaboration tools you use, e.g. wiki, etc.

Thanks.

Duke

Hi Duke,

Thanks for your suggestion! I've added "collaboration tools" to my list of topics to cover.

Cheers,
Graham

Post a comment

Comments are moderated, and will not appear on this weblog until the author has approved them.

If you have a TypeKey or TypePad account, please Sign In

Destiny

  • Destiny is my science fiction movie about the future of humanity. It's an epic, similar in breadth and scope to 2001: A Space Odyssey.

    To see the 18 minute video, click on the graphic below.

    Destiny17small

People