| Panel: "Question Time! about Use Cases" | Ballroom B |
Following a format from the British television program, "Question Time," our moderator will question four expert panelists with differing views, to expose their views and their reasons for differing. There are no position statements, the 90-minute panel is filled by discussing eight questions. The questions are submitted in advance by the public and audience members. The moderator picks eight questions that will be interesting and help tease apart subtle issues and differences between the panelists. For each question, all four panelists respond, moderated by the panel moderator, a well known (English!) OO figure. The questioner then makes a brief reply, and there is a brief period of comments from the floor. If you would like to submit a question for this Panel session, please send it to Martin Fowler (fowler@acm.org). Moderator: Martin Fowler, Independent Consultant Panelists: |
|
| Technical Papers: | Exhibit Hall A |
| Chair: Scott Smith, Johns Hopkins University "Making the Future Safe for the Past: Adding Genericity
to the Java Programming Language" |
|
| Practitioner Reports: | Ballroom A |
| Frameworks Session
Leader: Douglas C. Schmidt, Washington University "Building an Object Relational Database Access
Layer" This report discusses the experience we gained designing and implementing an object-oriented application using a relational database. In particular, it focuses on the object relational database access layer. The database access layer handles the transition of the object-oriented paradigm to concepts of the relational database. It hides database specific information and guarantees the persistence and consistency of application object data. The database access layer's architecture is described in detail. Performance requirements and design and implementation problems and their solutions are discussed. Finally, some general experiences and observations refering to an object-oriented project are reported. We found the object relational database access layer has been a well performing approach to combine the object-oriented paradigm with a relational database. It also proved to be easy to handle. "Business Object Framework as an Enabler
of Business Application Development, an Experience in Enterprise Software
Engineering" Business systems are hard to develop because the developer must become expert in a number of diverse domains. A Business Object Framework (BOF) can make it possible for novice object developers to be employed effectively on complex business system development projects. This is possible because the BOF separates the business logic from the user interface and the object persistence domains thus greatly simplifying development. This finding is particularly important given the expectation of widespread adoption of CORBA (and the current definition of a CORBA-based BOF by the OMG) and the recent release of the Enterprise Java Beans specifications. It is our belief that as the industry moves to BOF development environments, our experiences using a BOF provide a glimpse of the way most developers will be working in the near future. Our experience demonstrates that once you have a well-designed business object framework in place, you can build high quality and complex business systems with complete (OO) novices. "Deploying an Application Framework and
its Applications" IFA Informatik has developed an application framework for building web-based server applications. This framework has been used to create several applications for large customers. We want to tell some of the things that happened in the last two years, since the framework evolved and applications using it were built and deployed. We have learned that there is a substantial difference between developing and using an application framework within a small group of qualified developers and giving the framework to customers and their development organizations. The information we are going to present has the nature of an Anti-Pattern. We feel it important to show our observations, what we did right and where our measures didn't reach expectations. Nevertheless, we still believe in building and using application frameworks, but we learned that organizing their use and evolution in a real-world environment is hard. |
|
Last updated 16 October 1998 10:31:35/Teresa Warwaruk