Group No.
Group Members (Name | Roll No. | Section | Role)
Institute Name
Department / Program (MCA)
Semester: MCA II Sem
Course Name: Software Testing
Assignment Title
Case Study Title
Selected Application Name
Faculty Name
Submission Date
1. A 10% deduction in marks will be applied if the student does not appear on the
scheduled review due date.
2. Font Type: Times New Roman, Font Size: 12, Line Spacing:1.15
1. Purpose / Objectives of the Assignment
Write 6–8 points:
Understand end-to-end software testing process
Apply testing across SDLC phases
Learn requirement-based testing and traceability
Practice static testing and review techniques
Design test cases using black-box and white-box thinking
Understand defect reporting and defect lifecycle
Prepare a test plan with metrics and risk handling
Improve teamwork, documentation, and ethical testing practices
2. Case Study Title
Write the exact title:
“Comprehensive Software Testing of a Real-World Application”
3. Selected Application (Case Study System)
Choose ONE:
Online Banking System
E-Commerce Application
University / LMS Portal
Hospital Management System
Travel Booking Application
Mobile Wallet / Payment App
Mention:
Why you selected this system
Target users
Key modules/features in the system
4. Requirement Analysis & Test Basis (Module 1)
Your group must:
4.1 Identify Requirements
Write minimum 8 Functional + 6 Non-Functional requirements.
4.2 Define Testing Scope
Mention:
In-scope modules
Out-of-scope modules
Assumptions and constraints
4.3 Defect Thinking
Explain:
Error vs defect vs failure (with one example from your system)
Possible root causes (requirement gap, design flaw, coding, environment)
5. Traceability Matrix (Mandatory)
Create a simple table:
Req ID Requirement Test Case IDs Test Type Status
Purpose: show end-to-end traceability between requirements and testing artifacts.
6. SDLC Model + Testing Across SDLC (Module 2)
Your group must:
6.1 Choose SDLC Model
Pick one:
Waterfall
Agile
V-Model
Spiral
Justify why it fits your application.
6.2 Map Testing to SDLC
Write phase-wise testing:
Requirement phase → review + test planning
Design phase → test design
Development phase → unit test
Integration → integration testing
Deployment → system + acceptance testing
Maintenance → regression testing
7. Test Levels + Test Types
Write clearly:
7.1 Test Levels (Mandatory)
Explain how your system will be tested at:
Component Testing
Integration Testing
System Testing
Acceptance Testing
7.2 Test Types (Minimum 8)
Classify and list:
Functional testing
Regression testing
Smoke testing
Sanity testing
Performance testing
Security testing
Usability testing
Compatibility testing
8. Static Testing & Reviews (Module 3)
Your group must perform ONE formal review of:
Requirement document OR
UI screen design OR
Test case document
Include:
Review roles (Author, Moderator, Reviewer, Scribe)
Review checklist
Defects found (minimum 8 review findings)
Summary: benefits and learning from static testing
9. Test Design Techniques + Test Cases (Module 4)
This is the most important section.
9.1 Black-Box Test Design
Write test cases using:
Equivalence Partitioning
Boundary Value Analysis
Decision Table Testing
State Transition Testing
9.2 White-Box Concepts (Conceptual)
Include:
Statement coverage
Branch coverage
Path testing (basic explanation)
9.3 Test Case Format (Mandatory Table)
Provide at least 15 test cases:
TC ID Scenario Steps Input Expected Output Priority
10. Test Plan + Defect Management (Module 5)
Your group must include:
10.1 Test Plan Contents
Test objectives
Test strategy
Test environment (browser/device/database)
Entry & exit criteria
Testing schedule
Effort estimation (days + roles)
10.2 Risks & Mitigation
Minimum 5 risks:
Requirement changes
Environment mismatch
Time shortage
Test data issues
Security gaps
10.3 Defect Lifecycle + Reporting Format
Create:
Defect lifecycle diagram (New → Assigned → Fixed → Retest → Closed)
Defect report table:
| Bug ID | Summary | Severity | Priority | Steps | Status |
11 Conclusion
Write:
What you tested
Major learning outcomes
Key defects and risk areas
Improvement suggestions
12. References (Minimum 5)
Examples:
ISTQB Foundation notes
Software Engineering textbook
Online testing documentation
Case study website/app screenshots
Tool documentation (JIRA, Selenium, Postman – optional)