Abstract
AbstractThere are numerous examples of system developments which have not been entirely successful based on cost, schedule, and technical criteria. Many development problems have been traced to poor system requirements. This research introduces a user‐centered system development model which begins with user participation during the requirements elicitation phase. The Facilitator Assisted Requirements Elicitation (FARE) method is introduced, in which a technical facilitator acts as a neutral third party who bases discussion of requirements on concepts of operations (CONOPS) and use‐cases. User involvement continues throughout the system development lifecycle via participation in Integrated Product Teams, design reviews, and human‐machine interface reviews. End‐users take ownership of the System Requirements Specification (SRS); the system design; validation, transition, and training plans; and ultimately the delivered system.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
