1 / 6

The Challenge of Requirements Elicitation

The Challenge of Requirements Elicitation. Barriers to Elicitation. The “yes, but” syndrome The “undiscovered ruins” syndrome The “user and the developer” syndrome. The “Yes, But” Syndrome.

rianna
Download Presentation

The Challenge of Requirements Elicitation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Challenge of Requirements Elicitation

  2. Barriers to Elicitation • The “yes, but” syndrome • The “undiscovered ruins” syndrome • The “user and the developer” syndrome

  3. The “Yes, But” Syndrome • Often users like what they see when evaluating the system, BUT they immediately identify additional features they would like, or things they would like changed. • Unlike mechanical devices software doesn’t become “real” to the users until it is finished. • Developers need to discover the “buts” early in the process.

  4. The “Undiscovered Ruins” Syndrome • How do you find requirements that no one has thought of? • The more you find, the more you know exist. • Making sure to talk to all stakeholders is one way to address this.

  5. The User and Developer Syndrome • Users and developers usually come from different worlds and speak different languages and have different backgrounds, motivations, and objectives. • Few developers have had any training in elicitation techniques

  6. The User and Developer Syndrome (Cont’d)

More Related