I had a client to whom I was sending a copy of my company's development methodology. Unfortunately, with more than a million files on the companies network here, I can't find the doc in question. However, I did find the nice image that accompanied the document.
I thought that I would do a 'reality check' against articles on software development at Wikipedia and I did not find quite what I was expecting. If our (relatively simple) take on what is actually done on software projects is not represented there, it makes me wonder.
FWIW, the diagram merely shows the flowchart (arrows, docs, decision diamonds, 'things', etc) of the following development cycle:
What is nice about the diagram is that it shows in a tidy way how these stages flow into one another both forward and back and shows the entire life-cycle from conception to system retirement. It also shows how (and why) it's possible (as happens) that a system could make it all the way to release into production and then almost immediately retired.
I wonder: how many other people like myself have been discouraged by such actions at Wikipedia? My time is limited and that article may now not see the light of day. That's a shame.
I would link to the offending pages, but unfortunately that appears to be considered bad practice at Wikipedia and might even get me banned (oh my)!
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!