Defining the requirements is the first, and most critical, step in software system development. If the requirements are done well, the software design flows logically and smoothly. Conversely, if the requirements are done poorly, the resulting design is awkward and the coding is more difficult. Usually, errors identified in the requirements stage are the fastest and least expensive to correct, while those found in later stages (due to poor requirements) are increasingly more time-consuming and expensive to correct. This workshop presents both formal and field-tested approaches to defining requirements, including current standards, proper specification documents, object-oriented approaches, real-time considerations, and requirements automation.
This workshop is intended for systems engineers, software engineers, programmers, analysts, and staff members involved in requirements definition.
Requirements Engineering: A Good Practice Guide by Ian Sommerville & Aan Sommerville, with Pete Sawyer, John Wiley & Sons (1997).
$250 per participant (based on 20 participants)
We hope you found what you needed on this page. If you have
any questions or comments, please contact me.
Howard J. Bender, Ph.D.
President
The Education Process Improvement Center, Inc.
P.O. Box 186
Riverdale, Maryland 20738
hjbender@epicent.com