... | ... | @@ -4,29 +4,30 @@ |
|
|
Our team is developing a website for a flight reservation system, therefore we will be combining the conventional testing strategies of software and the innovated Web Application Testing.<br>
|
|
|
|
|
|
**Scope**<br>
|
|
|
- The features and requirements (functional and non-functional) that will be checked and those that will not be checked. Refer to FURPS+<br>
|
|
|
Functionality - What the customer wants! Note that this includes security-related needs.
|
|
|
|
|
|
*Functional*
|
|
|
<br>
|
|
|
1. As a customer, I want to be able to easily search for flights based on the desired destination, origin, departure date/time so I can book flights with minimal technological ability.
|
|
|
Usability - How effective is the product from the standpoint of the person who must use it? Is it aesthetically acceptable? Is the documentation accurate and complete?
|
|
|
|
|
|
2. As a customer, I would like to see all of the details related to my reservation including terminal number, luggage added, booking reference, etc. so check-ins are easier and I feel prepared.
|
|
|
Reliability - What is the maximum acceptable system downtime? Are failures predictable? Can we demonstrate the accuracy of results? How is the system recovered?
|
|
|
|
|
|
3. As a customer, I want a website that is visually appealing and doesn’t require any extra digging for information, so I can save time and effort.
|
|
|
Performance - How fast must it be? What's the maximum response time? What's the throughput? What's the memory consumption?
|
|
|
|
|
|
4. As a customer, I want to see the current time at my origin/destination and what time it will be when I arrive, so I can plan my trip accordingly.
|
|
|
Supportability - Is it testable, extensible, serviceable, installable, and configurable? Can it be monitored?
|
|
|
|
|
|
5. As a customer, I would like to know the exact trip length and the exact final price before booking, so I have a sense of awareness.
|
|
|
|
|
|
6. As a customer, I want different language options so I can choose a language I’m most comfortable with.
|
|
|
Design constraints - Do things like I/O devices or DBMS constrain how the software must be built?
|
|
|
|
|
|
7. As a customer, I want to know that my financial information is secure when booking a flight, so I’m not concerned about my information being leaked.
|
|
|
Implementation requirements - Do the programmers need to adhere to standards? Is the use of TDD required? Is statistically sound testing in the context of Cleanroom required?
|
|
|
|
|
|
8. As a new customer, I want an “About” section where I can learn about the company before I book with them so I can feel more connected and develop trust.
|
|
|
<hr>
|
|
|
*Non-Functional*
|
|
|
Interface requirements - What downstream feeds must be created? What other systems must this one interface with? How frequent are feeds produced?
|
|
|
|
|
|
Physical requirements - What hardware must the system be deployable on? Must we be able to deploy to a machine no larger than 12" square, to be stationed in the Iraqi desert?
|
|
|
|
|
|
*Functional*<br>
|
|
|
All eight ranked user stories with eligible acceptance tests (from Milestone 5 <Storyboard> ).
|
|
|
|
|
|
*Non-Functional*
|
|
|
Font size of text, webpage loading speed, etc.
|
|
|
|
|
|
**Quality Objective**<br>
|
|
|
An easy-to-use web application for not just markers but everyone who has basic technology of computer<br>
|
... | ... | |