(ref.doc)comp-0696

IEEE Computer
June 1996

p 8 Letters to the Editor
What's wrong with Java?
Answer by Ted Lewis

p 92 Software Challenges
Strategies for managing requirements creep
by Capers Jones

  Requirements change because software is expanding the ways companies
  operate. In a sense, creating software requirements is like hiking
  in a gradually lifting fog.
  Not all software applications have unstable requirements, but the
  majority do.

  JAD [Joint Application Design] is a method for developing
  requirements in which user representatives and development
  representatives work together with a facilitator to produce a joint
  requirement specification.
  Prototypes...
  RAD...
  Requirements Inspection
  Cost-per-function-point contracts...
  QFD [Quality Function Deployment] is a way to analyze requirements
  in terms of user quality needs.
  Change-control boards...
  Change- and configuration-management systems...

p 95 Object Technology (editor: Bertrand Meyer)
Gurus share insight on objects (Booch, Jacobson, Rumbaugh)

  The process we realize is important is one that is use-case driven,
  architecture centric, iterative and incremental.