1. Patterns of Risk Management
Peter Davies. daviesp1@anz.com
ANZ Banking Group,
26/55 Collins St., Melbourne, 3000, Australia
Permission granted to reproduce this work verbatim in its entirety for non-commercial use.
Abstract
Risk management is performed in order to avoid risks or to mitigate
the impact of risks that may adversely impact the project. This paper identifies
four patterns that describe problems faced by project managers when performing
the risk management activities of identifying and quantifying risk. Each
pattern describes a problem that needs to be solved, the consequences in
which the problem exists, and a proposed solution that addresses the different
forces that need to be resolved in order for the solution to be effective.
2. A Pattern Language for a Federated Architecture
George Fernandez, Liping Zhao
{george, liping}@cs.rmit.edu.au
Department of Computer Science, Royal Melbourne Institute of Technology
Inji Wijegunaratne
injiw@au1.ibm.com
IBM GSA
Melbourne, Australia
Abstract
This article presents a small pattern language for implementing a distributed
federated computing infrastructure. A federated architecture intends to
mirror the structure of an organisation, providing better support for both
new and legacy applications in a distributed environment, and facilitating
data exchange between applications to support information integration.
Under this architectural form, an organisation’s information systems are
separated out into autonomous co-operating application clusters, each connected
to a message-oriented federal highway acting as the vehicle for inter-domain
communication. The federated approach intends to avoid unnecessary coupling
(in the distributed computing sense) by clustering highly interdependent
modules and applications into domains, and minimising the strength of inter-domain
connections. The pattern language introduced here outlines the federated
architectural form discussed in [11].
3. Model GUI Mediator
Andy Bulka
abulka@netspace.net.au
Abstract
A MGM object displays a portion of a software application’s data to
the user, and optionally allows that data to be altered by the user of
the application. MGM is specifically suited to the display of application
data in contemporary, off-the-shelf GUI control widgets within a modern
RAD (Rapid Application Development) IDE. The MGM design pattern empowers
a programmer to simulate “object-aware” controls using off-the-shelf GUI
controls.
4. The Actor-Spectator-Producer Pattern
Fethi A. Rabhi
School of Information Systems
The University of New South Wales
Sydney 2052 (AUSTRALIA)
f.rabhi@unsw.edu.au
and
Thibault Devillers
Excite Europe Ltd.
60 Charlotte Street
London W1P 1LS (UK)
tdevillers@excitecorp.com