SDLC -SOFTWARE LIFE CYCLE DEVELOPMENT

today we are discussed SDLC (software Life Cycle Development)
how its work and also

• Requirement Analysis gathering
• Analysis
• Planning
• Development
• Testing - STLC
• Deployment
• Operations and maintenance

1.Requirement Analysis:
Role play:Business Analyst
client to meet and gathering the application requirement.
writing the plain language its called BRD.
common man understand documentation the language no technical terms.
Once collect document after the walk though section.
Discuss with project manger.
planning the requirement resource,software,hardware,duration of the project,sign off project and how many months the development and testing environment.
which methodology follow now follow the only one agile methodology
form the team Agile methodology.
how many sprint done the first phase.

Design:
All requirement understand Design will start the UI/UX front-end design start. software architecture user interface will done quickly.
its the first phase of the project.

Development:
development team design finish the code will start.
development team work with dev environment.
once done first phase of the code change to the test environment

Testing:
Before that code receive testers work STLC model
Business analyst work same time will tester also work the same procedure this model:
Requirement analysis
Test planning
Test Design
Test Execution
sign off

Requirement analysis:
Understand the BR document
Clarification and doubts logs though session
identify test types to be performed
get application access

Test Planning:
preparation the test plan document for various of testing
test tool selection
Automation who will when will do
manual who will do when will do
resource planning

Test Design:
test scenarios,test case,automation script,RTM (requirement tracability matrix)
create test data
review the test case peer or lead
get approval

Test Execution:
execute the test cases as per the plan
Document test result and log defects for fail cases
track defects to closure
retest the defect fixes
Execution result defect log

Sign off:
evaluate the cycle completion
prepare test closure reports
test result analysis

Every phases the entry and exit criteria.

Defect life cycle (DLC):
once defect fix the it will automatically work
New:
when the defect the found the and posted for the first time
Assigned :
once defect posted the testing team will assign the dev team
open:
once the developer opens the bug and work on fix it
Fixed:
when developer fixed the bug with appropriate codes
Pending retest:
When the tester retesting the whether the bug it will be moved on the testing team
Retest:
when the retesting whether the bug raised was fixed or not.
Verified :
If the tester confirms the bug fixed
Reopen :
if the tester confirms that bug is not found the same defect again it will moved to assigned stage and flow continuous

Closed:once the tester verified the bug is fixed then defect raised will be closed
Duplicate:
if the bug is already by some one and if it is raised again will be duplicate.
Rejected/ Not a bug:
when the developer feels that the bug is not genuine.
Deferred:
This bug which developer feels that it can be fixed later the upcoming sprints.