OBJECT-ORIENTED PROGRAMMING, SYSTEMS, LANGUAGES and APPLICATIONS
 
 
Program
 


Program (2mb PDF)

Explore
  Invited Speakers
  Onward!
  Panels
  Workshops
Discover
  Research Papers
  Student Research Comp.
  Posters
  Doctoral Symposium
  Educators' Symposium
  Wiki Symposium
  Dynamic Lang. Symp.
Understand
  Tutorials
  Essays
  Practitioner Reports
  Demonstrations
Create
  DesignFest
  Lightning Talks
  FlashBoF
  Instant Arts School Exp.
 
Other Events
 
Resort Map (364kb PDF)
 
Resort Map (JPG)

 

 
Basket
 

view, help

"Use Cases Are Early Aspects"

 

 
Page
 

Printer-friendly

 
 
  > Tutorials > All Tutorials

 : Sunday Afternoon Tutorials (13:30 - 17:00) : Sunday : Requirements, Modeling, Architecture, and Design : Aspect Oriented Programming

Use Cases Are Early Aspects

Sunrise
Sunday, 13:30, half day

 


 
7·8·9·10·11·12·13·14·15·16·17·18·19·20·21

Ivar Jacobson, Ivar Jacobson Consulting
Pan-Wei Ng, Ivar Jacobson Consulting

Tutorial number: 12

Everyone talks about aspects—but most people think about them as a programming technique to deal with low level crosscutting concerns. We know that aspects can be applied to large scale projects, but how do you use them in real software development from requirements to code? With use cases of course! A strong parallel exist between use cases and aspects in that just as aspects cut across objects, so does use cases. Furthermore, use cases are "early aspects". They provide the means to model stakeholder concerns, even crosscutting ones. Thanks to aspect-orientation techniques, you can keep these use cases or early aspects separate from each other all the way to code. This works for features of many kinds, functional or non-functional or infrastructural or even platform specifics. In doing so, we take a new grasp on Model Driven Architecture. Each "aspect" of the design model (i.e. the platform specific model) is very much like an overlay as used for an overhead projector. You stack them up to produce the whole system. We added new constructs needed to UML to model these overlays. In this way, we formulate a simpler and more aspect-oriented approach to architecture.

Intermediate: Attendees should have some basic knowledge of aspects, use cases and UML

Ivar Jacobson, Ivar Jacobson Consulting:  Ivar Jacobson, Ph.D., is "the father" of many technologies including components and component architecture, use cases, modern business engineering, and the Rational Unified Process. He was one of the three amigos who originally developed the Unified Modeling Language. He is the principal author of five best-selling books on these methods and technologies, in addition to being the coauthor of the two leading books on the Unified Modeling Language. Ivar is founder of Ivar Jacobson International, which has offices around the world.

Pan-Wei Ng, Ivar Jacobson Consulting:  Pan-Wei Ng, Ph.D., plays multiple roles in Ivar Jacobson Consulting (IJC). As a member of the IJC Technology Office, Pan-Wei defines best practices in architecture, use cases, iterative development, business modeling, active software, and aspects. He develops materials for some of these best practices and conducts research in other best practice areas. Pan-Wei also actively works on customer accounts to enable companies and project teams to adopt these best practices quickly and safely. Pan-Wei works alongside practitioners and ensures that the best practices developed are both relevant and practical.

 
.