Home/ Questions/Q 6541579
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T11:07:19+00:00

Is it beneficial in OO design to include drawing capabilities in otherwise model classes?

  • 0

Is it beneficial in OO design to include drawing capabilities in otherwise model classes?

To give an example, on a university project, I have to develop an implementation of the board game ‘ticket to ride’. In there, I have a Card class called AbstractCard, to represent a card in the game, subclassed by TrainCard and DestinationCard. The AbstractCard class would look like this:

-------------------------------
|      AbstractCard            |
-------------------------------
|                              |
--------------------------------
|drawFront(Graphics2D:g2):void |
|drawBack(Graphics2D:g2):void  |
--------------------------------

The subclasses add extra data and methods.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There is no hard and fast rule that you MUST separate out the business logic from the UI.

    Ask yourself these questions:

    • What is the probability that the class that you are designing will be modified in the future?
    • Will it add other user interfaces (views) in the future (like accessing the business logic through the web services, etc.)?

    In most of the cases the answer to the above questions is a resounding yes. But note that there is negative impact on the performance of the application when you implement this sort of loose coupling (Designing Too Far Into The Future). So my advice is unless the application has a requirement for loose coupling do not make it so. Beware of overengineering!

    More information

    • 0