THE SDLC WATERFALL Planning: Quality assurance plan, Configuration management plan, project plan & schedule.

The outputs of the project planning stage are the configuration management plan, the quality assurance plan, and the project plan and schedule. Requirement elicitation: The goals that were defined in planning stage will be taken as input and Each goal will be refined into a set of one or more requirements. Who is going to use the system? How will they use the system? What data should be input into the system? What data should be output by the system? This produces a nice big list of functionality that the system should provide, which describes functions the system should perform, what data is stored and used by the system The outputs of the requirements definition stage include the requirements document, the RTM, and an updated project plan. Design stage: The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced. Generally include functional hierarchy diagrams; screen layout diagrams business process diagrams, pseudo code, entity-relationship diagram. Programmers may develop the software with minimal additional input. The outputs of the design stage are the design document, an updated RTM, and an updated project plan. Development stage: The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include menus, dialogs, data management forms, data reporting formats, Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software.

Integration & Testing: At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite confirms a robust and complete migration capability. The outputs of the integration and test stage include an integrated set of software, an online help system, an implementation map, a production initiation plan that describes reference data and production users, an acceptance plan which contains the final suite of test cases, and an updated project plan. Installation & Acceptance stage: At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite is a prerequisite to acceptance of the software by the customer. After customer personnel have verified that the initial production data load is correct and the test suite has been executed with satisfactory results, the customer formally accepts the delivery of the software. Advantages y Simple and easy to use. y Phases are processed and completed one at a time y Works well for smaller projects where requirements are very well understood. Disadvantages y y y y y Adjusting scope during the life cycle can kill a project . High amounts of risk . Poor model for complex and object-oriented projects. Poor model for long and ongoing projects Poor model where requirements are at a moderate to high risk of changing.

SPIRAL LIFECYCLE

The spiral model starts with an initial pass through a standard waterfall lifecycle, using a subset of the total requirements to develop a robust prototype. After an evaluation period, the cycle is initiated again, adding new functionality and releasing the next prototype. This process continues, with the prototype becoming larger and larger with each iteration. Hence, the spiral.

V-Shaped life cycle model:

Integration Testing : Testing of more than one (tested) unit together to determine if they function correctly. ensuring the correct flow of data from the first through the final component. Done by developers/designers and testers in collaboration Also called Interface Testing or Assembly Testing.

System testing : Testing the system as a whole - Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system. Ensures that system meets all functional and business requirements.

What is Regression Software Testing? Regression means retesting the unchanged parts of the application. Test cases are re-executed in order to check whether previous functionality of application is working fine and new changes have not introduced any new bugs.

Acceptance testing: (UAT) To determine whether a system satisfies its acceptance criteria and business requirements or not. Done by real business users. Also called as Beta Testing, Application Testing or End User Testing.

Some Important questions BuG, Defect and Error : Error:Which comes at the time of development. Bug:Which comes at the time of testing(Pre-Release) Defect:Which comes in Production or when client doing the system testing(Post-Release).