Design UI Entities that make your life easier
Nuestro amigo Javier Caceres nos comparte su artículo:
Design UI Entities that make your life easier
While designing software you think about the system in abstract terms and you try to model under the Object Oriented paradigm, so your universe looks like a harmonic set of objects, which usually are persistent as tables (the relationship between objects and tables is usually 1:1). You’re happy, the design seems perfect.
In the middle of development a software developer start using the “new UI control” that seemed to be the best in the research stage and quickly finds that for showing a summary or a nested column chart is necessary to break the design with some new classes which emerge as Frankenstein objects compared with the existing harmonic set of objects. When I say Frankenstein I want to describe a class which is loosely cohesive and highly coupled to the consumer.
These new objects should not be Frankenstein, they should be well designed and modelled since the beginning but under a different paradigm because although chart series and reports can be adjusted into the OOP paradigm, you will quickly be a victim of the Object-relational impedance mismatch, and thus a Frankenstein objects maker.
Ver más aquí.
Saludos.
Fernando García Loera (Community Program Manager – Latin America Region)
