Title
Business Object Design and Implementation III: OOPSLA99 Workshop Proceedings 2 November 1999, Denver, Colorado, USA,Used
Sold by Ergodebooks, an authorized reseller.
Returns accepted within 30 days | support@ergodebooks.com
Shipping Information
- Free Standard Shipping — United States only
- Processing Time: 1–3 business days
- Estimated Delivery: 3–5 business days after dispatch
- Double-boxed, fully insured & discreetly packaged
- Tracking number sent via email once dispatched
- Orders over $250 require signature upon delivery. Taxes calculated at checkout.
Returns & Refund
Returns accepted within 30 days of delivery.
Damaged or Defective Item
Free return shipping + replacement or full refund
Wrong Item Received
Free return shipping + replacement or full refund
Change of Mind
Return shipping at customer's expense · 25% restocking fee applies
Payment Option
The NCITS Accredited Standards Committee H7 Object Information Management, now part of NCITS T3 Open Distributed Processing, and the Object Management Group BUsiness Object Domain Task Force (BODTF) jointly sponsored the Fifth Annual OOPSLA Workshop on Business Object Component Design and Implementation. The focus of the workshop was on design and implementation of business object component frameworks and architectures. Key aspects discussed included: What is a comprehensive definition of a business object component'? Are the four layers (user, workspace, enterprise, resource) presented at the OOPSLA'98 workshop the right way to layer a..bysiness object component. system? How is a business object component implemented across these layers? What are the associated artefacts? Are there different object models representing the same business object component in different layers? What are the dependencies between business object components? How can they be plug and play given these dependencies? How can they be flexible and adaptive? How do they participate in workflow systems? How will the em~rgence of a webbased distributed objectcomputing infrastructure based on XML, influence business object component architectures? In particular, is the W3C WebBroker proposal appropriate for distributed business object component computing? The aim of the workshop was to: Enhance the pattern literature on the specification, design, and implementation of interoperable, plug and play, distributed business object components.
⚠️ WARNING (California Proposition 65):
This product may contain chemicals known to the State of California to cause cancer, birth defects, or other reproductive harm.
For more information, please visit www.P65Warnings.ca.gov.