sonny-maan / oystercard

Oystercard Clone!

Oystercard Challenge

This week's challenge will start with going back over the basics we covered last week in Boris Bikes, giving you the chance to reinforce what you learned last week. You'll then be challenged to build a more complex system which should really stretch your skills in Ruby, TDD and object-oriented design.

Focus goals

Mindful engagement with these challenges can help you achieve these goals:

I write code that is easy to change

Writing easy to change software is highly prized amongst developers and employers. By developers because most of a developer's time is spent changing software. By employers because their teams can deliver value to customers faster.

I can test-drive my code

Tested software is easier to change because you can tell when it's broken just by running a command, even the tricky edge cases.

I can build with objects

Most code in the world is structured in small pieces called objects. This is done because it is easier to change than having everything in one place.

Weekly challenge user stories

Here are the user stories you will be working on for this project:

In order to use public transport
As a customer
I want money on my card

In order to keep using public transport
As a customer
I want to add money to my card

In order to protect my money
As a customer
I don't want to put too much money on my card

In order to pay for my journey
As a customer
I need my fare deducted from my card

In order to get through the barriers
As a customer
I need to touch in and out

In order to pay for my journey
As a customer
I need to have the minimum amount for a single journey

In order to pay for my journey
As a customer
I need to pay for my journey when it's complete

In order to pay for my journey
As a customer
I need to know where I've travelled from

In order to know where I have been
As a customer
I want to see to all my previous trips

In order to know how far I have travelled
As a customer
I want to know what zone a station is in

In order to be charged correctly
As a customer
I need a penalty charge deducted if I fail to touch in or out

In order to be charged the correct amount
As a customer
I need to have the correct fare calculated

Sequence & Schedule

• Onsite
• Remote

Set up the project:

1. Create a Gemfile
2. Create RSpec conventional files
3. Review debugging basics

Create a basic Oyster card:

4. Add the balance
5. Enable top up functionality
6. Enforce maximum balance
7. Deduct the money

Add touch in/out functionality:

8. Add touch in/out support
9. Checking mininum balance on touch in
10. Charging for the journey

Record the journeys

11. Saving the entry station
12. Adding journey history
13. Creating the station class

Refactor to extract Journey class

14. Handling a journey without a touch out

Refactoring: get the code into shape

15. Extracting the journey log out of the Oystercard

Make fares depends on zones

16. Calculating the fare between zones

Example Code