Help shape GoConqr. What should we add next?

Flashcards

10.2 Installation

Cameron Taylor ICT - A Level A level English 24 cards

Cards in this deck (24)

  1. 1What are the changeover methods of introducing systems into an organisation?Direct Changeover
    Parallel Changeover
    Phased Conversion
    Pilot Conversion
  2. 2What is a Direct Changeover method?The most instantaneous way of replacing an old system to a new system. You close down the old system and restart and replace it with the new system.
  3. 3What are some advantages of a Direct Changeover method?This is the quickest of all the methods.
    This is the cheapest of all the methods.
    It allows the company to change the system when most convenient.
    Don't need to keep data duplicates.
  4. 4What are some disadvantages of a Direct Changeover method?If the system goes wrong there is no system to fall back on.
    Training is difficult as the system does not go live until it is used fully.
    It is the most stressful because the old system needs to be completely replaced with a new system.
    There is a period of time when neither systems are operational.
  5. 5What is a Parallel Changeover method?It is where you run both systems together simultaneously and after a while, the old system used is abandoned and all work is done using the new system.
    This method is used to minimise the risk when introducing a system into a company.
  6. 6What are some advantages of a Parallel Changeover method?If there are any problems with the new system then the old system can still be used.
    This is the method with the lowest risk.
    Staff can be trained on the new system, at their own pace.
    They can fall back on the old system if the new system stops working.
  7. 7What are some disadvantages of a Parallel Changeover method?This is a very expensive method as data usually has to be entered into both systems, requiring two sets of staff.
    Smaller systems may not be able to cope with one member of staff entering the data twice.
    It cost more money to run both systems simultaneously.
    The system can be out of sync with each other.
  8. 8What is a Phased Conversion method?This is when you phase the system into other organisations, one branch at a time. This can be weeks apart from each stage e.g. if the system works in one location then a few weeks later the organisation will release it to another company and so on.
    This can involve installing: hardware, software, rewire cables, changing layouts, modify the network infrastructure. All of these must be proved to be working effectively before releasing the system.
  9. 9What are some advantages of a Phased Conversion method?Much more efficient to control and stop the process.
    It is more effective to monitor the changeover and train staff using the pilot system.
    If the pilot fails then there is a low risk of losing data.
    Allows users to get to use the system overtime so, errors can be found earlier on rather than later.
  10. 10What are some disadvantages of a Phased Conversion method?The rollout is slow.
    Very complex as the organisation will be running two systems until full rollout.
    Some problems may only occur following full rollout and therefore are difficult to locate.
    It can be expensive to run as the system is introduced in stages.
  11. 11What is a Pilot Conversion?The system is brought in, in stages, or phases, until the whole system is implemented. You will only be able to distribute the system to different departments once the system is working perfectly.
  12. 12What are some advantages of a Pilot Conversion?A very structured method, allowing each phase to be fully evaluated before moving onto the next.
    Helps to reduce risks with the system in the long term because the system is evaluated early on and any errors are corrected before being implemented into the next branch.
    It allows the organisation to improve processes because the problems with the software can be fixed while the system is still online.
    One output of the pilot are graphical workflow charts that reveal how the software will be used to run the business. These workflows will be used to train the users.
  13. 13What are some disadvantages of a Pilot Conversion?The complete system cannot be evaluated until the last stage has been implemented.
    It can be complex integrating the old and the new system.
    The staff using the new system might not be able to efficiently share data with the rest of the company who are still on the old system
    Extra work for IT staff who are having to support two different systems.
  14. 14Why is Hardware installation and testing needed?Hardware needs to be installed and tested before the software is installed. Large systems are usually networked, so a large part of the time is spent setting up wireless networks and then testing them for efficiency and cable management etc.
  15. 15Why is Software installation and testing needed?Large systems often contain different servers located in different places so all the required software will need to be installed on each server.
    Software needs to be configured so that it works with the network and computers on the network. The data will be transferred into a database and file conversion utilities may be used to allow the new system to use the old data from different software. The system is then tested for functionality.
  16. 16Why is Documentation important?It is VERY important for any new software or system as it helps users use the system efficiently without any errors. Documentation needs both: written and diagrammatic evidence.
  17. 17What are the two types of Documentation?User documentation (User Guide) for the system
    Technical documentation
  18. 18What is User Documentation?This is a procedure manual (User Guide) on how to perform the necessary tasks within the system. This can include tutorials, reference to manuals and must be in the language the end user will understand, wirh NO JARGON.
  19. 19What is does User Documentation usually contain?Minimum hardware and software requirements
    How to load the software
    How to perform certain functions
    How to save
    How to print
    Frequently asked questions (FAQ)
    How to deal with error messages and troubleshooting
    How to back up data
  20. 20What is Technical Documentation?Technical documentation is produced to help systems analysts and programmers understand the technical workings of the system.
  21. 21What does Technical Documentation usually contain?Details of the hardware and software required for the system
    Details of data structures (data types, field names, etc.)
    Details of expected inputs
    Details of validation checks
    Details of how data is processed
    Diagrams showing how data moves through the system
    Flowcharts describing how the system works
  22. 22What is User Acceptance?This is done by the client in order to see whether the system is suitable to their needs and meets their expectations. It is judged on the original criteria that was set at the beginning once the system was first initially discussed and designed, these are known as “Milestones” which the developers must meet.
    The testing that is usually carried out is functional tests and usability (How efficient is the system to use) and how close to the real world the system is, users tend to do the tests after working hours so they must have a flexible working schedule.
  23. 23Why must the system be tested on the network?You have to make sure that the effect on the new system does not affect the network structure. You must use special testing when testing a network based system so, specialist engineers are needed to ensure that the network does not slow down the system.
  24. 24Why are resources important?Installation takes up different resources but the main cost is in terms of the human resource costs for training the staff that will be using the new system. This often means taking the staff away from their normal operational work and training them to use the new system.

Information

Description
A level ICT - A Level Flashcards on 10.2 Installation, created by Cameron Taylor on 01/06/2018.
Created by
Cameron Taylor
Views
0
Rating

More on System Implementation and Changeover

Feedback

What is it about?

What should we add next?