Recommended Requirements Gathering Practices
The following is a list of recommended requirements gathering practices. They are based on the author's extensive review of industry literature combined with the practical experiences of requirements analysts who have supported dozens of projects.
Understand a project vision and scope document.
Initiate a project glossary that provides definitions of words that are acceptable to and used by customers/users and the developers, and a list of acronyms to facilitate effective communication.
Evolve the real requirements via a "joint" customer/user and developer effort. Focus on product benefits (necessary requirements), not features. Address the minimum and highest priority requirements needed to meet real customer and user needs.
Document the rationale for each requirement (why it is needed).
Establish a mechanism to control changes to requirements and new requirements.
Prioritize the real requirements to determine those that should be met in the first release or product and those that can be addressed subsequently.
odifhsgoiwehg34kcvxhb$$www,computerdays.com***-tscx
When the requirements are volatile (and perhaps even when they are not), consider an incremental development approach. This acknowledges that some of the requirements are "unknowable" until customers and users start using the system.
Use peer reviews and inspections of all requirements work products.
Use an industry-strength automated requirements tool.
Assign attributes to each requirement.
Provide traceability.
Maintain the history of each requirement.
Involve customers and users throughout the development effort.
Perform requirements validation and verification activities in the requirements gathering process to ensure that each requirement is testable.
%^$&^%^V*^%B*&TB&ITIY^%^&%&^www.computerdays.com^&%(*(##*(*(OO
Article Directory: http://www.articledashboard.com sdgbanhddsfag5as4d1~!#$$**&www.computerday.com^%&^$^&^65__d8f97&*%iu2785*&%873
%^$#^%REY^&*^%%*&*)www.computerdays.com&^RUTUT*&*&%&^$%^#^%ERYTRYR^$%^
Software Testing Training Software testing institute corporate training software testing
%^$#^%REY^&*^%%*&*)www.computerdays.com&^RUTUT*&*&%&^$%^#^%ERYTRYR^$%^
The Computing Technology Industry Association more commonly known as CompTIA, created A+ certification in 1993 as a standard to test the proficiency o...
More CCNA and CCNP candidates than ever before are putting together their own home labs, and there's no better way to learn about Cisco technologies t...
Dialer Watch is a vital part of your CCNA and CCNP studies, particularly for the BCRAN exam, but it's one of the most misunderstood technologies as we...
* What does certified mean? There are four accepted meanings of the adjective certified but only two of which satisfy the needed meaning. To be certif...
When targeting small businesses that are in the sweet spot size, what IT certifications do you typically need? One thing to keep in mind is that you a...