Home

Requirements

wpe1.jpg (4007 bytes)Requirements, Design, Architecture

[ List of Services ] [ Training, Seminars, and Mentoring ] [ Facilitation ] [ Requirements ] [ Infrastructure ]                                             

 

Requirements

The principle problem areas in the software development process are specifying and managing requirements. If these activities are not performed properly then the chances are that the solutions will be ineffective or just plain wrong. Clearly, improving the processes of discovering, documenting, and managing requirements are critical for the future business success of any enterprise.

The following points highlight the key steps for gathering requirements:

bulletproblem solving tools;
bulletproblem determination and definition;
bulletcapturing customer (stakeholder) requirements (use cases - eliciting requirements);
bulletconducting facilitated sessions (analyzing requirements);
bulletcontrolling scope and establishing agreement;
bullet developing application requirements (detailed specifications);  
bulletensuring traceability;
bulletconducting walkthroughs (validating requirements).

This benefits of the process provides an enterprise with an opportunity to:

bulletraise the quality of the requirements process;
bulletminimize risk of not solving the right problem(s);
bulletaggregate requirements;
bulletdevelop improved communications with client;
bulletmanage solution provider and client expectations;
bulletspot process improvement or reengineering opportunities.

Regardless of the 'promises' of the various contemporary methodologies (Unified Process, Agile, etc.), gathering and understanding the requirements is essential to success. Shortcutting or, worse, short-circuiting will certainly result in project failure. 

Send mail to smarcus@MarcusSoftwareDesigns.com with questions or comments about this web site.
Copyright © 1998-2006 Marcus Software Designs, Inc.
Last modified: July 14, 2006

[ News and Info ] [ Services ] [ Clients ]