Java: Enforcing design decisions
I was advised over at stack overflow to post here instead. I'm not sure how well received questions that clearly serve test preparation are, but here goes:
What constructs in OOP languages (specifically Java) allow you to enforce design decisions and intent? I think some examples would be the 'final' keyword, access modifiers, template methods, perhaps interfaces - but clearly I am having trouble coming up with an exhaustive list. Some constructs, like inheritance, feel like they fit this criterion but I find it difficult to explain exactly why.
Any help would be much appreciated. Thank you in advance for any answers
I was advised over at stack overflow to post here instead. I'm not sure how well received questions that clearly serve test preparation are, but here goes:
What constructs in OOP languages (specifically Java) allow you to enforce design decisions and intent? I think some examples would be the 'final' keyword, access modifiers, template methods, perhaps interfaces - but clearly I am having trouble coming up with an exhaustive list. Some constructs, like inheritance, feel like they fit this criterion but I find it difficult to explain exactly why.
Any help would be much appreciated. Thank you in advance for any answers
No comments:
Post a Comment