Desmond D'Souza

Biography

Desmond D'Souza is senior vice president of component-based development at Computer Associates, responsible for defining methods, tools, and architectures for effective component-based software engineering. He heads up CA's Catalysis Technology Center. He is co-author and developer of the CATALYSIS method, published by Addison Wesley in 1998. He has worked with software technology since 1981, developed object systems since 1985, and worked on modeling and design methods and tools since 1990. Desmond is a frequent invited speaker at companies internationally. He may be contacted at dsouzad@acm.org

OUTLINE:

Introduction: What problem are we setting out to address?
Components: What they are, how they interact, how to describe them.
Architecture: What it is, why it is essential, how to describe it.
Frameworks: The basic idea.
Reuse: What it is (and is not), reuse at all levels.
Systematic Reuse with Frameworks: Making models, designs, code reusable.
Summary: Catalysis in Perspective.

Abstract 1: Catalysis - Systematic Components and Frameworks with UML

The Catalysis method (www.catalysis.org) provides a simple and consistent use of UML to:

(a) treat "objects" and "use-cases" in a fractal manner, from business to code.
(b) specify and design components using "types" and "collaborations"
(c) use a "plug-in" framework approach from requirements patterns, through architecture and design, to code.
(e) define component architectures based on an extensible "kit" of architectural modeling elements.

BACKGROUND: Attendees should be familiar with object modeling and programming, design patterns as defined by Gamma et al, and use-cases. Those wanting to use patterns with UML, seeking a consistent component-based approach from requirements to code, and using languages like Java, will particularly benefit.

Abstract 2: JavaBeans: Specification, Design, Test with UML/Catalysis

Components / JavaBeans / Modeling
Component standards like Java Beans promise standard re-usable parts that can be easily composed. To be replaceable and scalable, the behavior of a Bean should be described in a way which is abstract (permit many implementations) and precise (clear, unambiguous, a basis for qualification and test). Moreover, designing to a component architecture such as JavaBeans offers (and requires) a new level of abstraction in describing and composing parts. This tutorial will describe an approach to the precise and systematic specification of a Java Bean, extended to its design, implementation, and test. Background: Attendees must be familiar with Java, Java Beans basics.