Design Continues

• Let's continue to work on the SodaMachine
• 
  • Make this diagram in umlet quickly.
  • umlet
  • On Line version
  • Save and load in each.
• How do I define the behaviors of the SodaMachine
  • I need to model a button press.
    • Do I want a Single button press or
      • a soda button press, give button id
      • A coin return button press
    • These are physically different objects, so I will do the following
    • 
  • I could start to write algorithms for these right now, but I am focused on the SodaMachine Interface.
  • I need to insert money.
    • I think just a InsertMoney method will do.
  • I am not modeling the machine for maintenance, so I don't want
    • AddCans
    • AddCoins
    • RemoveCoins ...
  • 
  • The UML book gives the following syntax for methods
    • The behavior/operation/method syntax
    • 
    • The parameter syntax
    • 
    • The multiplicity syntax
    • 
    • Ignore properties for now.
  • Some notes:
    • Try to be accurate with the UML diagram.
    • But this is a tool, not a programming language for us.
    • Also notice, I am only focusing on the level of abstraction for the problem I am solving.
      • I am not including properties
      • I am not including relationships.
• Let's work on these behaviors.
  • In doing this, it will help me validate my high level model.
  • It will give me some insight into the interfaces needed for the components.
  • CoinReturnPress

    • Get available coins from the bank
          // this will be an array of coin values and quantities
      Give available coins to the banker
          // this will return either a list of coins or error
      If not error
          tell the banker to reset amount to 0
          while (there are coins in the list of coins) 
             get coin from bank
             give coin to output
      else
          give error message to output.  

  • SodaPress(id)

    • Ask soda bin id for price of top soda (sodaPrice)
      Ask banker for amount deposited (amount)
      if (amount >= sodaPrice) 
          Ask soda bin id for top soda (can)
          Give can to output
          Tell banker to deduct soda price
          Do CoinPressReturn
      else
          Give "insufficient funds", price, amount to output 

  • InsertMoney(money)

    • Tell banker to add the amount of the money
      Give money to bank 

• I am somewhat happy with these
  • I feel I am really bad at naming things, so this might need modified.
  • There could be errors, but we are validating the design right now.
  • I think we are on the right track for validation.
  • Right now I am not worried about copy constructors, assignment operators and anything else.
    • Competent programmers should know to add these if required.
    • And that would just add complexity to a complex design
• Let's start on the properties/attributes/member values
  • 
  • 
  • I didn't like the name Output, so I changed it to OutputDevice.
• We should add all of this to our design document.
• What would a next step be?
  • We could build a soda machine with stubs for each of the components.
  • I would be much happier if I at least did an outline of each of the components.