The category concept: an extension to the entity-relationship model
Data & Knowledge Engineering
A requirements modeling language and its logic
Information Systems
Goal-directed requirements acquisition
6IWSSD Selected Papers of the Sixth International Workshop on Software Specification and Design
Unifying temporal data models via a conceptual model
Information Systems
Semantics of time-varying information
Information Systems
Information modeling in the time of the revolution
Information Systems - Special issue: selected papers from the 9th International Conference on advanced information systems engineering (CA ISE '97)
Knowledge representation: logical, philosophical and computational foundations
Knowledge representation: logical, philosophical and computational foundations
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Temporal Entity-Relationship Models-A Survey
IEEE Transactions on Knowledge and Data Engineering
A foundation for vacuuming temporal databases
Data & Knowledge Engineering
The specification of business rules: A comparison of selected methodologies
Proceedings of the IFIP WG8.1 Working Conference on Methods and Associated Tools for the Information Systems Life Cycle
Tropos: An Agent-Oriented Software Development Methodology
Autonomous Agents and Multi-Agent Systems
Specifying and analyzing early requirements in Tropos
Requirements Engineering
Relating evolving business rules to software design
Journal of Systems Architecture: the EUROMICRO Journal - Special issue: Adaptable system/Software architectures
REERM: reenhancing the entity-relationship model
Data & Knowledge Engineering - Special issue: ER 2004
| Hi-index | 0.00 |
ERM remains the tool of choice for conceptual data modeling. It relies on entities and relations to model the domain of interest and so does essentially (differences in notation and terminology aside) object oriented modeling. Consistently with this perspective, prevailing “temporal models” are based on facts and their associated valid and transaction times, rather than events and the corresponding occurrence times. Arguably the approach is, in both cases, inadequate for design independent modeling of dynamic (i.e., time-varying) domains and possibly complicates the definition of the system's behavior. This paper puts forward an alternative, XCM, that purports to be richer and more domain-oriented, specially where history and forecasting support requirements arising from the temporal nature of the domain of interest are concerned, and that may have a positive influence in other aspects of conceptual modeling.