How does TSER modeling differ from ER modeling and Object Oriented modeling?
They are different, indeed. TSER covers horizontally (through the SER construct) both data modeling and knowledge modeling in the same framework, and vertically (SER and OER) both semantic/functional modeling and logical data modeling/database design. The traditional ER models do not include knowledge and do not support dependency analysis within an entity or a relationship. When comparing TSER to object models, the latter subordinate knowledge to data (i.e., lacking the independent representation of inter-subject knowledge as contexts) and do not support dependency analysis, either. Thus, the design of the CASE tool is heavily biased towards implementing TSER as opposed to equally supporting ER and OO. We’re enhancing the ERs and OO personalities of TSER to support these common uses, since the software is now provided to the community at large. Even when we accomplish this completely, ER is still not best compared to SER, but OER. For some disciplined ER models which are similar to OO
Related Questions
- How does TSER modeling differ from ER modeling and Object Oriented modeling?
- How to do Object Oriented Modeling using TSER constructs?
- How to do Object Oriented Modeling using TSER constructs?
- What are the advantages of Object Oriented Modeling?
- What are the advantages of Object Oriented Modeling?
- Does PowerDesigner support Object Oriented modeling?
