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

System Life Cycle

description
by

Hayley Barker

on 10 March 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of System Life Cycle

Define the problem Feasibility Study Systems Analys s Requirement Specification Desgin Solution Building Testing Implimentation Documentation Evaluation Maintanance System Life Cycle The scope of the problem (how big the problem is)

Also this is when the customer and the analyst figure out exactly what the problem is, so that it can be solved efficiently.

THIS IS THE MOST IMPORTANT STAGE....
Feasibility basically means is there a solution that is possible?

Is the technology avaliable?

Is it economically possible?

Are there people who can work the system once built?

Can anyone be trained if not?

Are there many benefits? For example. Do you make more of a profit by having the system in place? Once the information has been collected it must be analysed to see what is useful and what isnt. This results in a requirement specification. The specification is basically what is going to put into the project and what isnt. Diagrams will be used DFD's, FD, algortihms and pseudo code. This is so that the customer is able to understand all the infromation that the analyst is giving them. Building is when the project is created, so in a sense creation : )

This is where the analsyt creates the project for the customer, its as simple as that... This is simply to come up with a solution to the problem. The analyst 'designs a solution' and shows it to the customer, to see if they approve of the solution, and if they can cover the cost etc..

Mostly an analyst will come up with a few alternative ideas for the customer to pick from, ranging in price etc.. This is the crucial stage after the building, due to the fact that you cant just create and build a solution and then not test it.

Testing is simply, when the solution is implimented, the analyst must test the solution using these testing ideas:
Alpha
Beta
White box
Black box

Once all of these, or at least most of these testing examples have been used, then the analyst can evaluate the solution that they have created. Implimentation is where the solution is installed within the shop or various place of work that it was designed for.

This can be done in a number of ways:
Direct installment
Phase installment
Parallel installment
Pilot installment

These are all different ways of placing the solution within the invironment for which it has been designed for. Depending on the users requests, any of these can be used. Maintanance is basically making sure that when someone else comes to update, change or simply fix the system that has been put into place, they will be able to see what has been done to the system and change it easily and quickly, without having to re write the whole project again. diagrams and written instructions so that people can understand what the analyst has been doing. evaluation is to make sure that all the objectives have beenmet and the requirement specification is completed.
when this is finished the analyst gets paid.
Full transcript