Who, What, and (currently) How

Tom Kelliher, CS 319

Sept. 22, 2000

Administrivia

And the winning hostname is...

Identify tasks for incorporation into master schedule.

I'd rather forget last time. Important lessons.

Continuation of intro. to requirements engineering.

Client (C. Surbeck, J. Dickens, E. Shmookler (informally)): Why we exist.
VP (Tom): becomes rich and famous.
Managers (Erica, Ed): Coordinate efforts within their respective departments. Set goals and monitor progress. Negotiate for resources. Create and revise schedules.
Product Planners (Amanda, Evan): work with client to produce requirements definition.
Requirements Engineers (Eric, Squirt): Working from requirements definition, produce requirements specification.
Architect (Jennifer): Working from requirements specification, produces architectural specification.
Software Engineers (John, Will): Working from architectural specification, design, implement, and configure system.
Technical Writers (Lisa, Stephanie): Produce user's manual, Installation guide, and maintenance guide.

VP signs-off on all documents.

Requirements Definition: Produced by product planners. Signed-off on by client, Development. Natural language document.
Requirements Specification: Produced by requirements engineers. Signed-off on by Marketing. Structured document.
Architectural Specification: Produced by architect. Signed-off on by requirements engineers. Structured document.
User's manual: Produced by technical writers. Signed-off on by marketing, software engineers. Natural language document.
Installation Guide: Produced by technical writers. Signed-off on by marketing, software engineers. Natural language document.
Maintenance Guide: Produced by technical writers. Signed-off on by marketing, software engineers. Natural language document.

Ed walks us through the current prospect/ambassador match process and gives Marketing ideas for consideration.

Thomas P. Kelliher
Thu Sep 21 14:51:22 EDT 2000