my dog learned polymorphism*
The moose likes OO, Patterns, UML and Refactoring and the fly likes CS/Engineering Terminology and Compromises in Modeling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "CS/Engineering Terminology and Compromises in Modeling" Watch "CS/Engineering Terminology and Compromises in Modeling" New topic
Author

CS/Engineering Terminology and Compromises in Modeling

Tony Tirolese
Greenhorn

Joined: Nov 20, 2011
Posts: 12

Is there a generally accepted term or concept in computer science or software engineering associated with the following:

You are designing a software model of a physical, real-world system. You realize that you could make the software model much more efficient (processing, resources, coding) if you organized the components of the software model a little bit differently from the physical system you are simulating. In the end, the user gets exactly the same feedback from any input to the model that they would have gotten from the real world system, but you have "cheated" with some of the "levers and pulleys" inside the model in order to achieve that.
Jelle Klap
Bartender

Joined: Mar 10, 2008
Posts: 1761
    
    7

Abstraction?


Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: CS/Engineering Terminology and Compromises in Modeling