Requirements Document


This first meeting went excellently, and now the team has a better understanding of what MonkeyTongue is looking for in an expense report application. Vshift's first task will be to review the meeting notes and create a requirements document to deliver to MonkeyTongue. This document will formally describe everything that Vshift is planning to deliver to MonkeyTongue by the project due date. Vshift was careful to make sure the requirements document contained only attainable tasks, not ambiguous ideas.

graphics/02fig01e.gif

The tasks were compiled from the wish list created at the initial meeting; any issues the team thought were not attainable before the due date were left out. The document was then delivered to the MonkeyTongue CEO for him to sign and return to Vshift. This step ensures that the team understands everything MonkeyTongue expects to see in the application (if MonkeyTongue disagrees with the requirements document, the team will hear about it immediately rather than hearing about it after half of the development has been done incorrectly).

With the requirements document delivered, the Vshift team is now ready to plan the application. The next chapter discusses this planning process in depth, including project plan, initial design ideas, technology decisions, and application architecture.



Reality Macromedia ColdFusion MX. Macromedia Flash MX Integration
Reality Macromedia ColdFusion MX: Macromedia Flash MX Integration
ISBN: 0321125150
EAN: 2147483647
Year: 2002
Pages: 114

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