|
|
|
|
|
by kazinator
3675 days ago
|
|
They try to prioritize their principles, but they are vague. Let's see: > Our highest priority is to satisfy the customer by building a non-linear, proactive, and self adaptive system Okay, firstly, what is that? And secondly, does it serve the customer if those are not the customer's requirements? What if I don't want a "self adaptive" system, whatever that is? It could be bad: self-adaptive software keeps some global state somewhere and doesn't quite ever do the same thing twice. If I require something that produces exactly the same output every time I feed it a given input, then I'm ill-served as a customer if I'm handed some self-adaptive contraption. |
|
A collection of popular buzz-words in contemporary software engineering research.
> And secondly, does it serve the customer if those are not the customer's requirements?
These are never any customer's requirements. Not a sane customer, at least. Instead, they are (conjectured, probably correctly, to be) generalizations of sufficiently many customers' requirements.
But you're correct -- most customers don't want or need any of those things (except non-linearity. But every piece of software everywhere has this spades.)