Business Object Design And Implementation

Over the past 10 years, object technology has gained widespread acceptance within the software industry. Within a wider context, however, it has made little impact on the core applications which support businesses in carrying out their tasks. This volume contains a collection of papers establishing the need for Business Objects, with particular reference to work undertaken by the Object Management Group (OMG). The emphasis is on defining an agenda for establishing Business Object standards and architectures, for developing software technology to support Business Objects applications and managing object oriented development projects. The wide variety of papers presented, and their authors' expertise, make this book a significant contribution to the development of Business Objects and their management.

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 web-based distributed object-computing 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.

This proceedings contains some of the papers presented at the Business Object and Implementation Workshops held at OOPSLA'96, OOPSLA'97 and OOPSLA'98. The main theme of the workshops is to document the evolution of business objects, from ~any perspectives, including modelling, implementation, standards and applications. The 1996 workshop intended to clarify the specification, design, and implementation of interoperable, plug and play, distributed business object components and their suitability for delivery of enterprise applications; and to assess the impact of the WWW and, more specifically, the Intranet on the design and implementation of business object components. The main focus of the workshop was: What design patterns will allow implementation of business objects as plug and play components? How can these components be assembled into domain specific frameworks? What are the appropriate architectures/mechanisms as distributed object systems? What for implementing these frameworks organisational and development process issues need to be addressed to successfully deliver these systems? Is this approach an effective means for deploying enterprise application solutions? The third annual workshop (OOPSLA'97) was jointly sponsored by the Accredited Standards Committee X3H7 Object Information Management Technical Committee and the Object Management Group (OMG) Business Object Domain Task Force (BODTF) for the purpose of soliciting technical position papers relevant to the design and implementation of Business Object Systems.

Object-oriented analysis and design (OOAD) has over the years, become a vast field, encompassing such diverse topics as design process and principles, documentation tools, refactoring, and design and architectural patterns. For most students the learning experience is incomplete without implementation. This new textbook provides a comprehensive introduction to OOAD. The salient points of its coverage are: • A sound footing on object-oriented concepts such as classes, objects, interfaces, inheritance, polymorphism, dynamic linking, etc. • A good introduction to the stage of requirements analysis. • Use of UML to document user requirements and design. • An extensive treatment of the design process. • Coverage of implementation issues. • Appropriate use of design and architectural patterns. • Introduction to the art and craft of refactoring. • Pointers to resources that further the reader’s knowledge. All the main case-studies used for this book have been implemented by the authors using Java. The text is liberally peppered with snippets of code, which are short and fairly self-explanatory and easy to read. Familiarity with a Java-like syntax and a broad understanding of the structure of Java would be helpful in using the book to its full potential.

Software -- Software Engineering.

Object-Oriented Information Engineering: Analysis, Design, and Implementation discusses design, both its object-oriented and traditional development and analysis, on which the book gives much focus. The book begins with an introduction to information engineering and its phases, object-oriented information engineering, and object orientation. The text then moves on to more specific topics, such as business information requirements; detailed object modeling; business functions and subject areas; and individual object behaviors and object interactions. The book also explains the integration and validation of analysis models; object structure designs; and system designs and its different applications. The text is recommended for undergraduates and practitioners of computer and/or information engineers who want to learn more about object-oriented design, its relation with traditional design, and its analysis. The book is also for those who wish to contribute and conduct further studies in the field of object-oriented design.

A rigorous and practical framework for modeling business systems Pares object modeling down to its core concepts, making it easier than ever. Twelve object collaboration patterns that address virtually any business scenario Powerful techniques–not fancy notation! Streamlined Object Modeling presents the first rigorous, practical framework for object modeling complex business domains, rules, and systems. Three world-renowned leaders in object development have pared object modeling down to the core concepts for all business domains, business rules, and business services. Starting from the first principles of "object think," the authors offer a fully integrated approach to building, validating, and critiquing object models. Coverage includes: Proven principles and techniques for successfully modeling the structure and operations of any business domain. Guidelines for finding and associating objects, assembling object models, and distributing system behavior among objects. Rigorous methods for discovering, organizing, and implementing business rules around objects. Twelve all-encompassing "collaboration patterns"–what they represent, how they relate, and how to apply them. Five kinds of business rules, three types of services, and six categories of properties completely specify object-oriented business requirements From start to finish, the book makes extensive use of examples drawn from real commercial applications. To illustrate how streamlined object modeling flows from analysis to code, it also presents a complete case study derived from a real-world application, and implemented in two leading object-oriented languages-Java, and the Squeak implementation of Smalltalk.

"Domain-Driven Design" incorporates numerous examples in Java-case studies taken from actual projects that illustrate the application of domain-driven design to real-world software development.