The Project Approach Strategy

---

The project approach strategy areas discussed in chapter 1 are summarized in table 3-1 below. Keep these strategy areas in mind as you formulate your solution to a programming project. The purpose of having a project approach strategy is to kick start the creative process and perpetuate your creative momentum. I remind you once again that you can tailor this approach strategy to suit your individual taste. Modify it in any way you see fit.

Table 3-1: Project Approach Strategy

Strategy Area	Explanation
Requirements	Determine and clarify exactly what purpose and features the finished project must have. Clarify your understanding of the requirements with your instructor if the project specification is not clear. The result of pursuing this strategy area should be a clear definition of what problem must be solved.
Problem Domain	Study the problem until you have a firm understanding of how to solve it. Optionally, express your understanding of the solution by writing a pseudocode algorithm that describes, step-by- step, how the problem can be solved. The result of this strategy area should be a high-level solution statement that can be translated into a detailed application design.
Language Features	Make a list of all the language features you must understand and use to draft a competent design and later implement your design. As you study each language feature check it off your list. Doing so will give you a sense of progress. The result of this strategy area should be a complete understanding of all C++ language features required to effect a good design and solve the problem.
Design (Plan)	Sketch out a rough application design. The design should address issues such as data structures, Input/Output, and how you plan to execute the problem solution you derived in the Problem Domain strategy area. The result of this strategy area will be a clear understanding of what source code should be written.

---