After 8 years in the software industry and software engineering research, one topics comes back over and over again: requirements engineering - or how to build the right software right?
That is, this “simple” process of understanding what the user wants and deriving a useful solution for that problem as well as building that solution in an efficient manner.
Traditional requirements engineering assumed that the more time you invest upfront, the better the specification (as collection of requirements) will get and thus the rest of the project is just about implementing this set of requirement.
However, as numerous projects in the industry showed this assumption might be flawed. The fact that software in an intangible good and that software vendors promise to be able to solve any given problem with their solutions does not really help either…
No comments:
Post a Comment