TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
-----Original Message-----
From: Rowena Hart [mailto:rhart -at- XCERT -dot- COM]
Sent: Thursday, April 22, 1999 10:14 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Fw: Writing Requirements Seminar [Vancouver, BC, Canada], May
6-7
>IN SEARCH OF EXCELLENT REQUIREMENTS with Karl Wiegers
>
>Thursday and Friday, May 6-7, 1999 (register by April 29)
>9:00 am - 4:30 pm
>SFU Harbour Centre, 515 W. Hastings St., Vancouver, BC
>Price SPC Members: $750+GST Non-members: $885+GST
>To register, call 604-662-8181, ext. 115 or enroll online at
>www.spc.ca/training/courses.
>
>*****************************************************
>Previous attendees' comments:
>
>"As always, Karl presents practical, understandable material that can
>be applied immediately."
>Roxanne Harms, Total Care Technologies Inc.
>
>"An excellent course full of proven tools, pragmatic methods and just
>enough theory to be useful."
>Ron Jasper, when with Chancery Software Ltd.
>*****************************************************
>
>Seminar Description
>
>Requirements form the foundation for all the software work
>that follows. Arriving at a shared vision of the product to be
>developed is one of the greatest challenges facing the
>software project team, and customer involvement is among
>the most critical factors in software quality. The objective of
>this seminar is to give attendees a tool kit of practices,
>reinforced with practice sessions and group discussions, that
>they can begin applying to improve the quality of the
>requirements development and requirements management
>processes in their organization.
>
>This seminar describes tested methods that can help any
>organization improve the way it elicits, analyzes, document
>verifies and manages software requirements. Characteristics
>of excellent requirements statement and requirements
>specifications are presented and used to evaluate some
>sample functional requirements. The seminar emphasizes
>several practical techniques:
>
>* customer involvement through a "project champion" model
>* the application of use cases for defining user needs and
> system functions
>* a simple model for prioritizing requirements
>* writing software requirements specifications using a standard
> template
>* construction of dialog maps to model user interfaces
>* the use of prototypes to clarify and refine user needs
>* the use of technical inspections to find requirements errors
>* use of a requirements traceability matrix to connect requirements
> to design elements, code, and tests.
>
>The basic concepts of requirements management are described, as are
>practical methods for managing changes to requirements. These
>techniques can reduce project risk by improving the quality and
>control of the software requirements, thereby increasing the
>likelihood of a successfully completed project.
>
>Audience
>
>This seminar will be useful for software engineers, managers,
>requirements analysts, and anyone else engaged in gathering,
>documenting, analyzing, or managing customer requirements for
>software applications.
>
>Seminar Format
>
>Blend of lecture, class discussion, group discussions on
>requirements problems and solutions, and practice sessions.
>Practice sessions give attendees some experience in working
>with use cases, drawing a dialog map, reviewing a
>requirements specification, writing good requirements, and
>writing an action plan to improve their group's requirements
>practices.
>
>Seminar Outline
>
>* Introduction to Requirements Engineering *
>- Introduction to seminar, objectives, participant expectations
>- Define three levels of software requirements: business, user,
> and functional
>- Describe characteristics of high-quality requirements
>- Requirements development vs. requirements management
>
>* Practice Session *
>- Small group discussions on requirements problems in their projects
>
>* Software Requirements Development *
>- Sources of requirements
>- Customer involvement in the requirements process: the project
> champion model
>- Gathering requirements through use cases
>- Practice session: identifying use cases for an airline
> reservation kiosk
>- Prioritizing requirements
>- Documenting requirements: the software requirements specification
>- Practice session and discussion: reviewing a portion of an SRS
>- Practice session: examining requirements for problems and
> rewriting them
>- Software quality attributes, including practice session to write
> some quality attributes
>- Modeling user interfaces with dialog maps
>- Practice session: drawing a dialog map from use cases
>- Reducing the expectation gap through prototyping
>- Requirements verification
>
>* The Capability Maturity Model for Software *
>- Intent and structure of CMM
>- Requirements and the CMM
>- Group discussion: barriers to process improvement
>
>* Software Requirements Management *
>- Requirements management goals and practices
>- Requirements traceability
>- Managing changes to requirements
>- Requirements change impact analysis
>- Requirements and software risk management
>- Requirements management tools
>
>* Practice Session *
>- Small group discussions on how to apply solutions to the
> requirements problems from the discussion in section II
>
>* Practice Session *
>- Writing a requirements process improvement action plan
>
>* Summary, Wrap-up, and Course Evaluations *
>
>Instructor - Karl Wiegers
>
>Karl E. Wiegers is Principal Consultant with Process Impact,
>a software process education and consulting company in Rochester,
>New York. Previously, he spent 18 years at Eastman Kodak Company,
>including positions as a photographic research scientist, software
>developer, software manager, and software process and quality
>improvement leader. Karl received a B.S. degree in chemistry from
>Boise State College, and M.S. and Ph.D. degrees in organic chemistry
>from the University of Illinois. He is a member of the IEEE, IEEE
>Computer Society, ASQ, and ACM. His interests include software
>requirements, software technical reviews and inspections, software
>process assessment and improvement, metrics, and software risk
>management.
>
>Karl is the author of the Jolt Productivity Award-winning book
>Creating a Software Engineering Culture (Dorset House, 1996),
>as well as more than 110 articles on many aspects of computing,
>chemistry, and military history. Karl is presently writing a book on
>software requirements to be published by Microsoft Press in 1999.
>He is a frequent speaker at software conferences and professional
>society meetings.
>
>Seminar Sponsor
>
>This seminar is presented by the Software Productivity Centre Inc.
>as part of its goals to help companies adopt the most effective and
>productive processes available for producing quality software.
>For information on the SPC and its seminars, consult our web site at:
>http://www.spc.ca.
>
>Cancellation Policy
>
>A full refund for cancellations received up to one week prior to the
>event (cut off Thursday, April 29, 1999). No refunds for cancellations
>received after this date. Replacements will be accepted upon
>notification.
>
