S/w LC

S/w LC

1. Models

   • Iterative increm Devep model
     • Iterative -incremental dev is the process of establishing requ, design, build & test a system in a series of short development cycles
     • prototyping, (RAD), (RUP) and agile development models.
     • An incre, added to others dev previously, forms a growing partial system, which should also be tested
   • V -model
     • Compo (unit ) test ,Integration test, Syst test, Acceptance test

2. Compo Testing

   • Test basis
     • Component requirements
     • Detailed design
     • code
   • test objects
     • Com ponents
     • Prog rams
     • DB modules
     • Data conver / mig prog
   • Comp test (unit, module or program test) searches for defects in, and verifies the functioning of, software mod, prog, objects, classes, etc., It may be done in isolation from the rest of the system, depending on the context of the dev life cycle and the system
   • Component test may include test of function and specific non-functi characteris tics, such as resource-behavior (e.g., searching fo r memory le aks) or robu stness test, as well as structura l test(e. g., decision c overage). TC derived from work prod ucts such as a spec of the compo, the s/W design or the data model.
   • One app roach to component test is to prepare and automate TC before cod. This is test-first app roach or test-driven development. its highly iterative and is based on cycles of developing TC, then build & integratin g small pieces of code, and executing the compo tests correcting any issues and iterating until they pass.

3. Int Test

   • Test Basis
     • S/w & system design
     • Architecture
     • Workflow
     • Use case
   • Test objects
     • Subsystems
     • DB implementation
     • Infra structure
     • Interface
   • Systematic integ strategies may be based on the system architet (such as top-down and bottom-up), functional tasks, transaction processing sequences, or so me other aspect of the s ystem or components. In order to ease fault isolation and detect defects early, integration should normally be incremental rather than “big bang”.

4. System Test

   • Test basis
     • System & s/w req spec
     • Use cases
     • Funct spec,Risk anays rep
   • Test objects
     • System, user and operation manuals
     • System config and config data
   • System test include tests on risks / requ spec, business processes, use cases, or other high level text descripmodels of system behav, interactions with the operating sy stem, and syste res

5. Accept Test

   • Test basis
     • User requ
     • System requ
     • Use cases,Business processes
     • Risk analysis reports
   • test objects
     • Business processes on fully integrated s ystem
     • User procedures
     • Forms,Report
     • Configuration data
     • Operational and maintenance processes
   • A COTS S/w product may be acceptance tested when it is installed or integrated o Acc eptance testing of the usability of a component may be done during component testing o Acc eptance testing of a new functional enhancement may come before syste m testing