Requirements Continued
Based on the initial vague Requirements you probably have some questions.
Questions
How to identify different rooms?
- Each room has a location code (identification).
- Some rooms have a name.
How big is the meeting room?
- For every room the number of persons that can use it together (for a meeting) is known.
Is the number of rooms / facilities known?
- During startup of the service(s), the configuration of rooms and facilities can be loaded.
Sample Data
Below are three samples given of concrete data, for rooms and their possible facility.
Sample 01
Name | Location | Capacity | Facilities |
Mercury | BG.01-1 | 8 | computer small screen |
Venus | BG.02-1 | 16 | computer large screen/whiteboard |
Mars | BG.02-1 | 30 | beamer |
Sample 02
Name | Location | Capacity | Facilities |
Athens | DE-01 | 8 | whiteboard |
Berlin | DE-05 | 16 | beamer/whiteboard/workstations |
Copenhagen | WL-03-01 | 12 | whiteboard |
Dublin | WL-02-01 | 12 | whiteboard |
Sample 03
Name | Location | Capacity | Facilities |
1st floor 03 | 6 | ||
1st floor 05 | 6 | ||
2nd floor 02 | 10 | ||
2nd floor 03 | 10 |
Create Cucumber Features
Based on the requirements, questions, answers and sample data create scenarios in Cucumber Gherkin format.
Feature: Refund item
Scenario: Jeff returns a faulty microwave
Given Jeff has bought a microwave for $100
And he has a receipt
When he returns the microwave
Then Jeff should be refunded 100 USD
Written on May 7, 2016