This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hey guys, Sorry in advance if this question is out of place.
With that being said, my question is more about design than actual code. I am just thinking about designing a house alarm system (no real world value, just for fun) When I started designing (class diagram) it, I ended making the majority of my diagram interfaces.
My thinking with this was, for the system to work, (for example) an out side light must be able to detect movement, and must be able to turn on.
So normally I would make a class called OutsideList. But I made it into an interface because my thinking was, maybe someone wants to make an outside like that detects motion AND sound. So I wanted to let them....
With that thinking, everything turned into an interface, and my question is...Was that a good idea, or is it just making things annoying / diffucult to implement?