Software Testing-Testing Tutorials,Initial Phase,Analysis Phase,Design Phase-Software Testing Life Cycles
  1. Home     
  2. About Us

  3. Introduction To Software Testing
  4. Software Test Plan
  5. Software Manual Testing
  6. Component Testing
  7. User Acceptance Testing(UAT)
  8. Software Automation Testing
  9. Software Testing Automation Tools
  10. Quality Assurance
  11. Software Testing-TestCases
  12. Software Testing Validation
  13. Software Testing Verification
  14. Software Testing Versioning
  15. Software Testing Development
    Life Cycle
  16. Glossary of Testing Terms
  17. Software Testing Interview Faq's
  18. Software Testing Books
  19. Software Testing Certification
  20. Software Testing Standards
  21. Software Testing Resumes
  22. Contact Us


etestinghub-Online Software Testing Tutorial-Manual and Automatic
 
Testing LifeCycles page and stages of life cycle pages are updated very clearly.Please check it.

Software Testing-Testing Life Cycles

Before going to the Testing Life Cycle in Software Testing,
we need to know how the software is developed and its Life Cycle in Software Testing.
The Software Development Life Cycle (SDLC) is also called as
the Product Development Life Cycle (PDLC) in Software Testing.

The SDLC in Software Testing has 6 phases:-
They are:-
a)Initial Phase in Software Testing
b)Analysis Phase in Software Testing
c)Design Phase in Software Testing
d)Coding Phase in Software Testing
e)Testing Phase in Software Testing
f)Delivery & Maintenance Phase in Software Testing

Now let Us discuss each phase in detail:--
a)Initial Phase in Software Testing:-
(i)Gathering the Requirements:-
The Business Analyst(BA) will gather the information of the company through one template which is predefined and goes to client.
He would collect all the information of what has to be developed and in how many days and all the basic requirements of the company.
For the proof of his collection of information the Business Analyst(BA) would prepare one document called as either
BDD in Software Testing:--Business Development Design
BRS in Software Testing:--Business Requirement Specification
URS in Software Testing:--User Requirement Specification
CRS in Software Testing:--Customer Requirement Specification
All are the same.

(ii)Discussing the Financial Terms and Conditions:--
The Engagement Manager(EM) would discuss all the Financial Matters.
Go to Top

b)Analysis Phase in Software Testing:-
In this phase the BDD document is taken as the input.
In this phase 4 steps are done.
(i)Analyse the requirements in Software Testing:-In this step all the requirements are analysed and studyed.
(ii)Feasibility Study in Software Testing:-Feasibility means the possibility of the project developing.
(iii)Deciding Technology in Software Testing:-Deciding which techonology has to be used for example:
Either to use the SUN or Microsoft Technology etc:
(iv)Estimation in Software Testing:-Estimating the resources.for example:-Time,Number of people etc:
During the Analysis Phase the Project Manager prepares the PROJECT PLAN.
The output document for this phase is the Software Requirements Specification(SRS).


And this document is prepared by Senior Analyst(SR).Go to Top

c)Design Phase in Software Testing:-
The designing will be in 2 levels:-
(i)High Level Designing in Software Testing:-In this level of Designing the project is divided into number of modules.
The High Level Designing is done by Technical Manager(TM) or Chief Architect(CA).
(ii)Low Level Designing in Software Testing:-In this level of Designing the modules are further divided into number of submodules.
The Low Level Designing is done by Team Lead(TL).
In this Phase the Cheif Architect would prepare the Technical Design Document or Detail Design Document.Go to Top



d)Coding Phase in Software Testing:-
In this Phase the Developers would write the Programs for the Project by following the Coding standards.
In this phase the Developers would prepare the Source Code.Go to Top

e)Testing Phase in Software Testing:-
1.In the first phase when the BDD is prepared the Test Engineer would study the document, and send a Review Report to Business Analyst(BA).
2.Review Report in Software Testing is nothing but a document prepared by the Test Engineer while studying the BDD document and the points which he cannot understand and not clear are written in that report and sent to BA.
3.And the Test Engineer would write the Test Cases of application.
4.In Manual Testing there would be upto 50% defect free and in Automation Testing it would be 93% defect free.
5.In this Phase Testing people document called as Defect Profile DocumentGo to Top

f)Delivery & Maintenance Phase in Software Testing:-
1.In this Phase after the project is done a mailis given to the client mentioning the completing of the project.
2.This is called as the Software Delivery Note.
3.The project is tested by client and is called as the User Acceptance Testing.
4.The project is installed in client environment and there testing is done called Port Testing in Software Testing
while installing if any problem occurrs the maintenance people would write the Deployment Document(DD) to Project Manager(PM).
5.After some time if client want to have some changes in the software and software changes are done by Maintenance.


More internal processes of the Software testing Life cycles are continued in the next page

Home |   Introduction to Testing |   Test Plan  | Manual Testing  | Automated Testing |   About Quality Assurance |   Contact Us   Sitemap  
© Copyright 2012 EtestingHub