Skip to main content

Identifying interactions











[Time 5:50 mins]


In this section we will identify collaborations among the classes as they enact each use case. In this phase we may discover new classes that we had not thought of earlier, as well as new responsibilities for existing classes. We may also discard some initial classes. The process of determining the collaborations as each use case is enacted helps in refining and validating the design.


CUSTOMER DETERMINES THE PRICE OF A GROUP OF ITEMS:

  1. Customer enters item codes at the UserTerminal
  2. UserTerminal creates Item objects for each item and finds out their individual prices
  3. The UserTerminal finds out all the schemes these items belong to
  4. The UserTerminal determines the Scheme price of all items belonging to a Scheme and adds the individual price of the remaining items
  5. The UserTerminal displays all the above information to the Customer

 

CUSTOMER CHECKS OUT ITEMS:

  1. Customer takes items to the checkout system
  2. Checkout assistant adds item codes in the CheckoutSystem
  3. Checkout system determines the price of all the items, taking into account discounts and schemes
  4. Checkout system generates a bill for the customer
  5. Checkout system accepts the customers payment

 

STOREMANAGER DETERMINES THE SHOP INVENTORY VALUATION

  1. The StoreManager uses the ControlPanel to get inventory vauation
  2. The ControlPanel uses the CurrentStock to get the valuation
  3. The CurrentStock object determines the price of every individual item and the price of items and represents it as the maximum price in the PriceRange
  4. The CurrentStock determines the minimum price by associating items into schemes and assuming that they are sold such
  5. The CurrentStock returns the PriceRange object back to the ControlPanel which displays the details to the StoreManager

New classes identified:

  • UserTerminal
  • CheckoutSystem
  • PriceCalculator
  • ControlPanel
  • PriceRange


Note: This post was originally posted on my blog at http://www.adaptivelearningonline.net
Labels:

Comments

Post a Comment

Popular posts from this blog

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other ...
3 comments
Read more

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables ...
Post a Comment
Read more

Running your own one person company

Recently there was a post on PuneTech on mom's re-entering the IT work force after a break. Two of the biggest concerns mentioned were : Coping with vast advances (changes) in the IT landscape Balancing work and family responsibilities Since I have been running a one person company for a good amount of time, I suggested that as an option. In this post I will discuss various aspects of running a one person company. Advantages: You have full control of your time. You can choose to spend as much or as little time as you would like. There is also a good chance that you will be able to decide when you want to spend that time. You get to work on something that you enjoy doing. Tremendous work satisfaction. You have the option of working from home. Disadvantages: It can take a little while for the work to get set, so you may not be able to see revenues for some time. It takes a huge amount of discipline to work without a boss, and without deadlines. You will not get the benefits (insuranc...
10 comments
Read more