We need to define the term SDLC as Software Development Life Cycle, meaning how we are going to develop the software the acronym states each and everything in step by step.
Let’s start from the beginning the company receives queries about developing software from the client.
The company CEO or Senior Management, after receiving the query, tells the Project Manager to send potential candidates to the client in order to know the nuances (CRS and SRS) of the product.
Now the Project Manager sends Business Analyst (BA) to the customer place.
The duty of the BA is to note down all the requirements or detailed specs or CRS (customer requirement specification).
As you know they are smart enough to convert CRS into SRS and narrate the whole thing to the development team.
Here the development team comes into picture because they start developing the software after reading SRS.
Do you know after the development of the software they hand one copy of the software to the testing team?
You must be thinking why we need to bring the testing team for this activity; So now I would like tell you without testing team the company cannot get robust product.
The testing team installs the copy in the testing server and checks since they need to check all developed modules.
If they find the results are satisfactory, then they hand it to the development team.
They prepare a report and submit it to the development team in order to make sure that all modules are working fine and you can get ahead with the product.
Now the development lead or BA heads to the customer’s place in order to give illustration on the product.
After satisfaction the customer sends all his installation Engineer to their location in order to complete installation of the software.
But if the results are not satisfactory and the customer finds any bug in the product.
Then they inform the Project Manager that the product is not working as per the SRS.
The Project Manager hands it to the development team along with a defect report stating each and every defect of the software.
Let’s elaborate on the meaning of the features of the software.
Do you know these are (critical, major and minor) and after the first build if each and everything is fine then the development repeats the same process?
A brief History of Software Testing
In 1970 there were no Test engineers.
Hence the Software developer used to test the developed software i.e. developers were involved in testing.
When we deploy developers for testing there were some drawbacks;
- The developers utilize testing time to develop the software.
- Since the product is theirs, they rarely find bugs in their product.
- You can say this habit is overconfidence.
- They never try to break the product to find more bugs and defects.
In 1980 the companies hired Test engineers to test the software.
In these days software testing was done by the Test engineer.
What are the Models of SDLC?
- Waterfall Model
- Spiral Model
- V and V Model
- Proto-type Model
- Hybrid-Model
- Derived Model
- Agile Methodology
Let’s define the Stages of SDLC in brief
Requirement Collection or Planning
This is the stage where BA or Senior developer collects requirements from the customer since this is the stage where the team decides how to develop the software.
Study of the Requirement
In this stage the senior team performs thorough study on the product because they decide each and every nuance of the product development.
Design
This is the stage of SDLC Engineer performs Low level and high-level design
Coding
In this developer designs the code of the product.
Installation
In this stage we need to install software in the system after checking all the features.
Maintenance
This is the last stage in which we need to provide maintenance to the client pertaining to the developed product.
Now the Test Engineer tries to find out each and everything related to the product i.e.
- How much is the number of bugs in the product?
- In which of the features bugs are creating major issues?
- How did he find the bug?
- How much impact is the bug going to have on the customer business?
- Give some number to the defect report?
- And he will give it to the developer to fix the bug?
In real time for each bug, we need a separate defect report
- Developers read the defect report and after knowing the bug they start working on it.
- Developers open the source code which contains lots of programs.
- The developer opens the particular program and modifies the code and this we need to define it as fixing the bug.
- Source codes are nothing but software programs.
- After fixing the bug, the same copy of the software, we call it a modified copy or updated copy of the software.
- After fixing the bug the developer gives the updated copy to the test engineer.
- The test engineer uninstalls the first copy of the software and installs the updated copy on it for testing.
- The Test Engineer checks the same feature in order to check its robustness.
- When the Test Engineer finds there is no bug.
- Then they inform the development team that the product is working fine, this is called testing the bug.
- Now Test engineer will check the remaining features because. does fixing earlier bug created any problem in other features of the software or not.
- Re-testing the bug means testing the modified area of the software
- Developers always work in backend i.e. writing the code but Test engineer works on front end.
In real time software is technically called build.
Ist copy of the software is called Ist build
The 2nd copy of the software is called 2nd build
The 3rd copy of the software is called the 3rd build
One project contains many builds for each build we have one ID (identification) b01, b02, b03 and so on until the completion of the project.
To test (start and complete the testing) of one build/software in particular time duration is called test execution cycle or Test cycle.
One test cycle may take 5 days, 7 days, 15 days since it depends on the size of the project (number of features), complexity and number of test engineers.
One project contains many test cycles and many builds because it depends upon the size and complexity of the project.
Ans: -1. Requirement Collection or Planning 2. Study 3. Design 4. Coding 5. Installation and Maintenance
Wrapping Up
Since we defined each and every stuff related SDLC as far as possible your valuable feedback is a nectar to us.
Hence do comment and don’t forget to subscribe for the latest update.