There are many tasks to complete before coding begins in a large project. The actual coding of the Library Project starts in Chapter 5. For this chapter, we will complete the project agreement document that describes the Library Project features.
This chapter does not include a Visual Studio project template that you can load and examine in Visual Studio. Instead, you must access the Chapter 3 subdirectory from the book's installation directory. This subdirectory contains three files:
This is the primary project document that identifies the features of the completed project. It is agreed upon by both the developer and user representatives. Deviation from this document occurs only through the "Change Order" process.
This file is used to modify the original project through the "Change Order" process. When using this document, include a description of the change to be made to the project, and any schedule and cost impact.
This file is used when the project is complete, and the user is ready to accept the finished product. This document combines the "Acceptance Criteria Testing" and "Project Acceptance" elements described earlier in the chapter.
Please feel free to use these documents to support your own projects. However, the legal team at O'Reilly Media would like to remind you that if you choose to use these documents, you're on your own, bucko. These documents are meant as examples only. You should talk to a lawyer in ...