Page 26 - DCAP205_DCAP409_ANALYSIS_AND_DESIGN_OF_INFORMATION_SYSTEMS
P. 26
Analysis & Design of Information Systems
Notes sub-phases, i.e., database design and program design. Database design is the most important
aspect of developing a new system. As data is the basic component or raw material of any
information system, it is needed to be stored in an organized way. How data has to be organized,
depends on the requirement specifications, hardware configurations and the features of
programming language and DBMS used. What is DBMS and how database can be organized
and managed?
Program design is mainly concerned with writing of programs (coding), editing of programs
using a text editor or word processor, debugging and finally testing them. There is generally a
team of programmers, who work under guidance of their project leader/systems analyst and do
all the codings.
Two method-dependent strategies for systems development can be recognized. The first strategy
depends on methodology; and the second on technique.
Did u know? Systems development is, basically, a problem-solving action. A problem in
an application domain is malformed by the systems development procedure into a solution
in the computer’s implementation field.
1.5.1 Unified Methodology Approach
Methodologies are a formal effort to address intricacy via the use of standard, conventional
strategies to systems development. Current methodologies are apt to concentrate on chiefly
one unit of disintegration, but they fluctuate on what that unit of disintegration is. Most
general methodologies base disintegration on either process or data, or some combination of
the two.
The procedure approach to managing intricacy is seen, for instance, in the structured techniques—
structured analysis, design, and coding. It is, possibly, the oldest and most broadly accessed
methodology, and also is the one most often referenced in the information systems concept. The
structured techniques all mainly utilize process decomposition, even though the seminal functions
on structured analysis also incorporated normalization of data as a secondary concentration of
the methodology.
The data approach to managing intricacy is observed in information engineering. It has its
origins in the entity relationship strategy to modeling data. Information engineering originally
employs data decomposition at the enterprise or organization stage to manage problem intricacy,
the motive being that an enterprise’s data is, in common, more steady than the processes accessed
to proceed on that data. After the preliminary data analysis, systems projects are produced by
means of process decomposition, which is, as a result, a secondary importance.
!
Caution The dissimilarity between process and data-oriented methodologies is one of
preliminary emphasis. So, ultimately, both orientations must be measured.
The object-oriented strategy to managing intricacy considers both data and procedure as a
package. An object is a constituent of the problem’s world, a consistent compilation of data
coupled with the procedures (methods or functions) acting on that data. The function of systems
development by means of the object-oriented approach interleaves analysis and design of objects
with analysis and design of the processes concerning to those objects. The foundation for the
object-oriented strategy is that application problems frequently develop around real-world
objects and the manners in which they interrelate.
20 LOVELY PROFESSIONAL UNIVERSITY