Software Best Practices

All, You may have noticed one short paragraph at the end of the call: using the term "non-functional." Although there is some precedent from many years ago when people didn't know any better, the adjective "non-functional" is abhorrently inappropriate. Nonfunctional is an actual...

[quote user="Earl Beede"] Hi Nick, Welcome to the Conversation! I fully agree with you. While I think this is right (and what I teach) does anybody do it? Do you do it regularly on your projects? If so, which methods do you use to get them? [/quote] Thank you, Earl, it's my pleasure to...

[quote user="Earl Beede"] Hi David, Welcome to the Conversation! Did you create those requirements ahead of time? That is, did you explicitly state them as goals at the beginning of the project or just experience them as quality requirements somewhere in the project, more interestingly, near...

These examples cover many different projects. All of these were created during Project Planning, ahead of time, and were explicity stated as goals. The telecom examples were defined for an entire product line of mobile phones, prior to work on any specific model. Each of the quality requirements had...

Yes, of course. Most quality requirements are not about defects. There' re only two I can think of: defect density and failure intensity. The quality requirements for which I've had to deal include notions of: Learn-ability, Port-ability, Maintain-ability, Documentation Use-ability; and in telecom...

The IEEE is currently requesting papers (sounds so academic) for a Software issues on quality. Their focus is on upfront quality (naming quality attributes, making sure they appear in the product. You can read more about it in a follow-on post. I am sorely tempted to try my hand at writing a paper (though...