Software process

A little rant due to frustration that I may add to if I remember:

• If you remove or comment out code someone else has added and they are still around, let them know what it is and why in case they needed it and they have to find out the hard way.
• If the build is broken, attempt to fix it. If you don't know anything about it the problem, find someone who does.

I worked for a company that implemented ISO 9001 while I was there. One of my projects was even used during the examination and I had to explain to the ISO 9001 rep how I used it.

After going through the ISO 9001 process, how do I feel about it? Personally, I think ISO 9001 is mainly a thing for advertising and provides very little in terms of your process.

From my project history and observations, here are some common problems I commonly see/hear about software development projects.

• Not keeping the requirements up to date.

  On some projects people get lax and it all becomes too hard to keep all the requirements up to date. This will cause even more problems further down the track when nobody can agree on what is meant to be delivered. It also makes it very hard to test a system if you don't know what the systems functionality is.

  Posted On: November 26, 2004 - 3:19pm by Rational
  ( categories: Software process )

Here are some sites that contain quality articles and content:

• The Server Side - Contains great articles, forums and reviews. Good source for pattern ideas.
• Martin Fowler - Martin Fowler is a smart fellow and manages to write his ideas in an easy to digest format. His website contains many great articles about OO including refactoring, patterns and methodologies.
• Agile Data - Scott Ambler's website containing a lot of useful articles, many referring to Agile methods.
  Posted On: August 4, 2004 - 8:04am by Rational
  ( categories: Software process )

There is such acronym overload in computing that I started this page so I could easily find them when I forget what they mean:

Programming

• XMI (XML Metadata Interchange) - A Format used by many CASE tools to write out UML models for data exchange. Whilst this is a "Standard", there appear to be different versions from vendors.
• POJO (Plain Old Java Objects) - Objects with just getters and setters, often used in domain modelling.

Software Process

• CRC (Class Responsibility Collaborator)
  
Posted On: August 4, 2004 - 7:23am by Rational
( categories: Software process )