Question

A test specification provides designers with what needs to be known in order to perform a specific test, and to validate and verify the requirement to be tested. The test script is divided into the test script, which is the generic condition to be tested, and one or more test cases within the test script. Provide a test script and test case for at least 3 of your requirements identified in your requirements specification. Provide the following format for an ONLINE AIRLINE RESERVATION SERVICE

• Test script:
  • Test script ID
  • Test description (generic condition being tested)
  • System or subsystem being tested
  • Type of test (functional, security, performance)
  • Input data sources
  • Expected results
  • Priority (mandatory or critical; important; desirable)
  • Pass/Fail criteria (allowable delta between degree of mismatch between actual and expected results)
  • Traceability (ties back to functions, modules, data structures)
• Test Case:
  • Test Case ID and test script number (which script this test case is exercising)
  • Input test transaction data values
  • Initial environment and configuration, initial state of system required for this test
  • Test driver ID (if a real driver is needed)
  • Expected results (output test data values)

1. Introduction:

1.1 Purpose

The purpose of this document is to build an online system to manage flights and passengers to ease the flight management.

1.2 Scope

The purpose of the online flight management system is to ease flight management and to create a convenient and easy-to-use application for passengers, trying to buy airline tickets. The system is based on a relational database with its flight management and reservation functions. We will have a database server supporting hundreds of major cities around the world as well as thousands of flights by various airline companies. Above all, we hope to provide a comfortable user experience along with the best pricing available.

2. References:https://www.uccs.edu/Documents/tboult/srs.doc.

3. Overall Description:

A distributed airline database system stores the following information.

• Flight details:
  It includes the originating flight terminal and destination terminal, along with the stops in between, the number of seats booked/available seats between two destinations etc.

• Customer description:
  It includes customer code, name, address and phone number. This information may be used for keeping the records of the customer for any emergency or for any other kind of information.

• Reservation description:
  It includes customer details, code number, flight number, date of booking, date of travel.

Users of the system should be able to retrieve flight information between two given cities with the given date/time of travel from the database. A route from city A to city B is a sequence of connecting flights from A to B such that: a) there are at most two connecting stops, excluding the starting city and destination city of the trip, b) the connecting time is between one to two hours. The system will support two types of user privileges, Customer, and Employee. Customers will have access to customer functions, and the employees will have access to both customer and flight management functions.

4. Specific Requirements/Functionality:The customer should be able to do the following functions:

• Make a new reservation
  • One-way
  • Round-Trip
  • Multi-city
  • Flexible Date/time
  • Confirmation

• Cancel an existing reservation

• View his itinerary

The Employee should have following management functionalities:

• CUSTOMER FUNCTIONS.
  • Get all customers who have seats reserved on a given flight.
  • Get all flights for a given airport.
  • View flight schedule.
  • Get all flights whose arrival and departure times are on time/delayed.
  • Calculate total sales for a given flight.

• ADMINISTRATIVE
  • Add/Delete a flight
  • Add a new airport
  • Update fare for flights.
  • Add a new flight leg instance.
  • Update departure/arrival times for flight leg instances.

Each flight has a limited number of available seats. There are a number of flights which depart from or arrive at different cities on different dates and time.

5. Usability: The flight schedules should satisfy a maximum number of customers needs.

6. Reliability:The flight should reach start from correct start terminal and should reach the correct destination.

7. Performance:The airline reservation system maintains information on flights, classes of seats, personal preferences, prices, and bookings. Of course, this project has a high priority because it is very difficult to travel across countries without prior reservations.

• Search for Airline Flights for two Travel cities

• Displays a detailed list of available flights and make a “Reservation” or Book a ticket on a particular flight.

• Cancel an existing Reservation.

8. Supportability: The administrators and flight in chargers should maintain correct schedules of flights.

9. Design Constraints:
   The global schema, fragmentation schema, and allocationschema.

• SQL commands for above queries/applications

• How the response for application 1 and 2 will be generated. Assuming these are global queries. Explain how various fragments will be combined to do so.

• Implement the database at least using a centralized database management system.

10. Licensing: Any licensing enforcement requirements or other usage restrictions on the airline reservation software are listed here.

11. RequirementsVerification:

    -Simple checks

    -Prototyping (choose prototype testers, develop test scenarios, execute test scenarios, document problems using a problem reporting tool)

    -User manual development

    -Reviews and inspections (A group of people read and analyze requirements , look for potential problems, meet to discuss the problems, and agree on a list of action items needed to address these problems.)

    -Functional test design

12. Requirements Traceability: Requirements Traceability

    Requirements traceability refers to the ability to describe and follow the life of a requirement, in both forwards and backwards direction (i.e. from its origins, through its development and specification, to its subsequent deployment and use, and through all periods of on-going refinement and iteration in any of these phases.)

    Performing a requirements traceability analysis is an important part of the software engineering process as it ensures that all of the requirements have been adequately considered during each phase of the project, and that there aren't any scope 'holes' in the developed system due to missed requirements. The activity also ensures that all of the requirements are internally consistent with each other and support the overarching business drivers, goals and objectives. The most common way of ensuring that there is full requirements traceability is by means of a Requirements Traceability Matrix (RTM). The traceability matrix is used to verify that all stated and derived requirements are associated with corresponding design elements, system components, modules and other project deliverables. This is known as the forward trace. The RTM is also used to verify and document the original source of the requirements so that if questions should arise by the customer regarding why certain features were included, there is a comprehensive audit trail. This is known as the backward trace.

Answer 1

       ANSWER:

• Test Script: Student login script

• Test Script ID: Student login #1

• Test description: Check if student is genuine student.

• System or subsystem being tested : Login system

• Type of test: Functional and security

• Input data Source: Login records

• Expected results : Correct Student Login, success on correct details, error messages on unsuccessful login attempt, lock login on three unsuccessful attempts

• Priority: Mandatory and Critical

• Pass: Correct student Id and password

• Fail: Three incorrect student Id and password

• Traceability:

• Student_login check from login files and passwords from password link file

• Test case: Correct login

• Test case ID : Correct login. Student login#1

• Input test transaction data value: Login ID and password

• Expected result: Login and password match

• Test case: Incorrect login

• Test case ID : Incorrect login. Student login#1

• Input test transaction data value: Login ID and password

• Expected result: Login and password does not match, Increment number of attempt by one

• Test case: Incorrect login Third attempt

• Test case ID : Incorrect login Third attempt. Student login#1

• Input test transaction data value: Login ID, password and number of login attempts

• Expected result: Login and password does not match, lock the login ID

Please Kindly help with Thumbs up for this answer. If any doubts feel free to query. Thank you