1 / 6

Aspect-Oriented Web Development vs. Non Aspect-Oriented Web Development

Aspect-Oriented Web Development vs. Non Aspect-Oriented Web Development A. M. Reina, J. Torres, and M. Toro Languages and Systems Department University of Seville (Spain) {reinaqu, jtorres, mtoro} @lsi.us.es Index What are we doing? Where are we going? Our problems. Discussion topics.

lotus
Télécharger la présentation

Aspect-Oriented Web Development vs. Non Aspect-Oriented Web Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Aspect-Oriented Web Development vs. Non Aspect-Oriented Web Development A. M. Reina, J. Torres, and M. Toro Languages and Systems Department University of Seville (Spain) {reinaqu, jtorres, mtoro} @lsi.us.es AAOS 2003 - Darmstadt, Germany

  2. Index • What are we doing? • Where are we going? • Our problems. • Discussion topics. AAOS 2003 - Darmstadt, Germany

  3. WEB DESIGN METHODOLOGIES AOP WEB DEVELOPMENT NON-AOP WEB DEVELOPMENT NAVIGATION SEPARATION OF CONCERNS AspectJ + JSP + HTML Cocoon + XML What are we doing? Our beginnings Currently AAOS 2003 - Darmstadt, Germany

  4. XML COMPONENT TECHNOLOGY WEB DESIGN METHODOLOGIES SEPARATION OF CONCERNS NAVIGATION Where are we going to? AAOS 2003 - Darmstadt, Germany

  5. Our Problems • Separate navigation completely. Is this possible? • For web applications: • Is it better a high-level language, but more restricted, based on XML to specify web-related concepts?. • How can we mix the component-based proposal (Cocoon) with the aspect-oriented one? • Will these initial ideas help us with navigation? • At design level, most of the proposals are very near to implementation level, and they are too connected to the join points defined by Aspect/J. What if I would like to work with other proposals for separating concerns? AAOS 2003 - Darmstadt, Germany

  6. Discussion Topics • What are the differences between non-functional requirements and aspects/concerns at analysis requirements level? Are they the same thing? • What about an standard representation of aspects at design level? There are many proposals, why not an agreement? AAOS 2003 - Darmstadt, Germany

More Related