1 / 7

A Level ICT Unit 5.6.3

A Level ICT Unit 5.6.3. Implementing CBIS’s. Support. Installing a new system is disruptive and the support program will need to be planned well in advance

sasha
Download Presentation

A Level ICT Unit 5.6.3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A Level ICT Unit 5.6.3 Implementing CBIS’s

  2. Support • Installing a new system is disruptive and the support program will need to be planned well in advance • Training. Needs and provision will need to be identified. All users must know how to use the new software. Also, appropriate documentation must be provided. • Training materials will help the user to use the system. • User manuals and references are designed for when the user is familiar with the basics of the system but need to look up an unfamiliar task or procedure they haven’t used for a while. On line help may support this. • Procedural documentation. Provides information about backup procedures, security controls and disaster management and recovery procedures.

  3. Support cont.. • Existing files or paper based systems must be transferred to the new system. It might be possible to use software to convert the existing records to the format needed by the new system. If the existing system is paper based, the data will have to be entered manually.

  4. System Review • This the process of observing how the system is operating and deciding whether the original performance specification is being met. • A system review will arise either if there are problems with the system or if it has been pre planned (regular time intervals). The latter is more advantageous, as improvements can be planned without having an immediate problem to solve. • Time planned reviews will be determined by the complexity of the system and how fast the needs of the organisation change. This could include • System needs to store more data • System needs to handle more customers • System needs to provide a faster response time

  5. System Review Cont.. • The system might not be cost effective • The system might not be able to use the latest telecommunication links. • Operating procedures might have changed, so the documentation is out of date. The system review will identify • Whether the system is still meeting performance targets • Potential problem areas so that modifications can be planned before problems develop At the end of the review an action plan identifying a course of action should be produced. This will lead to system maintenance or the system life cycle starting over again. (Extreme case!).

  6. Maintenance • Maintenance is needed when the system isn’t operating properly or efficiently in some way. It might be needed immediately or planned as a result of a system review. • Corrective maintenance is used when the system isn’t working correctly. This type of maintenance fixes bugs in the system. • Perfective maintenance makes the system work better. A procedure may be re-written, for example, reducing the computer response time. • Adaptive maintenance is used when the needs of the organisation have changed. For example, the organisation has expanded so that the system can store sufficient data. It will also be necessary if the organisation has changed the way it works.

  7. Maintenance cont.. • Maintenance can be disruptive. The system might need to be taken off line. This might not be possible. In this case, there might have to be two separate computer systems, each capable of handling all operations. • If one is taken off line for a while, the back up can take over all operations for a short time. • This also provides security against the complete failure of one system.

More Related