1. So You Think Objects Are RecordsWith Byte Codes On The Side? T h i n k A g a i n

2. Where Do Objects Fit?As a vehicle for implementing programs.So You Think Objects Are Records With Byte Codes On The Side? 2 3. Where Do Objects Fit?As a vehicle for implementing programs.As a vehicle for modeling actual business entities andthe diverse, complex rules that govern theirinterpretation and use.So You Think Objects Are Records With Byte Codes On The Side? 3 4. How Do We View Objects? Traditional thinking holds that objects are the managers and clients of state stored in data base records. So You Think Objects Are Records With Byte Codes On The Side? 4 5. How Do We View Objects? Traditional thinking holds that objects are the managers and clients of state stored in data base records. An intuitively appealing conceptual model... So You Think Objects Are Records With Byte Codes On The Side? 5 6. How Do We View Objects? Traditional thinking holds that objects are the managers and clients of state stored in data base records. An intuitively appealing conceptual model... that is inherently external to the data base. So You Think Objects Are Records With Byte Codes On The Side? 6 7. How Do We Implement Objects? Traditional thinking holds that objects are records with methods on the side. So You Think Objects Are Records With Byte Codes On The Side? 7 8. How Do We Implement Objects? Traditional thinking holds that objects are records with methods on the side. An intuitively appealing conceptual model... So You Think Objects Are Records With Byte Codes On The Side? 8 9. How Do We Implement Objects? Traditional thinking holds that objects are records with methods on the side. An intuitively appealing conceptual model... that insists on viewing the world one individual at a time. So You Think Objects Are Records With Byte Codes On The Side? 9 10. So Whats Wrong With That? It may work for clients that consume relatively small amounts of data... So You Think Objects Are Records With Byte Codes On The Side? 10 11. So Whats Wrong With That? It may work for clients that consume relatively small amounts of data... It may work for programs So You Think Objects Are Records With Byte Codes On The Side? 11 12. So Whats Wrong With That? It may work for clients that consume relatively small amounts of data... It may work for programs but it leaves the hard problem of implementing scaleable business objects, particularly entity objects, as an exercise for the reader.So You Think Objects Are Records With Byte Codes On The Side? 12 13. So Where Do We Go Next? Establishing Principles Starting At The Top Questioning Assumptions Developing a New Foundation So You Think Objects Are Records With Byte Codes On The Side? 13 14. Establishing PrinciplesFrom an application perspective: comprehensibility most applications we encounter are ultimatelydeveloped by involved, business knowledgeable users,not programmers. integration solving interface and impedance matching problemsis a jargon laden waste of time.So You Think Objects Are Records With Byte Codes On The Side? 14 15. Establishing PrinciplesFrom a technology perspective: theory a collection centric theory of operation is critical toachieving reliable application scalability anddeployment.integration solving interface and impedance matching problemsis a jargon laden waste of time.So You Think Objects Are Records With Byte Codes On The Side? 15 16. Establishing PrinciplesFrom any perspective: generality most applications are a collection of many simple,hard problems. it is impossible to overstate the complexity of eventhe simplest looking applications.So You Think Objects Are Records With Byte Codes On The Side? 16 17. Starting At The TopWithout creating an application specific technology,start with an understanding of how entity basedapplications work and what needs to be in place inorder to create them.So You Think Objects Are Records With Byte Codes On The Side? 17 18. For Example, Account defineMethod: [ | getHoldingsOverlap | A mutual fund analysis!lowerPct