Define Blastoff Objectives (Process Notes 1.1.1)


Define the deliverables to be produced by the blastoff. Examine the Project Intention and decide whether the blastoff is to produce:

  • Project Goals: This will always be produced.

  • Work Context Model: There may be an existing model that will provide a starting point for this project; otherwise, the blastoff must produce a new context model.

  • Identified Stakeholders: Always.

  • Anticipated Developers: Examine the kind of product wanted by the customer. Use previous project experience to determine the skills needed for this product. The anticipated developers is a list of the people and skills that are most likely to work on this project.

  • System Events: These, at some level, will always be delivered by the blastoff.

  • Event/Use Case Models: These are produced in a blastoff to prove the feasibility of the project. When the project is large and there are no dominant transactions, then there is little point in producing use case models during the blastoff. When the project has a few critical transactions, then preliminary use case/event models will be very helpful to determine whether the product can be built.

  • System Terminology: A preliminary terminology must be produced by the blastoff, unless there is a well-established standard terminology in use by the organization. For example, some industries have national or international standards for their terminology.

  • Scenario Models: These fall into the same situation as events/use cases.




Mastering the Requirements Process
Mastering the Requirements Process (2nd Edition)
ISBN: 0321419499
EAN: 2147483647
Year: 2006
Pages: 371

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net