Jon Siegel, OMG's Vice President of Technology Transfer, heads OMG's
technology transfer program with the goal of teaching the
technical aspects and benefits of the Model Driven Architecture (MDA)
based on OMG's industry-standard Unified Modeling Language (UML) and
its foundation standards: the MetaObject Facility (MOF), XML Metadata
Interchange (XMI), and the Common Warehouse Metamodel (CWM).
Siegel's scope also includes OMG's industry-standard
middleware, the Common Object Request Broker Architecture (CORBA), and
the Object Management Architecture (OMA) comprised of the CORBAservices,
the CORBAfacilities, and the Domain specifications in vertical markets
ranging from life sciences and telecommunications to manufacturing and
financial systems. In this capacity, he presents tutorials, seminars,
and company briefings around the world, and writes magazine articles,
web pages, and books including the popular "CORBA 3 Fundamentals
and Programming" and "Quick CORBA 3". With OMG since 1993,
Siegel previously chaired the Domain Technology Committee responsible
for OMG specifications in the vertical domains.
Dr. Siegel moved to OMG after twelve years with Shell Development Company, the
research arm of Shell Oil, where his last position was in the Computer Science
Research Department. Siegel's background includes extensive experience in distributed
computing, object-oriented software development, and geophysical computing, as
well as theoretical and computational work done at Argonne National Laboratory.
While at Shell, he served as that company's representative to OMG, playing an
active role in several OMG subgroups, chairing the Life Cycle Services Evaluation
working group and the End User SIG, and serving on the Object Services Task Force.
He holds a doctoral degree in Theoretical Physical Chemistry from Boston University.
Model Driven Architecture® (MDA®) defines an application fundamentally
in terms of its business functionality and behavior instead of its technology,
and supports a sound IT architecture that lowers the barriers to enterprise
integration. Software development in the MDA starts with a technology-independent
model of an application, built in the Unified Modeling Language (UML).
This model remains stable as technology evolves, extending and thereby
maximizing software ROI. MDA development tools, already available from
vendors, convert the technology-independent model to a working implementation
on virtually any middleware platform: Web Services, XML/SOAP, EJB, C#/.Net,
OMG's own CORBA, or others. Portability and interoperability are built
into the architecture. OMG's industry-standard modeling specifications
support the MDA: UML, now at Version 2.0; the MetaObject Facility (MOF);
the Common Warehouse Metamodel (CWM); and XML Metadata Interchange (XMI).
Version 2.0 of UML enhances Component, Architectural, Behavioral, and
Business Modeling, and integrates representation of structure and behavior.
OMG Task Forces organized around industries including Telecommunications,
Finance, Manufacturing, Biotechnology, and others use the MDA to standardize
facilities in their domains.
Michael Hirsch (Zühlke
Moving from a Plan Driven Culture to Agile Development
20 May @ 11:00 AM
Hirsch is partner and software engineering consultant with
Zuehlke Engineering AG in Zurich, Switzerland. He has been active in
software development for more than 20 years in various roles,
including project manager, software architect and software
developer. His current interests are agile development methods,
software architectures, and open source software. He holds a degree
Electrical Engineering from HTL Bregenz in Austria and a degree in
Software Engineering from HTL Bern in Switzerland.
Abstract: Plan driven
cultures are characterized by a strong belief in the
plannability and predictability of software development projects. The
SEI-CMM, software process improvement initiatives, and software
metrics programs are some of the hallmarks of this school of
thought. The more recent trend towards agile development places the
emphasis on constantly adapting to a project's changing goals rather
than on detailed upfront planning. The majority of reports from
pracitioners of agile development are positive and confirm the
advantages of this approach. However, moving from a plan driven
culture to agile development is not easy. Making the transition
requires changes to many established practices and may even touch core
values held by stakeholders. Areas affected are requirements and
change management, user involvement, willingness to take on
responsibility, contract management, and the ability to live with many
uncertainties. This talk looks at what it takes to make the transition
and presents lessons learned from organizations and projects which
have successfully completed the switch to agile development.
Eric Brechner (Microsoft
Corp.) Journey of Enlightenment & the Evolution of Development
20 May @ 2:00 PM
Brechner is the director of development excellence for Microsoft Corporation.
His group is responsible improving the processes and
practices of software development across Microsoft through the
application of Human Performance Technology. Prior to his current
assignment, Eric was director of development training, and the head
development for an Office shared feature team. Before joining
Microsoft in 1995, Eric was a Senior Principal Scientist at The Boeing
Company where he worked in the areas of largescale visualization, computational
geometry, network communications, data-flow languages,
and software integration.
He was the principal architect of FlyThru(tm),
the walkthrough program for the 20GB, 500+ million polygon model of the
aircraft. Eric has also worked in computer graphics and CAD for Silicon Graphics
Inc., GRAFTEK, and the Jet Propulsion Laboratory. He holds five patents, a BS
and MS in mathematics, and a Ph.D. in applied mathematics from Rensselaer Polytechnic
Abstract: Like many
software companies, Microsoft has been doing distributed
application development for many years. However, recent changes in the
market have altered the rules, both in terms of customer expectations
and programming models for ubiquitous interconnected smart
devices. These changes have provoked two dramatic shifts in the way we
develop software. The first is the creation and use of the .NET
Framework as a simple, secure, and robust platform for device
independent software development, data transfer, and
communications. The second is an agile yet highly disciplined approach
to designing, testing, implementing, and verifying our software which
presumes all bugs are unacceptable and must be found and fixed early
before they impact internal groups, external partners, and eventually
our customers. This paper discusses the nature and impact of these two
dramatic shifts to the development practices at Microsoft.
Roy T. Fielding (Day Software) Software Architecture in an Open Source World
20 May @ 2:00 PM
T. Fielding is the chief scientist of Day Software. He is best known
for his work in developing and defining the modern World Wide
Web infrastructure by authoring the Internet standards for HTTP and
URI, defining the REST architectural style, and as co-founder and
former chairman of the Apache Software Foundation.
Dr. Fielding received his Ph.D. degree in Information and Computer
Science from the University of California, Irvine, and serves as an
elected member of the W3C Technical Architecture Group.
Abstract: In spite
of the hype and hysteria surrounding open source software development,
there is very little that can be said of open source in general. Open
source projects range in scope from the miniscule, such as the thousands
of non-maintained code dumps left behind at the end of class projects,
dissertations, and failed commercial ventures, to the truly international,
with thousands of developers collaborating, directly or indirectly, on
a common platform. One characteristic that is shared by the largest and
most successful open source projects, however, is a software architecture
designed to promote anarchic collaboration through extensions while at
the same time preserving centralized control over the interfaces.
This talk features a survey of the state-of-the-practice in open source
development in regards to software architecture, with particular emphasis
on the modular extensibility interfaces within several of the most successful
projects, including Apache httpd, Eclipse, Mozilla Firefox, Linux kernel,
and the World Wide Web (which few people recognize as an open source
project in itself). These projects fall under the general category of
collaborative open source software development, which emphasizes community
aspects of software engineering in order to compensate for the often-volunteer
nature of core developers and take advantage of the scalability obtainable
through Internet-based virtual organizations.