Your SlideShare is downloading. ×
0
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Systems Life Cycle
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Systems Life Cycle

439

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
439
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
27
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Systems Life Cycle ICT GCSE
  • 2. Introduction <ul><li>Most businesses need a computerised system </li></ul><ul><li>It could be a system to keep track of students’ names and address </li></ul><ul><li>Or a system to allow customers to access their bank details online </li></ul><ul><li>There are various stages that a business must go through in order to implement a new system </li></ul>
  • 3. Stages
  • 4. Analysis <ul><li>The analysis phase is where you indentify the problem and come up with possible solutions </li></ul><ul><ul><li>A good place to start is to examine the existing system </li></ul></ul><ul><ul><li>What improvements need to be made? </li></ul></ul><ul><ul><li>A feasibility report is often produced </li></ul></ul><ul><ul><li>A requirement specification will be produced </li></ul></ul>
  • 5. Design <ul><li>The system must now be designed to meet the requirement specification </li></ul><ul><ul><li>Data preparation </li></ul></ul><ul><ul><li>Code design </li></ul></ul><ul><ul><li>File design </li></ul></ul><ul><ul><li>Hardware configuration </li></ul></ul><ul><ul><li>Software </li></ul></ul>
  • 6. Testing <ul><li>You need to check that the system meets all of the requirements set out </li></ul><ul><li>It needs to be thoroughly tested before t is introduced </li></ul><ul><li>The general principle of testing is to check that the system works properly with typical data, data at the limits of what is allowed, and data that is wrong </li></ul>
  • 7. Implementation <ul><li>Once the system has been testing it needs to be installed for the staff to use, there are three main methods to implement a new system: </li></ul><ul><ul><li>Direct </li></ul></ul><ul><ul><li>Phased </li></ul></ul><ul><ul><li>Parallel running </li></ul></ul>
  • 8. Documentation <ul><li>Documentation is very important and is split into two distinct types: </li></ul><ul><ul><li>User documentation </li></ul></ul><ul><ul><ul><li>People who use the system every day will need clear instructions on how to use it, but they don’t need to know how it works </li></ul></ul></ul><ul><ul><li>Technical documentation </li></ul></ul><ul><ul><ul><li>People responsible for maintaining the system do need to know how the system works </li></ul></ul></ul>
  • 9. Evaluation <ul><li>Once the new system is up and running it is important to evaluate it, two key questions are asked at this point: </li></ul><ul><ul><li>Does the finished system meet the specified requirements? </li></ul></ul><ul><ul><li>Does it carry out all required tasks properly? </li></ul></ul>

×