By bloid
via codeproject.com
Published: May 02 2007 / 07:21
If users get what they think they requested, and the features actually do what they are purported to do, then this feature-driven approach works fine. Users can justify upgrade purchases to their bosses based on waving the spec sheet and reiterating the vendor's promises of better performance and quality. From the vendor side, it works wonderfully. A new version of software with additional features typically opens up a fresh revenue stream, giving an existing product new life and making a substantial contribution to the vendor's bottom line. So, if the user is happy and the vendor is happy, what's the issue?
-
Using UI components in jQuery Mobile
-
Pinpointing a Static GC Root with SOS
-
video/presentation - Java EE 6 Programming: Immediate Productivity
-
Naming Conventions in JustCode
-
Limit your abstractions: Application Events–Proposed Solution #2–Cohesion
-
NetBSD 5.1.2 has just been released, and of course it runs on....
Add your comment
