SDLC

In Last session i explained about the Introduction of Software Testing. Today i'm going to explain
about the Difference between an "Error," "Bug" and "Defect" and "SDLC."

Error: The Developers identified the Errors.
Ex: Syntax Error, Logical Error, Runtime Error,...

Bug: Normally identified by the Tester. A deviation from the Expected result and the Actual
result.

Defect: Normally identified by the Client/Customer. An imperfection in the Product/Project.

Generally, Due to a human action("Error"), Bug was created. Due to the "Bug" the Product/Project
becomes "Defect". Due to this Defect, the Product/Project becomes "Failure/Fault".

What you mean by "Quality?"
Meeting the Clients/Customers requirements for First time and for every time. After the testing
part is completed, then only we can know the "Quality" of the Product/Project.


Now i'm going to say about "SDLC"(Software Development Life Cycle).

Before going to explain about this topic, i would like to say the example for this, so that u can
easily understand the topic. The best example for SDLC is "Butterfly Life Cycle". Everyone knows this life cycle, how the butterfly was grown from the egg to a beautiful butterfly. The
same concept is using in the SDLC also.

SDLC explains how the Product/Project is developed from Inspection through Completion. It has
Five Stages.
1. Requirement & Analysis.
2. Design/Architecture.
3. Coding/Developing.
4. Testing.
5. Delivery.

This is the Five main stages used in SDLC.

1. Requirement & Analysis:

Requirement: Collecting the ideas from the Client/Customer's as an input into a formal set of
documents.
Analysis: Analyzing the Clients/Customers system environment, so that the application will be
developed according to that system environment where the application should run successfully
without any failure.

2. Design/Architecture:

The Designer/Architecture will design the "Outlook" of the application. The output of this
stage is called "FDS"(Functional Design Specification) or "SRS"(System Requirement Specification).
This document contains the snapshots of the application and the fields details. This document will
be given to both Coding team and to the Testing team.
Ex: Fields means if the application is for an EMP records then the fields are Emp name,
textbox size, Designation like that the fields details will be given in the FDS or SRS.

3. Coding/Developing:

Using the FDS or SRS, the developer will develop the application. Once the coding part is
completed, the module or build will be "Unit Tested" and it will be move onto the Testing team.

4. Testing:

Once the FDS or SRS is completed, the Test Lead will prepare the Test Plan. The Test Engineer
start designing the Test Cases using the FDS or SRS. Once the Module or Build reaches the Testing
team, the Test Engineer starts to test the Module or the Build according to the Test Cases.

Once the Testing part is completed, the application will be moved onto the delivery section.

5. Delivery:

After the Testing part is completed successfully, the application will be delivered to the
Client/Customer.