Do you always get your product out on time and within budget? Does it sell as well as you expected? If not, it may be in part because you aren't investing enough in developing customer requirements.
Doing effective requirements is a collaborative process with all those involved in all aspects of producing a product or service; including engineering, management, marketing, and product support. A foundation principle in requirements engineering is that everyone works with the same understanding of the problem to be solved. Requirements is not design specification, it's a structured approach for constructing a model of the problem your customers face.
Requirements need not be a formal process; a soft system approach using heuristic methods can be very effective. Doing requirements early in the life cycle can reduce the risk in a project, shorten the development time, focus a product's definition, and help get your customer's needs fulfilled.
To convey enough information about requirements techniques and to give you enough practice with them to allow you to start using them immediately. Ideally, participants will have already started, by using actual live projects in the course.
of intense training on State-of-the-Art requirements techniques, consisting of:
Covering reasoning why requirements are an effective strategy for improving quality and productivity. Includes an assessment of your current practices and how they fit into a requirements program.
Twelve heuristic approaches for developing information about your customers and their needs. Participants will get an introduction to the subjects of Users, Attributes, Functions, User Expectations, User Satisfaction, User Inclusion, Naming, Use Cases, Context Free Questions, Issues, Assumptions, and Design Choices.
Participants will develop actual requirements information in a guided set of sessions, one for each heuristic method.
A review the results of the heuristics, with an assessment of the risk remaining due to uncertainty and ambiguity. A strategy will be developed to make certain that the requirements information developed in the course will be reflected in your products.
5% Theory - 95% Practice. Heavy on the practical side -- so you can use it, but some theory so you know how to proceed when the rules don't seem to apply.
Those who influence design choices; Developers, Quality/Test Engineers, Project Managers, Program Managers, Marketing Specialists, Customer Support Representatives, Documentation Specialists.
Copyright © 1996 by Brian Lawrence. All Rights Reserved.
