An Introduction to Java and Program Design - Java Programming: Comprehensive Concepts and Techniques - page 11

The Program Development Cycle
Programmers do not sit down and start writing code right away. Instead, they
follow an organized plan, or methodology , that breaks the process into a series
of tasks. Just as there are many programming languages, there are many applica-
tion development methodologies. These different methodologies, however, tend
to be variations of what is called the program development cycle . The cycle
follows these six phases: (1) analyze the requirements, (2) design the solution,
(3) validate the design, (4) implement the design, (5) test the solution, and (6)
document the solution. Table 1-1 describes each phase that a programmer goes
through to arrive at a computer application. Figure 1-9 on the next page por-
trays the program development cycle as a continuing, iterative process or loop.
When the maintenance phase identifies change, or the program must meet new
requirements, a new iteration of the cycle begins again.

Table 1-1 The Program Development Cycle
PHASE

DESCRIPTION

1 Analyze the Precisely define the problem to be solved, verify

requirements that the requirements are complete, and write

program requirements and specifications —
descriptions of the program's inputs,
processing, outputs, and user interface.

2 Design the solution Develop a detailed, logical plan using tools such

as pseudocode, flowcharts, class diagrams, or
event diagrams to group the program's
activities into modules; devise a method of
solution or algorithm for each module; and test
the solution algorithms. Design the user
interface for the application, including input
areas, output areas, and other necessary
elements.

3 Validate the design Step through the solution design with test data.

Receive confirmation from the user that the
design solves the problem in a satisfactory
manner.

4 Implement the design Translate the design into an application

using a programming language or application
development tool by creating the user
interface and writing code; include internal
documentation (comments and remarks) within
the code that explains the purpose of the code
statements.

5 Test the solution Test the program, finding and correcting errors

(debugging) until it is error-free and contains
enough safeguards to ensure the desired
results. Implement the solution at the user level.

6 Document the solution Review and, if necessary, revise internal

documentation; formalize and complete user
(external) documentation.