The project-approach strategy presented in chapter 1 is summarized in table 3-1. Keep the project-approach strategy in mind as you formulate your solution. Remember, the purpose of the project-approach strategy is to kick-start the creative process and sustain your creative momentum. Feel free to tailor the project-approach strategy to suit your needs.
Strategy Area | Explanation |
---|---|
Application 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. This results in a clear problem definition and a list of required project features. |
Problem Domain | Study the problem until you have a clear understanding of how to solve it. Optionally, express your understanding of the solution by writing a pseudocode algorithm that describes, step-by-step, how you will solve the problem. You may need to do this several times on large, complex projects. This results in a high-level solution statement that can be translated into an 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. Doi ng so will give you a sense of progress. This results in a notional understanding of the language features required to effect a good design and solve the problem. |
High-Level Design & Implementation Strategy | Sketch out a rough application design. A design is simply a statement, expressed through words, pictures, or both, of how you plan to implement the problem solution derived in the Problem Domain strategy area. This results in a plan of attack! |