Software Best Practices

[quote user="David Harper"]If your following scrum how about trying test driven development at the same time. So testing occurs before you implement any working code. That means writing tests and getting them to fail properly first. Then implement the code so that you start getting the tests...

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...

Hi Nick, Your process sounds close to Gilb's evo process. He scores designs instead of (or in addition to) practices but I bet he would really like your approach as well. You should share your stuff with him at tom@gilb.com . I had not thought deeply about how the methodology itself emphasizes some...

Hello Stan, Welcome to the Conversation! You are right, my question is slightly different than the Call. I figured that before I put a tremendous amount of effort in trying to write an article, I would check to see if doing non-functionals early is one of those things that, while correct and a good idea...

[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...

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 the end of the project?

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...