A011 Atharv Kapoor B. Tech. IT.

Sem-7th

Software Testing
BTech IT
2025-26 Batch
PART A
(PART A : TO BE REFFERED BY STUDENTS)
A.1 Aim:
 To implement requirement testing for your project

A.2 Prerequisite:
Basic knowledge of Project topic

A.3 Outcome:
After successful completion of this experiment students will be able to
(a) To implement testing to further understand user requirements.

Theory :
Requirements testing also includes help in gathering and analysis of user data and their domain. This procedure is required to
research UI usability, creation of profiles, finalizing documentation and, on the whole, facilitates design process.

This procedure helps improve requirements quality and reduce the number of tests necessary to meet these requirements.

First of all, our QA team gathers and analyzes requirements to find out what technology will be used to build the project, who
this project is designed for and the project goal.

We also discover missing requirements to make sure the information we gathered is consistent, clear and covers every aspect
of software under development.

Then we create test cases on the basis of the requirement measurements and perform them to make sure that the system under
test operates in accordance with the set requirements.

For example, you’d like to have system response time of 2 seconds – that is your requirement measurement. All of such
requirement measurements are passed through tests and then evaluated.

We also take part in review meetings, and in case any new requirements appear or any changes are made to the set
requirements, we track them in an issue tracking system.

Finally, when all requirements are tested and the client is satisfied with the results and signs the requirements document, we
freeze the requirements for design phase.

A.4. Procedure:
Steps:
This type of testing covers testing of requirements specification that describes:
 project functionality
 user interface
 software and hardware interfaces
 performance criteria
 implementation issues and risks
 security and system correctness criteria
Following steps to be followed

Faculty-in-charge: Dr. Ruchi Kaushal , NMIMS

 A011 Atharv Kapoor B. Tech. IT. Sem-7th

Step 1:
 Discover Missing Requirement
 Check If the Requirements Are Related to The Project Goal
Step 2:
 Structure: What is it?

 Function: What does it do?

 Data: What does it process?

 Platform: What does it depend upon?

 Operations: How will it be used?

Step 3 : Checklist for each requirement

1. User story describes one part of the functionality.

2. User story has all the necessary information and doesn’t refer to other stories.

3. All entities and objects of the user story are clear and defined in this story.

4. The customer and programmer can co-create details during development.

5. User story captures the essence, not the details.

6. All items in the story are useful to the system user.

7. The functionality described in the story is user-friendly.

8. Tasks in a story have enough information to be estimated.

9. User story should be easily estimated or sized, so it can be properly prioritized.

10. User story can be fully implemented in one schedule (including testing).

11. User story isn’t too big to plan/task.

12. Acceptance criteria are accurate and unambiguous.

(PART - B)
(TO BE COMPLETED BY STUDENTS)

Faculty-in-charge: Dr. Ruchi Kaushal , NMIMS

 A011 Atharv Kapoor B. Tech. IT. Sem-7th

Roll.No.: A011 Name: Atharv Kapoor

Sem/Year: Semester 7th Date of Submission: 29-07-25
Date of Experiment: 29-07-25 Faculty: Dr. Ruchi Sharma

Aspect Details for Ultimate Travel Guide

Structure Web-based platform with backend APIs, database, and frontend UI layers. Contains modules for itinerary planning, booking
integration, real-time data aggregation, mapping services, and AI content generation.
Function Enables destination exploration, personalized itinerary creation, booking services integration, real-time travel updates, and interactive
map-based navigation.
Data Processes user preferences, destination info, booking details, real-time transport and pricing data, map data (OpenStreetMap +
Overpass), AI-generated summaries, and user-generated reviews/tips.
Platform Depends on Python backend (FastAPI), PostgreSQL DB, GraphQL Hasura, React JS frontend with Tailwind, Chakra UI & Bootstrap,
APIs (Amadeus), web scraping (Playwright), OpenStreetMap, AI tools (Gemini 2.5), and hosted on Oracle VPS.
Operations Users access via web browsers; use UI to search, filter trips, generate itineraries, book travel, view maps, get real-time updates;
backend services scrape data, update DB, process AI; schedules run via APScheduler.

B.1: Input and Output:

This type of testing covers testing of requirements specification that describes:

1. Project Functionality

 Destination Exploration: Users can search and explore destinations, access information about landmarks, culture, and food.
 Personalized Itinerary Planning: The platform generates customized itineraries using AI (Gemini 2.5), based on user
preferences, budgets, and duration.
 Booking Integration: Direct booking of flights, hotels, and car rentals via Amadeus API.
 Real-time Data: Aggregates current data on pricing, local events, transport, and availability by scraping and API feeds.
 Interactive Navigation: Offers dynamic maps (OpenStreetMap, Overpass API) with POI discovery.
 Collaborative Planning: Enables group travel and trip sharing with flexible itinerary co-creation.
 User Content: Collects and displays reviews, travel tips, and local insights.

2. Software and Hardware Interfaces

 Backend:
 Python (FastAPI) for REST API.
 PostgreSQL database managed through Hasura GraphQL engine.
 APScheduler and Playwright for regular data collection.
 Frontend:
 React JS for UI logic.
 Tailwind CSS, Chakra UI, Bootstrap for mobile-responsive, accessible visuals.
 External Services:
 Amadeus API (bookings), OpenStreetMap (maps), Overpass OSM (geo-data), WikiTravel (content), Gemini 2.5 (AI
itineraries/content).
 Hosting:
 Oracle VPS for scalable backend and database hosting.
 Hardware Interfaces:
 Cloud/Server hosting, users’ web browsers (no direct device dependencies).

3. Performance Criteria
 Expected Response Time:
 API endpoints should respond within 1–3s for common queries.
 Itinerary generation with AI should complete in under 10s.

Faculty-in-charge: Dr. Ruchi Kaushal , NMIMS

 A011 Atharv Kapoor B. Tech. IT. Sem-7th

 Scalability:
 Support for thousands of concurrent users, with seamless data updates.
 Reliability/Uptime:
 System hosted on scalable infrastructure, aiming for 99.9% uptime.
 Real-time Updates:
 Travel data refreshed at least hourly (or more for critical information).

4. Implementation Issues and Risks

 API/Data Dependencies:
 Reliance on external data sources (Amadeus, Wikitravel) presents availability and terms-of-service risks.
 Web Scraping Compliance:
 Risk of being blocked or rate-limited by external sites. Requires user-agent rotations and legal review.
 AI Content Quality:
 AI-generated itineraries must be validated for appropriateness and reliability.
 Data Privacy:
 Handling user information and preferences securely to comply with data protection standards.
 Integration Complexity:
 Ensuring smooth interoperation among diverse APIs, scraping modules, and live data feeds.
 User Support:
 Absence of always-available support may impact user retention and satisfaction.
5. Security and System Correctness Criteria
 Authentication and Authorization:
 Secure login with OAuth or similar for personal data and itinerary access.
 Data Encryption:
 All traffic over HTTPS; sensitive info encrypted at rest in PostgreSQL.
 Input Validation:
 All user inputs are validated server-side to prevent errors and attacks.
 Error Handling:
 Graceful error reporting for failed integrations or data fetches.
 System Integrity:
 Acceptance criteria for correctness include accurate itinerary generation, up-to-date booking information, and reliable
map/navigation tools.
6. Function
 Feature Set:
 Discovery, planning, booking, map navigation, local reviews, and group collaboration—each supported by clear user stories.
 Inputs/Outputs:
 Inputs: User searches, preferences, budget, and travel dates.
 Outputs: AI-enhanced itineraries, lists of POIs, booking confirmations, interactive maps.

User Story and Checklist Validation

1. Each story addresses a single function: search, plan, book, explore, collaborate.
2. Stories have sufficient context and do not refer ambiguously to others.
3. Entities (user, destination, POI, booking) are defined and clearly related.
4. Requirements allow developers and stakeholders to clarify and extend as needed.
5. User stories focus on what the user wants to accomplish, not technical details.
6. Each feature delivers direct value to travelers (e.g., saving time, personalization).
7. Emphasis on a user-friendly, accessible UI/UX.
8. Tasks for each feature can be estimated based on the scope (“Integrate Amadeus API,” “Implement AI itineraries”).
9. Stories are crafted to be independently prioritized and delivered.
10. Each user story can be completed within a defined sprint, plus associated testing.
11. Stories are sized for practical planning; large items (like multi-source integration) are divided.
12. Acceptance criteria are/will be clearly stated for all: e.g., “As a user, I receive a complete itinerary with all required bookings and a
map in under 10s; errors are clearly displayed if generation fails.”

Faculty-in-charge: Dr. Ruchi Kaushal , NMIMS

 A011 Atharv Kapoor B. Tech. IT. Sem-7th

4. Co- 5. 7. 11.
1. 2. Self- 3. 6. 8. 9. 10. 12. Clear
creatio Captu User Size
Requirement / Single contai Clear Usef Esti Easily Implementa Acceptan
n res - Not
Checklist Functio ned Entit ul to mat Priorit ble in One ce
Possibl Essenc frien Too
nality Info ies User able ized Schedule Criteria
e e dly Big
Destination
✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️
Exploration
Personalized AI
Itinerary Planning ✔️ ⚠️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️ ⚠️ ⚠️ ⚠️ ❌
(Gemini 2.5)
Booking
Integration ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️
(Amadeus API)
Real-Time Data
Aggregation (Web ✔️ ⚠️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️ ⚠️ ⚠️ ⚠️ ❌
scraping + APIs)
Interactive Map &
Navigation (OSM + ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️
Overpass API)
Collaborative Trip
Planning (Group ✔️ ⚠️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️ ⚠️ ⚠️ ⚠️ ❌
features)
User Reviews &
✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️
Local Tips
Multilingual UI
✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ⚠️
Support
Performance &
Scalability (Non-
❌ ❌ ❌ ⚠️ ❌ ⚠️ ⚠️ ❌ ✔️ ❌ ❌ ❌
Functional
Requirement)
Security and Data
❌ ❌ ❌ ⚠️ ❌ ⚠️ ⚠️ ❌ ⚠️ ❌ ❌ ❌
Protection

B.2: Learnings:

 Importance of Detailed Requirements: Precise and comprehensive requirements specifications are critical for
developing complex platforms like the Ultimate Travel Guide. They clarify not only what features the system must
have but also how these features interact with other systems, perform under various conditions, and remain secure.
 Balancing Functionality with Usability: Integrating advanced technology—like AI-driven itinerary generation and
real-time data aggregation—must go hand in hand with a user-friendly, efficient interface to truly deliver value to
travelers.
 Risk Awareness and Mitigation: Identifying dependencies (external APIs, scraping targets), performance risks, and
compliance issues (privacy, scraping legality) early in the requirements stage is essential to guide safe and sustainable
implementation.
 Security and System Correctness: Defining explicit requirements for authentication, data privacy, encryption, and
robust error handling builds user trust and system reliability from the outset.
 Iterative, Testable User Stories: Breaking down the project into clear, self-contained, and testable user stories
ensures the project can be developed, estimated, and validated effectively in agile cycles.

B.3: Conclusion:

A thorough requirements specification process sets the foundation for a successful software project. For the Ultimate Travel
Guide, it has ensured alignment between technical features (like AI, mapping, and integrated bookings), user needs
(personalization, ease, reliability), and the realities of software and platform integration.
By systematically reviewing and refining requirements—including their functionality, interfaces, performance, security, and
risks—the project is positioned for efficient development, fewer delays, and a final product that meets both stakeholder goals
and user expectations. This disciplined approach to requirements engineering is a best practice and a key takeaway for
delivering robust, user-centric digital platforms.

**********

Faculty-in-charge: Dr. Ruchi Kaushal , NMIMS