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 313329
To read all comments associated with this story, please click here.
RE: Some Notes about the Post
by Larz on Wed 7th May 2008 19:56 UTC in reply to "Some Notes about the Post"
Member since:

I applaud any attempts at defining good software, rather than relying on peoples gut feelings about software. I also think that standards such as ISO 9126 are too limited, as they only deal with quality attributes directly related to the software (functional or non-functional requirements). There is clearly a need to extend such quality models. But I am still having some issues regarding your model (or list).

For most, it seems mostly like a generalized framework containing evaluation criterias. The evaluator picks whatever requirements that are important from the list and then evaluates the software against these requirements (based on appropriate metrics). A bit like ISO 9126.

At other times it makes some fairly specific (and a tad biased) assumptions the requirements of the end-user (and implicitly - what exactly is good software). As for something like "Good Software Management" - I think it's a mistake to evaluate software on the development methodology. "Program X is not developed with method Y - dump it".

I think the model is too much a mix between general quality attributes and personal opinions.

Reply Parent Score: 1