Goldfish bowl: "A goldfish bowl on patterns" |
Ballroom C |
This goldfish bowl will allow some experienced pattern-masters and you the audience to discuss how patterns are working today in the OO community. Some questions to be answered include: How are patterns effective for you? How do you use them in your organisation? Who writes them? Who are they most useful for? Who finances them? Where do they come from? How are they stored and accessed? Are they at the architectural, design and/or programming level? Is their use enforced? Bring your own points of discussion and make your way to the stage in this highly interactive session. Moderator: Bruce Anderson, IBM OTP Invited Participants:
|
|
Technical Papers: |
Exhibit Hall A |
| Chair: Eric Jul, University of Copenhagen "Visualizing Dynamic Software System Information through
High-level Models" |
|
Practitioner Reports: |
Ballroom A |
| Prototyping &
Architecture Session Leader: Patrick Logan, GemStone Corp. "The Mount Sinai Human Resources Case Management System:
an Example of Rapid Application Development in a Java Environment" The Mount Sinai Human Resources Case Management system was developed using several new software development tools and techniques. The system was developed with 2 FTE developers in six months as a series of iterative prototypes, starting with paper-based mock-ups, proceeding to executable throw away prototypes developed in Java, and ending in a deployed three-tiered architecture with a Java client, an Oracle server, and Symantec's dbAnywhere middleware product. This article describes the tools and techniques used to develop the system and some lessons learned from the project. "A Look Behind Internet's First Digital
Trading Cards" This paper outlines our experience in developing a challenging and fun system; the first limited edition digital trading cards to be offered on the Internet. The challenges included implementing the required complex mechanism for a deceptively simple looking product in a very short amount of time, with a limited amount of resources. The product needed to be deliverable and maintainable over the Internet and the system needed to offer a high level of security, scalability, and reliability. We developed the first phase of the project by utilizing an object oriented architecture and a database system, RASE (Rapid Systems Engineering) tools, and design patterns as well as a variety of multimedia development tools. "An Improved Smalltalk Application Server
for a Web-based Business Solution" The project team started with a corporate human resources application which was used to log, approve, and reimburse employee purchases. The application was fully distributed with the client functionality delivered across the corporate intranet. The server portion contained the domain model and was constructed using a combination of VisualWorks Smalltalk and Gemstone Smalltalk for persistence. The application scalability was adequate but limited. The report describes a revision to the application architecture which improved the response time of the application and gave it the potential to support a greater number of concurrent users. The revised architecture uses a series of new management objects, most notably the Session Broker and the Session Manager, to respond to variations in the demand pattern. In addition, another series of objects, representing the remaining components of the application architecture were separated from the domain model with the intention of producing a generalized framework applicable to other business problems. "Architecture for a Production-quality
Java Application" The Avalon project was aimed at providing an interactive entertainment experience for consumers used to television-like entertainment via a Java applet. To accommodate a typical consumer's low-bandwidth, no-storage, high security requirements, we prototyped and then rebuilt our applet environment. This report will cover the following technical areas: the designs used in order to deliver production-quality applications over the consumer internet, the use of Java in reality, and lessons learned in the process. |
|
Practitioner Reports: |
Ballroom B |
| Transitioning to OO Session
Leader: TBD "Automated
Testing of an Object Application" The system used for administrating the pension benefits for teachers in the province of Ontario is an example of a feature-rich intelligent agent participating in a highly complex business process. In addition to the challenge of developing the application itself, of major concern was the system testing for validation of the initial deployment and for regression testing of subsequent releases for maintenance, upgrades, and extensions. To that end, an automated testing system was also developed with the requirement that it be accessible to business experts: not just software developers. It also had to be usable at all stages of the business application's development: not just with a complete product but also at an object class and instance level. This paper illustrates how object design enabled software developers, testers, and business analysts to work together throughout the development and deployment process to improve quality and productivity. "Lessons Learned: Transitioning COBOL
Programmers to OO" Typical object technology (OT) courses provided by professional trainers are one week long and most managers expect developers to be productive after attending one or more of these courses. Yet, it is broadly acknowledged within the object-oriented (OO) community that the OT learning curve is anywhere from 6-18 months. Conventional wisdom concludes a longer-than-normal training program transitioning to object technology is better which we refute based on a recent experience. We attempt to provide a few primary reasons for the contradiction to conventional wisdom and offer suggestions to improve your experience. "An Integration Architecture for
Implementation of the DoD Computerized Patient Record" U.S. Military health systems include a very large set of heterogeneous systems involving multiple organizations, care environments, computing environments, and health care elements. Systems integration and interoperability in such an environment presents a series of challenges, particularly with respect to architectural and semantic mismatch. This report focuses on a particular logical architecture that facilitates meeting these challenges incrementally, on a requirements-based, mission increment by mission increment basis. Initial team experience in following the architecture and future implementation plans is also discussed. |
|
Last updated 09 October 1998 10:19:11