topical media & game development

talk show tell print

object-oriented programming

This chapter has dealt with business objects, business applications and the issues involved in business process redesign. Since business process redesign may be motivated by changes in technology, we also discuss the migration from legacy applications.

Business objects -- SanFrancisco framework


slide: Section 11.1: Business objects -- SanFrancisco framework

In section 1, we discussed the need for business objects and looked at the San Francisco framework, which aims to provide a generic solution to creating business applications.

Business process modeling


  • logistics-based modeling
  • business process simulation
  • example -- requests for loans

slide: Section 11.2: Business process modeling

In section 2, we looked at the issues involved in business process modeling, which we consider as a prerequisite for business process redesign. We dealt with the simulation of the logistic aspects of business processes and concluded with a small example.

Object-oriented simulation


  • simulation classes -- event, entity, generator, resource, queue
  • event scheduling strategy -- conditional, passive, pending
  • dining philosophers -- events versus processes

slide: Section 11.3: Object-oriented simulation

In section 3, we treated object-oriented simulation in somewhat more detail. An overview was given of useful simulation classes. We discussed event scheduling strategies, and looked at the classic dining philosophers example, both from an event-based simulation perspective and a process-based simulation perspective.

Visualization support


  • So many users, so many perspectives
  • DIVA -- distributed visualization architecture

slide: Section 11.4: Visualization support

In section 4, we looked at interactive information visualization as a means to support business process redesign and decision making. An overview was given of the DIVA software architecture, which allows for distribution, user perspectives and collaboration.

Migrating from legacy applications


  • fat versus thin clients -- screen scraping
  • Web-aware applications -- wrapping the legacy

slide: Section 11.5: Migrating from legacy applications

We concluded, in section 5, with a discussion of the opportunities to migrate from legacy applications to a modern, object-oriented, Web-aware architecture.

(C) Æliens 04/09/2009

You may not copy or print any of this material without explicit permission of the author or the publisher. In case of other copyright issues, contact the author.