Phase	Task	Example/Comment
User Acceptance Test	The customers run the system using their understanding of what the system is to do.	All types of data entry are allowed.
Move to Production	Do setup, movement of programs, and authorizations in the production system.	Typically involves converting data which must be carefully coordinated.
Maintenance	Make changes for errors, changing requirements, or legal statutes, as required to a system in production	Operations of the system - scheduled jobs, reports, etc. can also be considered maintaining the system.

 

Things to note:
   Not all staff have major roles in every phase of the SDLC. Eg. Programmers usually aren't involved in feasibility.
   Also each corporation has its own separate of job function, but the general phases must be completed.
   To skip a phase like high-level design is almost always extremely expensive, although the cost might not be seen until the difficulty of maintenance & support.
   Test data can be usefully varied through the SDLC. In High-Level Design, particular named test scenarios should be specified in words. In Detail Design and then in Code & Unit Test, further definition of values for the test scenarios will be developed. In System Test, the restriction on test data (scenarios) is relaxed. Broad spectrum of data from other systems must be handled.
   Note: the requirements usually do not capture the full aspect of the data to be handled. See above paragraph.