|
|
|
» When Telepathy Won’t Do: Requirements Engineering Key Practices
The software industry is exhibiting an increasing interest in requirements engineering — that is, understanding what you intend to build before you’re done building it. Despite the hype of "Internet time," companies across many business domains realize that time spent understanding the business problem is an excellent investment. Clients have told me they’re getting serious about requirements because the pain of having built poor products has simply become too great.
You can best achieve requirements success by applying established good practices on your projects. Figure 1 suggests a requirements development process framework with steps that incorporate the key practices described here. Thoughtfully tailor the practices to suit your project type, constraints, and organizational culture. Some highly exploratory or innovative projects can tolerate the excessive rework that results from informal requirements engineering. Most development efforts will benefit from a more deliberate and structured approach, though. Telepathy and clairvoyance rarely suffice.
Author: Karl Wiegers
Read More ...
| Comments |
Currently, there are no comments. Be the first to post one!
You must be logged in to post a comment. You can login here
|
|