CDO: Satisfy Your Requirements Before You Even Know You Have Them

Status:
Accepted

Suppose you must develop an application to support someone’s business processes and you accepted a set of requirements and agreed upon the underlying data model. Being eager to deliver, you employ the Eclipse Modeling Framework (EMF) to generate the interfaces and implementation classes of the model. Then you implement your functional requirements by programming against the generated model interfaces and you think you’re done. In this session I’ll explain the ten reasons why you’re not and how you could have been.

You’ve overlooked the following:

  • Database Persistence
  • Transactional Access
  • Collaboration
  • Scalability / Big Models
  • Thread Safety
  • Role-based Security
  • Auditing / Temporality
  • Branching / Merging
  • Fault Tolerance
  • Offline Availability

You'll leave this session with a good understanding of why you would have been done if you had chosen the Connected Data Objects (CDO) platform to satisfy these technical requirements.

Session details
Speaker(s): Session Type: Experience level:
Beginner
Track: Tags:
Schedule info
Session Time Slot(s):
Grand Peninsula A - Tuesday, March 18, 2014 - 17:00 to 18:00

Comments