Demeter Seminar

Subject: Demeter Seminar
Date: Sun Jan 20 2002 - 21:43:49 EST

Unusual Date and Time! Regular seminar on Friday.

All Demeter Seminar participants are invited to attend:

         Business Rules: A Microcosm of Requirements Engineering
                              Sol J. Greenspan

                          Thursday, January 24, 2002
                     11:00 a.m. Room 149 Cullinane Hall

at the end of message!

Demeter Seminar
Friday, Jan. 24, 10 - 12 am
149 Cullinane Hall
For Jan. 25, 2002

One talk and one discussion topic:

Speaker: Doug Orleans
Incremental Programming With Extensible Decisions

Preview of PL Day talk and his talk at the First
Conference on Aspect-Oriented Software Design.

Discussion topic: From Demeter to AspectJ

2002 is the 10 year anniversary of the first publication
on Adaptive Programming. The join point model back
then was simpler: we had only method call join points
and control to select method calls within specific method bodies.
And a key restriction was that the join points were in

AspectJ has generalized this basic join point model
to arbitrary user-written
method calls and other kinds of join points (like field accesses).
To facilitate the expression of sets of join points
AspectJ uses another Demeter technique: structure-based
wildcards. A structure-based wildcard selects succinctly a subset
of nodes in a graph. Two AspectJ examples are:
(1) A+ (modulo a class graph) selects all
subclasses of a class. (2) cflow(A) (modulo a call graph) selects
all join points reachable from A.

We will discuss how the join points needed in DemeterJ
are expressed in AspectJ and we will discuss what else
from the Demeter experience should be added to AspectJ.


         Business Rules: A Microcosm of Requirements Engineering
                              Sol J. Greenspan

                          Thursday, January 24, 2002
                     11:00 a.m. Room 149 Cullinane Hall

 Business rules represent policies, procedures and practices of an
 enterprise (such as a commercial business, government agency, or
 educational institution) that guide and constrain the enterprise's
 way of doing business. To get the full benefits of business rules,
 one needs an approach to representing and managing the business rules
 through their full lifecycle, from acquisition through deployment and
 evolution. This talk describes a framework and methodology for
 modeling an enterprise, its business rules, and the decision
 structures involved in business rules analysis and generation. This
 work demonstrates the possibility of automated support of the
 business rules lifecycle by automatically generating business rules
 from the modeled information along with data representing domain
 experience. A business rules development tool was implemented to
 illustrate and demonstrate the feasibility of the approach.
 Business rules can be viewed as special kinds of enterprise
 requirements that are characterized by their business orientation and
 their propensity for change. The business rules lifecycle thus
 serves as a useful microcosm, or test bed, for studying some very
 challenging issues in Requirements Engineering: 1) bridging the
 traditional gap between business needs and system requirements, and
 2) enabling rapid system modification in response to changing
 The talk reviews some principles of requirements modeling that carry
 over as well to the business rules context, describes the research
 trajectory that has led to the work on business rules, presents the
 business rules approach along with examples from industrial
 experience, and poses challenges for future research directions.

 Host: Carole Hafner

This archive was generated by hypermail 2b28 : Sun Jan 20 2002 - 21:43:50 EST