Java Reference
In-Depth Information
1. Analyze the Requirements
• Review program specifications
• Meet with analyst and users
• Identify program components
6. Document the Solution
• Review program code
• Review and revise internal
documentation
• Formalize and complete user
documentation
2. Design the Solution
• Group activities into modules
• Devise solution algorithms
• Design the user interface
Program Development
C ycle
3. Validate the Design
• Test the solution algorithm
with sample data
• Confirm with user that
solution meets requirements
5. Test the Solution
• Test program
• Find and correct any errors
4. Implement the Design
• Translate solution algorithms
into a programming language
• Enter program code into
computer
FIGURE 1-9
Program requirements drive the program development cycle. Requirements
often are identified by a program's users or a representative of the users when
they have a particular problem they believe can be solved by a computer pro-
gram. Users then submit a
requirements document
that lists the functions and
features that the program must provide. The requirements document usually
includes a statement of purpose for the requested program (also called a prob-
lem definition), the formulas the program must use, and an explanation of how
the program should respond to user interaction. Requirements also may specify
that a new program be developed or specify updates to an existing program. In
addition, requirements indicate how the program will be made available to users;
for example, requirements may specify that a stand-alone application must be
developed for the program, or they may specify that the program must function
over the Web.
Figure 1-10 shows an example of a requirements document. The document
specifies the requirements for a new program that must be made available
to users as both a console application and an applet. The program's main pur-
pose is to allow users to calculate shipping charges based on the weight of the
shipment.
Search WWH ::
Custom Search