1. Requirement Analysis 2. System and Software Design 3. Implementation and unit Testing 4. Integration and System Testing 5. Operation and Maintenance

o Requirement are very well documented, clear and fixed. o Product definition is stable. o Technology is understood and is not dynamic. o There are no ambiguous requirements. o Ample resources with required expertise are available to support the product. o The project is short.

- This model is ideal for supporting less experienced project teams and project managers or project teams whose composition fluctuates. - An orderly sequence of development steps and design reviews help to ensure the quality, reliability, adequacy and maintainability of the developed software. - Progress of system development is measurable in this model. - It conserves resources also.

1. Objective Setting 2. Risk assessment and reduction 3. Development and Validation 4. Planning Phase

- When costs and risk evaluation is important. - For medium to high-risk projects - Long-term project commitment due to potential changes of economic priorities. - Users are unsure of their needs. - Requirements are complex. - New product line. - Significant changes are expected (research and exploration)

1. Integration Test Plan 2. Integration Test Cases 3. Integration Test Data

1. Big Bang 2. Top-Down Testing 3. Bottom-up Testing

- Preparation of realistic test data. - Processing the test data via new system - Checking results thereof

System Test Plan System Test Case

Categories

Types

Introduction

Types

Quality Assurance Testing:

User Acceptance Testing:

New operating procedures should be clearly spelled out for final area staff such as those relating to, - data input - procedures - output, reports - internal control

Different Methods of conversion to new system. They are, - Direct Changeover - Parallel Conversion - Gradual Conversion - Modular Conversion - Distributed Conversion

a. Equipment Installation

b. Training Personnel

c. System Change-Over Strategies