User-centered requirements: the scenario-based engineering process
Developing today's complex systems requiresmorethan just good software engineering solutions. Many are faced with complex systems projects, incomplete or inaccurate requirements, canceled projects, or cost overruns, and have their systems' users in revolt and demanding more. Others want to build user-centric systems, but fear managing the process. This book describes an approach that brings the engineering process together with human performance engineering and business process reengineering. The result is a manageable user-centered process for gathering, analyzing, and evaluating requirements that can vastly improve the success rate in the development of medium-to-large size systems and applications. Unlike some texts that are primarily conceptual, this volume provides guidelines, "how-to" information, and examples, enabling the reader to quickly apply the process and techniques to accomplish the following goals: * define high quality requirements, * enhance productive clientinvolvement, * help clients maintain competitiveness, * ensure client buy-in and support throughout the process, * reduce missing functionality and corrections, and * improve user satisfaction with systems. This volume clearly details the role of user-centered requirements and knowledge acquisition within Scenario-Based Engineering Process (SEP) and identifies SEP products and artifacts. It assists project personnel in planning and managing effective requirements activities, including managing risks, avoiding common problems with requirements elicitation, organizing project participants and tools, and managing the logistics. Guidelines are provided for the following: selecting the right individual and group techniques to elicit scenarios and requirements from users; subject matter experts, or other shareholders; and ensuring engineers or analysts have the necessary skills.
What people are saying - Write a review
We haven't found any reviews in the usual places.
Engineering Activities and Artifacts
Planning and Managing Effective Requirements
Selecting the Right Techniques
10 other sections not shown
Other editions - View all
activities analyzed appropriate artifacts attributes brainstorming chapter cognitive task analysis communication complete components concept analysis concept maps conduct context critical success factors decision maker decision process tracing declarative knowledge define demonstration system depict describe determine diagrams discussion document domain model ensure episodic knowledge evaluation example expert facilitator feedback focus group follow-up format functions group sessions guidelines heuristics ideas identify initial interactive observation sessions involved knowledge acquisition McGraw & Harbison-Briggs mental models ments mind mapping nonverbal nonverbal communication organization output participants patient performers presented primary problem procedural knowledge process analysis process tracing session protocol prototype questions reference architecture refine represent representation requirements elicitation response Sample Scenario analysis scenarios screens selected session report shareholders solutions solve specific storyboards structured interview systems development tape task analysis tion understand users verbal videotape worksheet