System
Development Life Cycle is the stages of work performed by system
analysts and programmers in building information systems. Measures
used include:
1.
Conduct a survey and assess the feasibility of information system
development project
2.
Studying and analyzing the information systems that are running
3.
Determine the user requests information system
4.
Select the solution or solutions which are best
5.
Determine the hardware (hardware) and software (software)
6.
Designing a new information system
7.
Establish a new information system
8.
Communicate and implement new information systems
9.
Maintain and repair / improvement of a new information system if
necessary
System
Development Lyfe Cycle (SDLC) is the whole process of building the
system through several steps. There are several models of the SDLC.
The model is quite popular and widely used is the waterfall. Several
other models SDLC for example fountain, spiral, rapid, prototyping,
incremental, build and fix, and synchronize and Stabilize.
With
SDLC cycle, the process of building the system is divided into
several steps and on large systems, each step is done by different
teams.
In
an SDLC cycle, there are six steps. The number of steps in the SDLC
other references may be different, but in general are the same. The
move is
1.
Analysis of the system, which makes management of work flow analysis
ongoing
2.
Specification of system requirements, which do the details of what is
required in systems development and planning related to the project
system
3.
The design of the system, which makes the design work flow management
and design of programming required for the development of information
systems
4.
Development of the system, namely the stage of development of
information systems by writing the necessary programs
5.
Testing of the system, namely the testing of the system has been made
6.
Implementation and maintenance of the system, namely implement and
maintain a system that has been created
SDLC
cycle is executed sequentially, from the first step to the sixth
step. Every step has been completed should be re-examined, sometimes
together expert users, especially in step requirement specifications
and system design to ensure that steps have been done correctly and
according to expectations. If not, then steps need to be repeated
again or return to the previous step.
The
review in question is the nature of quality control testing, while
testing at the fifth step is quality assurance. Quality control is
done by internal personal teams to build quality, while quality
assurance is done by people outside the team to test the quality of
the system. All steps in the cycle must be documented. Good
documentation will facilitate the maintenance and enhancement of
system functions
Nice article :) This useful for me who always make a program :D
ReplyDelete