home   services   products   faqs   resources   news   about   contact

 

Take a Moment
Help define the State of the Practice by answering the following question:

We actively manage our reqts risk --

always (100%)
usually (70-99%)
often (40-69%)
sometimes (20-39%)
rarely (1-19%)
never (0%)
don''t understand the question


[ Results | Polls ]


Votes: 80

Past surveys

· What is your primary USE for requirements? (Results - 281 votes)
· What is your primary form of automated support for requirements DEVELOPMENT? (Results - 252 votes)
· Who typically LEADS your requirements development? (Results - 356 votes)
· What is the typical number of STAKEHOLDERS involved in reqs. on your projects? (Results - 228 votes)
· What % of your projects have ALL reqs. stakeholders in ONE local area (building, city, or metroplex) (Results - 221 votes)
· Rate the AVERAGE EFFECTIVENESS of your reqs in meeting the info needs of mgrs, architects, & testers (Results - 225 votes)
· We include use cases in our system requirements (Results - 234 votes)
· We include a GLOSSARY in our system requirements (Results - 249 votes)
· For one of your typical projects, what % of the time is spent on requirements? (Results - 276 votes)
· What percent of your software defects have been traced to requirements problems? (Results - 204 votes)
· What form of automated support do you use for requirements MANAGEMENT? (Results - 205 votes)
· Do you DOCUMENT requirements interactions (e.g., usability conflicts with tight security)? (Results - 156 votes)
· Who typically WRITES your requirements specification? (Results - 281 votes)
· We formally review (e.g. inspections, walk-throughs) our reqs. specs -- (Results - 97 votes)
· We actively manage our reqts risk -- (Results - 80 votes)
 
Clearer Requirements   

top | home | site map | save as favorite | alert a friend | submit comments
satisfaction guarantee | privacy policy | terms & conditions