Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Come back to our check in passenger example - After confirmed with the stakeholders … (This maybe the final product use case scenario) 1. Get the passenger’s.

Similar presentations


Presentation on theme: "1 Come back to our check in passenger example - After confirmed with the stakeholders … (This maybe the final product use case scenario) 1. Get the passenger’s."— Presentation transcript:

1 1 Come back to our check in passenger example - After confirmed with the stakeholders … (This maybe the final product use case scenario) 1. Get the passenger’s ticket or record locator1. Locate the passenger’s reservation 2. Is this the right passenger, flight, and destination? 2. Ensure the passenger is correctly identified and connected to the right reservation 3. Check the passport is valid and belongs to the passenger. 4. Record the frequent-flyer number to the reservation. 5. Find a seat.5. Allocate a seat. 6. Check the baggage onto the flight. 7. Ask security questions. 8. Print and hand over the boarding pass and bag tags.8. Print the boarding pass and bag tags. 9. Wish the passenger a pleasant flight.

2 2 It is time to start writing the requirements (the first draft) R1. Locate the passenger’s reservation R2. Ensure the passenger is correctly identified and connected to the right reservation R3. Record the frequent-flyer number to the reservation. Is it correct? How to write the requirements? 1. Get the passenger’s ticket or record locator1. Locate the passenger’s reservation 2. Is this the right passenger, flight, and destination? 2. Ensure the passenger is correctly identified and connected to the right reservation 3. Check the passport is valid and belongs to the passenger. 4. Record the frequent-flyer number to the reservation. 5. Find a seat.5. Allocate a seat. 6. Check the baggage onto the flight. 7. Ask security questions. 8. Print and hand over the boarding pass and bag tags.8. Print the boarding pass and bag tags. 9. Wish the passenger a pleasant flight.

3 3 It is time to start writing the requirements (the first draft) If you uncover only one requirement from each step, it suggests either the level of detail in your scenarios is too granular or your functional requirements are too coarse.

4 4 Example of 6. Check the baggage onto the flight Check baggage R1. The maximum number of baggage shall be two. R2. The baggage dimensions shall not bigger than 50x70x100cm R3. The maximum weight shall be no more than 100kg. 1. Get the passenger’s ticket or record locator1. Locate the passenger’s reservation 2. Is this the right passenger, flight, and destination? 2. Ensure the passenger is correctly identified and connected to the right reservation 3. Check the passport is valid and belongs to the passenger. 4. Record the frequent-flyer number to the reservation. 5. Find a seat.5. Allocate a seat. 6. Check the baggage onto the flight. 7. Ask security questions. 8. Print and hand over the boarding pass and bag tags.8. Print the boarding pass and bag tags. 9. Wish the passenger a pleasant flight.

5 5 Writing Requirements – be consistence for writing requirements, Simply use shall, do not mix with must, may, might, will etc Unless you define those words meaning. Requirements should say only “what to do” Not “how to do”


Download ppt "1 Come back to our check in passenger example - After confirmed with the stakeholders … (This maybe the final product use case scenario) 1. Get the passenger’s."

Similar presentations


Ads by Google