Brian janz 1 1 part3 systemsdevelopment methodologies

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: g: –  System specifica6ons from design stage are translated into soOware program code –  SoOware may be purchased, leased, or outsourced instead •  Tes6ng –  To ensure system produces right results –  Unit tes6ng: Tests each program in system separately –  System tes6ng: Tests func6oning of system as a whole –  Acceptance tes6ng: Makes sure system is ready to be used in produc6on secng –  Test plan: All prepara6ons for series of tests •  A Sample Test Plan to Test a Record Change •  Produced by Dr. Brian Janz •  0 1 Systems Implementa6on (cont.) •  Conversion –  Process of changing from old system to new system –  Four main strategies •  Direct cutover, aka, “cold turkey” •  Parallel strategy •  Pilot strategy •  Phased approach •  End users role: Cri6cal –  Requires end‐user training –  Finaliza6on of detailed documenta6on showing how system works from technical and end‐user standpoint –  Users provide test scenarios, help formulate sensible...
View Full Document

This note was uploaded on 02/24/2011 for the course MIS 7650 taught by Professor Janz during the Spring '11 term at U. Memphis.

Ask a homework question - tutors are online