Convention Ctr Ballroom
Session A
Panel: B2B E-Commerce Integration A Tower of Babel?
Lougie Anderson, GemStone Systems (Moderator)
Chris Beall, Requisite Technology
Thomas Joseph, Tibco Software
Mary Loomis, Commerce One
Stewert Allen, webMethods
New standards and new standard bodies are popping up like mushrooms in the area of Business-to-Business (B2B) E-Commerce Integration (e.g. Rosetta Net, ebXML, tpaML). Standards in this area define data sharing/integration within industry verticals and between companies, enabling new e-commerce business applications that streamline everything from supply chain management to customer support. This panel will discuss the state-of-the-state in all this frenetic B2B e-commerce standards activity.
Convention Ctr 101, A, B, I, J
Session B
Papers: Development Tools
Chair: Peri Tarr, IBM T. J. Watson Research Center
OO tools and methods become more useful when they can help developers identify, decompose, manage, and ultimately integrate multiple, evolving concerns in software. For example, while OO addresses object concerns, developers may also have concerns like business rules, roles, features, and performance and distribution requirements, which cross-cut objects. The three papers in this session provide mechanisms for identifying, managing, and integrating different kinds of concerns in OO systems. The first paper describes techniques for rapidly identifying refactorings that reflect design changes. The second paper defines a means of modeling separate, potentially overlapping concerns in UML-based designs and then automatically translating those concerns into a composed implementation. The third paper focuses on facilitating the representation and dynamic integration of different code concerns.
Finding Refactorings via Change Metrics
Serge Demeyer, University of Antwerp
Stéphane Ducasse, University of Berne
Oscar Nierstrasz, University of Berne
Mapping UML Designs to Java
William Harrison, IBM T. J. Watson Research Center
Charles Barton, IBM T. J. Watson Research Center
Mukund Raghavachari, IBM T. J. Watson Research Center
PIROL: A Case-Study for Multidimensional Separation of Concerns in Software Engineering Environments
Stephan Herrmann, Technical University Berlin
Mira Mezini, Technical University Darmstadt
Convention Ctr 101, C thru H
Session C
Practitioner Reports: Building Object Models
Chair: Rebecca Wirfs-Brock, Wirfs-Brock Associates
Object models are a critical part of any project developing object-oriented software. (Even when separate models are not used, there is always an object model there in the code.) Models can help or hinder understanding of requirements and can guide or mislead software design. The first report presents lessons learned while building a series of models in finance. The second describes how architecture can feed back into business process design. The third tells how a generic object model was built following a published comprehensive ontology.
A Decade of Modeling Financial Vehicles
William Frank, Financial Systems Architects
Anil Karunaratne, Citigroup
Building nine object-oriented financial systems in eleven years, we evolved techniques for "financial vehicles" (bonds, contracts, real estate, racehorses). We specify each particular financial vehicle by combining objects that implement the fundamental ideas behind financial vehicles. These techniques produce designs that enable installed systems to accommodate new kinds of objects.
How Conceptual Systems Architecture Leads to Business Processes
Hernan Astudillo, Soluciones S.A.
While designing a global bank's Cash-Link, our clustering of non-functional properties suggested two "lobes." (1) "transactional": enabling payments among partners, with high availability, security, and geographical distribution. (2) "analytic": traditional database requirements. These purely architectural components coincided with business processes separately identified by business analysts. Architecture provided problem domain insight.
Building a Large-Scale Generic Object Model: Applying the CYC Upper Ontology to Object Database Development
Stephen Strom, FGM, Inc.
The CYC upper ontology is a publicly-available, AI-derived "model of everything", expressed in predicate logic. We have attempted to transform it into standard object model form (UML and Java), resulting in a flexible generic object model and insight into the creation of object models in general.
|