Software Best Practices

Voices on Software Development Best Practices
Welcome to Software Best Practices Sign in | Join | Help
in Search

Browse by Tags

All Tags » Non-Functional (Quality) Requirements » Quality Attributes (RSS)
  • Re: IEEE Software Quality Article

    Yes, it has caused problems with customers. And, no, the term 'non-functional' is not a useful compliment to requirements about functions. As stated, requirements about 'objects' are in the set of all requirements that are not about functions, but to refer to them as "nonfunctional"...
    Posted to Forum by dblaine on 05-22-2007
  • Re: IEEE Software Quality Article

    [quote user="Earl Beede"] 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...
    Posted to Forum by Nick Kisialiou on 05-22-2007
  • Re: IEEE Software Quality Article

    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...
    Posted to Forum by dblaine on 05-21-2007
  • Re: IEEE Software Quality Article

    [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...
    Posted to Forum by Nick Kisialiou on 05-18-2007
  • Re: IEEE Software Quality Article

    [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...
    Posted to Forum by Nick Kisialiou on 05-18-2007
  • Re: IEEE Software Quality Article

    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...
    Posted to Forum by dblaine on 05-10-2007
  • Re: IEEE Software Quality Article

    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...
    Posted to Forum by dblaine on 05-10-2007
Page 1 of 1 (7 items)
Seminars           www.Construx.com           Consulting