Forgot your password?
New user?
Requirements Engineering Good Practices
Document Actions
Table 3-1 lists nearly 50 practices, grouped into seven categories, that can help most development teams do a better job on their requirements activities. Several of the practices contribute to more than one category, but each practice appears only once in the table. These practices aren't suitable for every situation, so use good judgment, common sense, and experience instead of ritualistically following a script. Note that not all of these items have been endorsed as industry best practices, which is why I've titled this chapter "Good Practices for Requirements Engineering," not "Best Practices." I doubt whether all of these practices will ever be systematically evaluated for this purpose. Nonetheless, many other practitioners and I have found these techniques to be effective (Sommerville and Sawyer 1997; Hofmann and Lehner 2001). Each practice is described briefly in this chapter, and references are provided to other chapters in this book or to other sources where you can learn more about the technique. The last section of this chapter suggests a requirements development process—a sequence of activities—that is suitable for most software projects.
|
Knowledge |
Requirements Management |
Project Management |
|---|---|---|
|
|
|
Requirements Development
|
Elicitation |
Analysis |
Specification |
Validation |
|---|---|---|---|
|
|
|
|
Back from the 3rd World Congress of Software Quality
