Linked by Thom Holwerda on Tue 6th May 2008 15:15 UTC, submitted by Shlomi Fish
Features, Office "Which parameters make software applications high-quality? And which parameters or methods, while desirable, are not directly 'quality'?" This is the question the author of this article asks himself. Most of his 'parameters' make a lot of sense, but be aware that the article is about what makes an open source program high quality, and not programs in general. This important bit is stated in the one-sentence 'abstract'.
Permalink for comment 313299
To read all comments associated with this story, please click here.
Many good points
by irbis on Wed 7th May 2008 18:11 UTC
irbis
Member since:
2005-07-08

Don't be so hard on the author just because he may not provide the ultimate most comprehensive list of requirements for every kind of quality software project out there... The article has many good points, too often forgotten and worth keeping in mind: like when it mentions good social engineering skills.

There's more to good open source software than just good quality open-source code. Social problems have caused many otherwise promising (open source) software projects to go astray.

The article is not trying to compete with a something like the ISO standard mentioned above: http://en.wikipedia.org/wiki/ISO_9126 It complements such a well-known but mostly only technical, code-related list of requirements by offering some extra points of view.

Reply Score: 2