|
Errors in the requirement phase are the most
costly errors in system development. How do analysts gather information
about requirements? How will that information be converted into user
functionality? To elicit and define user requirements, analysts must go
about their task in a methodical way. They must first understand their
roles and responsibilities. They must understand the development
lifecycle, from requirements through maintenance.
In this workshop,
participants will learn about a process to interview users and other
stakeholders to elicit business requirements. They will collaborate with
users and others to create a business requirements document (BRD). The
workshop includes data-gathering interviews, observation, surveys,
prototyping, process flow diagrams and tables, and requirement
walkthroughs.
Intended audience:
current and future business analysts, business systems analysts,
business operations analysts, requirements analysts, systems analysts.
|
