SDLC Flashcards
Idea Creation
Investigate the market and form a hypothesis about the product. The outcome of this is a general concept of the product
Requirement formation
Development of PRD and limitations
Design
Software architecture
Technical specifications
UI Design
Development and testing
Code is written, testing carried out, corrections made based on feedback
Release
Software available to end user
Maintenance
Maintain functionality and fix bugs
Discontinuation
Sunset the app (no more support)
What does QA do in Idea Creation?
Grasp the concept of the product
Analyze the product logic
Help find issues with the logic
Make a list of user scenarios to test
QA Responsibilities During Requirement Formation
Analyze the requirements for completeness, consistency, and testability
Suggest Improvements to facilitate testing process
Starts compiling test docs
What Does QA do during design
Makes sure implementation matches original requirements
Continues working on test documentation
Starts designing tests cases for automation regarding app functionality
Starts estimating amount of testing required
What does QA do during Development and Testing
Complete test documents
Test the product
Take part in designing automated tests
Make final decision on whether functionality is ready and signs off on release
What does QA do during Product Release
Conducts regression, smoke, or sanity testing
Checks the product functions in production
Collects feedback from end users to find bugs that wen undetected (typically done in beta)
Retests bugs found in production after they have been reported as fixed
What does QA do during support
Process feedback from product users: replicates, verifies, and retests
Tests upgrades, bug fixes, and new features
Sequential Product Development Methodologies
Waterfall
V-Model
Spiral Model
Waterfall
Linear model where each phase of the process depends on the deliverables of the previous phase
When is waterfall used
When product requirements are set and unlikely to change in the near future
When the desired result is known in advance
When the product development can be broken down into sequential stages
Core Agile Ideas
Focus on responding to change, rather than just following a plan
Gather the project team and business owners on a daily basis, and keep in touch with customers regularly
Deliver working software as frequently as possible (weekly-monthly) shorter is better
Gather
SCRUM
Sprints (time boxed iterations)
Tangible goals for every sprint to deliver something
Sprint planning and retros
Sprint Planning
Team gathers to set goals for next sprint
Development and testing
Team works on product, development, testing, and release
Demonstration
Show completed work to stakeholders to get feedback.
Retrospective
Reflect on the sprint, note what can be done differently
What does QA do during Sprint Planning
Assess work and difficulty of work in their POV
