Premium
4.3.1 Formalizing Informal Stakeholder Requirements Inputs
Author(s) -
Kitapci Hasan,
Boehm Barry W.,
Grünbacher Paul,
Halling Michael,
Biffl Stefan
Publication year - 2003
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2003.tb02631.x
Subject(s) - negotiation , computer science , stakeholder , requirements analysis , context (archaeology) , process (computing) , requirements elicitation , stakeholder engagement , requirements management , stakeholder analysis , system requirements specification , process management , knowledge management , software engineering , business , software , paleontology , public relations , political science , law , biology , programming language , operating system
Often, the stakeholders who can contribute the most value and realism to system requirements are the ones with the least time available to participate in the process. We have found the EasyWinWin requirement negotiation method and tools to be an effective way to involve such busy stakeholders. It avoids time‐consuming group wordsmithing, but results in relatively informal win‐win agreements (e.g., “24/7” or “anytime, anywhere” vs. more precise availability and accessibility requirements). For the past three years, we have been using EasyWinWin to capture informal requirements from stakeholders in an annual series of 15‐20 University of Southern California (USC) electronic services projects. In the context of these projects, we have been exploring alternative methods for formalizing these informal requirements inputs, including natural language processing, keyword analysis, template‐based refinement, formal methods expertise, and inspections. The paper summarizes our analysis of the relative strengths and difficulties of using these methods and our approach during the USC e‐services applications projects.