S ys t e m li f e Cyc l e  

​
Mind Map
Analysis

• This is where the current system is looked at in detail in order to figure

out what changes need to be made to make the new system better than
the old one.
design

• Once there is a clear list of requirements for

the new system it is time to design how it will
look and work.
• The system analyst develops the
specifications that describe how the system
requirements, identified in the analysis phase,
will be met
• The analyst answers those questions,
sometimes proposing alternative solutions
through a design approach
 Testing

• System Developer and programmer:

• While testing, if they find out any bugs, they will fix it and retest it
until there is no bug
implementation
• Implementation just means to 'install' the system ready for use.
• Before the new system can be installed, there are a number of tasks
that must be
• completed.
• These are outlined in the table below:
• Staff training
• Transfer files from existing system to the new system
documentation

• System documentation
explains how the system was
created and also how to use
it.
• Two sets of documentation
are produced for a new
system, for the following
reasons:
• Technical documentation
• User documentation
Evaluation
• Why is it important to
evaluate a system?
• Systems are evaluated in
order to determine if:
• The system is doing the job it
was designed to do
• The system is working well
with minimum errors
• Staff can use the system
properly.