Manual Testing Basics
Introduction to Software Development Life Cycle (SDLC) and Fish Model fundamentals
What You'll Learn
Introduction to Software Development Life Cycle (SDLC) and Fish Model fundamentals
SDLC Fundamentals
- 7 phases of Software Development Life Cycle
- Role of Business Analysts and Testing teams
- Different deployment models (Waterfall, V, Agile)
Fish Model Deep Dive
- Graphical representation of SDLC
- BRS and SRS document creation process
- Complete requirement analysis workflow
Software Development Life Cycle (SDLC)
SDLC means Software Development Life Cycle with different phases:
1. Requirement Gathering
- • Business Analyst (BA) team is responsible to gather requirements from client
- • BA team creates BRS (Business Requirement Specification) documents
2. Analysis Requirement
- • Analysis Requirement is done by Business Analysts (BA)
- • Once analysis is done, BA team again creates SRS/FRS/CRD/PRD/Stories/Epic documents
Document Types:
- SRS: System (Software) Requirement Specification
- FRS: Functional Requirement Specification
- CRD: Client Requirement Documents
- PRD: Product Requirement Documents
3. Design Application/Software/Products
- • On the basis of SRS documents, Design team designs the application
- • Creates High Level Design and Low Level Design
4. Coding
- • Development team develops frontend and backend applications
- • Based on SRS documents
5. Testing
- • Testing team tests frontend (Manual Testing) and backend (API Testing, Database Testing)
- • Based on SRS documents
6. Deployment
- • Once Testing is done, deploy application to client environment
- • Follow deployment process models:
7. Maintenance
- • Add new features
- • Modify existing features
- • Remove features
Fish Model
Fish model is nothing but the graphical representation of SDLC Life cycle. There are different phases present in Fish Model.
1. Requirement Gathering
- • Business Analyst people gather the requirement from client
- • BA people create BRS documents (Business Requirement Specification)
- • BRS document defines the client requirement to be used as software development process
- • BRS document acts as bridge between client team and technical team
- • BRS is formal document which is created by BA on the basis of Requirement gathering
BRS Document Examples
| Client Requirement | BRS Document |
|---|---|
| Dual SIM | 1 Device contains 2 SIM |
| ATM | Withdraw amount, view balance, mini statement etc. |
| Login Functionality | Login using Admin role, and login using User role, login using Retailer Role |
2. Analysis the Requirement
- • BA people analyze the BRS documents and they create detailed documents as SRS/FRS/CRS/CRD/PRD/Stories/Epic
- • SRS document is developed on the basis of BRS documents
- • One BRS document contains multiple SRS documents
- • SRS document defines client requirement to be used and functional requirement to be developed as software
Important Note
Do you know SRS/FRS/CRS/CRD/PRD/Stories/Epic? Yes, without knowing the SRS documents, how is it possible to write the test cases or execute the test cases.
What are the different contents present in SRS/FRS/CRS/CRD/PRD/Stories/Epic?
SRS documents consist of:
i) Functional Requirements
Define what the application should contain
Example: Application contains username text box, password text box, login button, forgot link, and create account should be present
ii) Use Cases
Use Cases means define functionality in terms of input, process and output
iii) Functional Flow Diagram
Visual representation of processes and workflow
iv) Screenshots
BA team creates screenshots of the application using IDOC software or HTML code
v) High Level Design and Low Level Design
Architecture specifications and detailed design documents
Knowledge Check
Key Takeaways
SDLC Phases (7 Steps)
- Requirement Gathering: BA creates BRS documents
- Analysis: Create SRS/FRS/CRD/PRD documents
- Design: High Level + Low Level Design
- Coding: Frontend + Backend development
- Testing: Manual + API + Database testing
- Deployment: Waterfall (90 days), Agile (30 days)
- Maintenance: Add/modify/remove features
BRS Document Examples
- Dual SIM → 1 Device contains 2 SIM
- ATM → Withdraw, view balance, mini statement
- Login → Admin, User, Retailer role access
SRS Document Contents
- Functional Requirements: What app should contain
- Use Cases: Input → Process → Output format
- Functional Flow Diagram: Visual process representation
- Screenshots: UI mockups using IDOC/HTML
- HLD & LLD: Architecture specifications
Key Relationships
- BRS acts as bridge between client & technical team
- SRS developed based on BRS documents
- One BRS can contain multiple SRS documents
- Testing impossible without knowing SRS documents
💡 These SDLC and Fish Model concepts form the foundation for all testing activities. In Day 2, we will explore the remaining Fish Model phases and dive into Black Box Testing techniques.