Heinrich Krause

We don’t have enough information about this author to calculate their statistics. If you think this is an error let us know.
Learn More
Requirements represent essential input for software projects and, thus, need to be defined clearly. Unfortunately requirements often are not prioritised systematically. As a consequence, it is not determined in the early phases of a project which functions (or functional requirements) are going to be covered by which release. This paper suggests a technique(More)
  • 1