Understanding and articulating business requirements for automated
systems always has been the weakest link in systems development.
Up to 67 percent of maintenance and 40 percent of development
is wasted rework attributable to inadequately defined business
requirements. Too often developers proceed based on something
other than what the business people really need; and development
methodologies commonly focus mainly on the format for representing
requirements. This interactive workshop also emphasizes how
to discover content, why to build it and what it must do to
produce value for the customer/user. Using a real case, participants
practice discovering, understanding, and documenting clear and
complete business requirements that can speed development, reduce
maintenance, and delight customers.
* Role and importance of defining business
requirements accurately and completely.
* Distinctions between the user's (business) requirements
and the system's (design) requirements.
* How to gather data, spot the important things, and
interpret them meaningfully.
* Using the Problem Statement tool to define clearly
problems, causes, and real requirements.
* Formats for analyzing, documenting, and communicating
* Techniques and automated tools to manage requirements
changes and traceability
WHO SHOULD ATTEND: This course has been designed
for systems and business managers, project leaders, analysts, programmer
analysts, quality/testing professionals, and auditors responsible
for assuring business requirements are defined adequately.