Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

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.

DeleteCancel

The Systems Life Cycle

No description
by

Katherine Kamen

on 29 November 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of The Systems Life Cycle

The Systems Life Cycle Analysis During analysis, it is important to obtain accurate information about the organisation, in order to produce suitable software. There are several methods through which you can obtain this information.




Document Inspection: Examining the current output documents and the uses made of them can help determine the nature of the system being developed.
Observation: Design Implementation Testing Evaluation Questionnaire

Information gathered can be processed automatically. Questions need to be well designed and should not restrict the range of information that can be gathered. Interview

Interviews can be useful, although it is time consuming. Document Inspection
Examining the current output documents and the uses made of them can help determine the nature of the system being developed. Observation/Inspection

Observing the current system in order to find problems. A good design will be detailed enough to allow the implementation team to produce the system as intended.

System components that need to be specified include hardware, software, data files, user interface, required inputs, required outputs, manual procedures, and test plan. -Development of software by coding and testing.
-Installation of hardware.
-Installation of software.
-Preparation of data files.
-Training.
-Writing system documentation. The whole system needs to be tested before it goes live. -Does the new system meet its original objectives?
-How effective is the new system in solving the original problem?
-Can users operate the new system without making mistakes or working under stressful conditions?
Full transcript