Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


System Life Cycle

No description

Aaron Winter

on 17 May 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of System Life Cycle

System Life Cycle
Problem Definition
Detailed definition of the problem
they are trying to solve Systems Analysis The systems Analysis uses a detailed study on the system
requirements and the existing system in place.

The systems analysis is also responsible for some of the
design work to go into the new system, having studied
the requirements of the new and the existing system. Feasibility Study A Feasibility study is an investigation carried out by the
Systems analyst to determine whether a new system is actually needed
The results of this study will finalise whethrer a new system is required. A feasibility study will involve:
Requirements analysis - what the new system needs to do
Technical report
Schedule report
Cost effective report
Budget Report
Analysis The systems analyst will study
the present system in detail, also will prompt
the users and the client of the buisness to find out what
exatly they want in the new system either by
Design Design elements
What data needs to be stored?
How is the data input?
Design of data validation
Processing - what type of processing needs to be performed on the data?
Batch or real time processing?
Types of output
Hardware and Software requirements.
Secruity of the data - how will it be kept secure? Teamwork People working together and coperating Data flow diagrams -External Entity



-Dataflow Example:
Changeover Three types of change over Direct changeover The old system is stopped and removed and is instantly replaced with the new system.
This can save money however, if the new system fails, your in deep trouble. Parrelel running This is when both systems are run together, this costs alot of money and alot of work has to be duplicated however, if the new system fails, , all is not lost because the old system is still there to be used. Piloting The new system is tested by a part of a company, and if all goes well it is them inplemented to the rest of the company.
Full transcript