Software Development Cross Solution - Index of - Free

test for bugs
Figure out what functionality works
You know that Orion’s Orbits was working fine until you integrated the
Mercury Meals library, so let’s focus on that code. The first step is to
find out what’s actually working, and that means tests. Remember, if it’s
not testable, assume it’s broken.
MercuryMeals
uses the singleton
pattern; you
call the static
getInstance()
method to get an
instance, instead
of instantiating
the class with the
“new” keyword.
You’ve got two
basic interfaces to
work with, along
with any helper
code that might
be hiding in these
classes.
396 Chapter 11
MercuryMeals
Here’s the main interface to
the Mercury Meals code.
+ getInstance(): MercuryMeals
+ createOrder(): Order
+ submitOrder(order: Order): boolean
+ getMealOption(name: String): MealOption
+ getOrdersThatMatchKeywords(keywords: String[]): Order[]
Order
+ addMealOption(mealOption: MealOption): void
+ addKeyword(keyword: String): void
Remember, we want
to use the flight
number as the
keyword for a meal.
Download at WoweBook.Com
Design note: Naming
a class with your
company’s name is a
lousy idea—Mercury
really was an awful
development shop!