(responding to Jason etc.) ... Bell Labs (Jim Coplien?) have also been here before - here's a link I have to the relevant pattern. How do you evolve eithout...
The term "non-functional requirement" is sort of goofy. "Non-functional" == "doesn't work", and do you really want to implement requirements that don't work? ...
... The ability to handle, say, 1000 requests per hour is not a technical requirement; it's a business requirement. Try "performance requirement" or "system...
Hubert Matthews
hubert@...
Jan 1, 2006 3:19 pm
3086
... "Non-functional" == "doesn't work", and do you really want to implement requirements that don't work? ... process standards first starting using it, and...
(responding to Jason) ... Diversity, yes. However this is again not in conflict with lean-and-mean. What we want to do is pick a set of practices out of or...
I'm in. I hate the term "non-functional" for the same reason you state and the RUP's "Supplemental Specifications" is very unsatisfying. I like Technical...
Hi Scott! ... Yes - we need to be even more careful because tho the above was the initial focus of SixSigma it has evolved to include "tools" in its toolkit...
... I thought that "non-functioning" == "doesn't work" and that Non-functional simply meant not functional/behavioral in nature. Thus if one talks about "form,...
non-functional was a shortcut for non-functionalBehavior, i guess. *Technical Requirements* seems okay to me... things like: performance (do smth in < X...
I read something recently that referred to these as "quality of service requirements". Not a bad phrase. Regards, - Ted ________________________________ From:...
(responding to Pete) ... I have few complaints about automating work, and much praise for it. One of the few complaints I have is that I have several times had...
Not too surprisingly, I find the best way to approach the question of automating software development work is iteratively (with the exception of SCM and IDEs)....
This same argument can be applied to many things. Automation of builds, tests, code generation Refactoring Building for reuse (better objects/methods, better...
In a message dated 1/1/2006 4:27:02 P.M. Pacific Standard Time, bradpro@... writes: Two of business’ leading strategy thinkers argue that the only...
(responding to Steven G) ... Not too surprisingly, I am in complete agreement. Paul. =========================================================== Our e-mail...
... Call me weird - but I like just using "requirement" (or "story" ;-). No prefix. I've not found that categorising requirements buys me much. I'm interested...
Adrian Howard
adrianh@...
Jan 3, 2006 9:57 am
3101
The main use I have for the categorization is whether or not it makes sense to build an automated test for the story. It should be relatively easy to express...
ARCHITECTURE & DESIGN WORLD 2006 CALL FOR PAPERS IS NOW OPEN. Submissions will be accepted through February 5, 2006 Please use the following link to submit...
Well, there's an interesting issue as to whether "non-functional" requirements actually are requirements at all or not. In many cases, they are things that can...
While I mostly agre with this characterization, it's worth pointing out that purists would say that any performance concern is non-functional, even thought...
yes, i agree with what you write. This is about doing something more efficiently from the outset by writing a macro or something to speed up the manual stuff....
in some sense, you are right. all requirements are just that... requirements (features, user stories, blah) one reason to categorize might be to help...
I don't think "technical requirements" is an improvement - it's just as vague (are you suggesting that functional requirements aren't technical?). I'd prefer...
I think you could reasonably argue that mismanaged requirements (as opposed to unknowable requirements) are in fact "shoddy workmanship". If the requirements...
This post was a great reaffirmation that software development is largely a means to an end rather than an end in itself. However, the "New Year's Resolution"...
(responding to Jordan) ... It may not have been recognised as good practice at that time, but these days it is in many contexts good practice first to make it...