Adding prac 6

[algh0065]

Test Plan for Baggage System

Any new system should be sufficiently tested before its release in order to avoid problems during the production stage. The individuals who are responsible for the system testing must communicate the process and results of the test. The individuals should identify any problem that can occur in the system. The testing process takes an objective approach to avoid any bias. This report looks at a sample test plan for an airport baggage system. The baggage systems at major airports handle huge volumes of bags. The systems are designed with a conveyor belt system to move the bags to their destinations. The system has various sensors and actuators. Most of the existing baggage systems have central control systems equipped with dedicated computers for autonomous operation.

Objectives and Tasks

Objectives

The document highlights the test procedure for a new airport baggage handling system. It documents a systematic approach that can be used to test any system. The results of such a test can be used as a service level agreement because it details how the system will perform in real life environment. Tasks The tasks involve testing the sensor networks, the system capacity, its reliability and how the system handles emergency situations. The test also looks at the system performance during peak and off-peak operation.

Scope

General The test looks at all the risks that face the baggage system. It simulates all the worst-case scenarios that the system can face. Tactics

The main objective of such a test is to avert all the problems that occur during the system operation. The tactic is to simulate the real life breakdown situation or procedure and evaluate how the system performs.

Testing Strategy Many operations of the system can be tested using computer aided design software. The user acceptance test can be done after the system or a section of it has been tested.

Alpha Testing (Unit Testing) The unit testing concentrates on the minimum performance requirement of the system.

The test procedure starts by testing if the system can perform the basic operations that form the minimum operation requirements. The baggage system should identify the bags. It should transport the system to their destination.

System and Integration Testing The process of integrating the system into the existing operations must be simulated. This is crucial in order to avoid system failure during the changeover period.

Performance and Stress Testing Peak and off-peak situations can be tested to evaluate how the system will cope with different operation situations. Emergency situations must be tested. This can be done using computer aided design (CAD) software to mimic system loading.

User Acceptance Testing User acceptance test can be used to evaluate the response of the user to the performance of the system. The system can be implemented and a limited number of passengers directed to operate from that section of the airport. The airport authority can use the domestic section of the airport to test the system.

Hardware Requirements The baggage system requires different sensors and actuators to operate. It also requires control systems that are usually implemented by dedicated computer systems.

Software Requirements The baggage system is usually assembled from components supplied by different manufacturers. Some of the components come with inbuilt software for control. The manufacturers provide an interface to help in integrating the software into the whole system.

Features to Be Tested Peak and Off-peak Operation The system should be able to detect peak periods in order to dedicate all the available resource. Off-peak periods should have reduced operation in order to reduce the operating costs.

Power Failure A simulated power failure test must be done to determine how the system will perform. The response time in such a situation is very important because it will determine if the flights will delay or not. Reliability

The reliability of the system components is important. The system should operate for long periods without breakdown. Baggage Loss Baggage loss can ruin the reputation of an airport facility. The system must be able to trace the exact point that the missing luggage disappeared in order to ensure speedy recovery.

Breakdown Handling The system must have the ability to divert the baggage handling task to another arm in case one section experiences failure.

Error Handling A good system should be able to handle errors. The test approach is to evaluate common errors that occur in the system like missing identification tags.

Sorting The ability of a baggage system to sort the bags is crucial. Any errors in sorting will lead to loss of bags. The test can be done by putting bags with different identification tags and evaluating the system performance. Features Not Tested

Security Security of an airport system is a sensitive matter and be handled by an independent system. The security protocol at an airport is determined by the policies that are set by the regulatory authority in that particular country and will not be tested in this plan.

Risks/Assumptions It is assumed that the tools used in the test environment will replicate the real life situation. The deviation between the simulation and the real life system will be minimal. Tools Due to the high cost of implementing an airport baggage handling system, the system can be best tested using a computer aided design (CAD) software. An airport baggage system is very expensive. Therefore, a computer simulation will be appropriate.

Approvals The system must be approved by regulatory authorities involved. The transport authorities in the country of operation must approve the system. The system must also meet the certain international operating standards.

References Shanks, N. E., & Bradley, A. L. (2004). Handbook of checked baggage screening: advanced airport security operation. London: Professional Engineering. Testing Help. SoftwareTesting and Quality assurance Templates. Software Testing Help RSS. Retrieved June 12, 2014, from http://www.softwaretestinghelp.com/test-plan-sample-softwaretesting-and-quality-assurance-template

[gardners]

You have successfully identified a number of issues, but you approach seems to treat the system as a monolithic whole, and fails to take advantage of the possibility of scaling up progressively, testing at each stage of integration and scale. Nonetheless, I will accept it.