Page 119 - DCAP308_OBJECT_ORIENTED_ANALYSIS_AND_DESIGN

Unit 9: Analysis and Design

Low Level Document contains information at a very low level. Notes

Example: Detailed Design of each house.
Design phase is itself sub-divided into sub-phases discussed below:
The first step is to determine how the output is to be produced and in what format.
Samples of the output (and input) are outlined.
Second, input data and master files (data base) have to be designed to generate the required
output. The operational (processing) phase are handled through program construction
and testing, including a list of the programs needed to meet the software objectives and
complete documentation.
Finally, details related to justification of the system and an estimate of the impact of the
software on the user are documented and evaluated before it is implemented.
4. Coding: In this phase the designs are translated into code. Computer programs are written
using a conventional programming language or an application generator. Programming
tools like Compilers, Interpreters, and Debuggers are helpful in generating and checking
the code. Different high level programming languages like C, C++, Pascal, and Java are
used for coding.

Did u know? With respect to the type of application, the right programming language is
chosen.
5. Implementation: The final stage of initial development is implementation where the
software is put into production and runs actual business.

In this phase, the organization configures and enables system security features, tests the
functionality of these features, installs or implements the system, and obtains a formal
authorization to operate the system.

!
Caution Design reviews and system tests should be performed before placing the system
into operation to ensure that it meets all required security specifications.

In addition, if new controls are added to the application or the support system, additional
acceptance tests of those new controls must be performed. This approach ensures that new
controls meet security specifications and do not conflict with or invalidate existing controls.

Notes The results of the design reviews and system tests should be fully documented,
updated as new reviews or tests are performed, and maintained in the organization’s
official records.

6. Maintenance: Change is inevitable. Software serving the user’s needs in the past may
become less useful or sometimes useless in the changed environment. User’s priorities,
changes in organizational requirements, or environmental factors may call for software
enhancements.

LOVELY PROFESSIONAL UNIVERSITY 113