SDLC DevelopmentUnit Testing Phase ApproachSDL.DOCXVIP

SDLC Development/Unit Testing Phase Approach I. IntroductionThis approach document is designed for the University of Michigan Information and Technology Services System Development Life Cycle (SDLC) projects. A. Purpose The intent of Development/Unit Testing is to efficiently and accurately develop, unit test, and provide documentation for Designs produced. Repeatable, consistent processes and comprehensive documentation support this goal. The end result should be increased quality (fewer bugs), and the reduction of delivery time and effort needed for subsequent projects.II. Approach A. Approach DescriptionThe general methodology/approach for SDLC Development/Unit Testing at ITS will involve the following steps:Initial planning efforts for this phase will include the establishment of:A project status reporting approach.A defect tracking approach.A metric collection approach for the phase.(If New Hardware or Configuration) Perform SDLC Environment Setup Validation Process (9000)The guidelines for Development and Unit Test work will be:Eliminate Objects to be obsoleted. System Testing will be the only verification of success for these changes.For Objects with Design Documents (S300 – Design Document) the following steps are performed:Code the Design.Develop the Unit Test Plan.Review Code and Unit Test Plan if functionality has been added or changed.Unit Test the Coded Objects.Review and Approve the Unit Testing results.The order in which the Objects should be Developed and Unit-Tested will be based upon all of the following:Priority assigned.Grouping of all objects for a Business Process.Direction of the SDLC Lead or Project Manager.Ordering of System Testing and Acceptance activities.Ordering of Objects from Design Phase.Availability of Test Data.Steps involved in Coding are as follows:Review and understand the information in the S300 Design Document.Determine exactly which objects will need to be changed and update the S300 Design Document to include that i