Main.HomePage History

Hide minor edits - Show changes to markup

February 12, 2007, at 10:26 AM by 134.206.10.138 -
Changed line 28 from:
 
This work is conducted in the context of the framework program (accord-cadre) between INRIA and France Telecom R&D, and is partially funded by France Telecom under the external research contract 46131097.
to:
This work is conducted in the context of the framework program between INRIA and France Telecom R&D, and is partially funded by France Telecom under the external research contract 46131097.
February 12, 2007, at 10:25 AM by 134.206.10.138 -
Changed line 28 from:
 
This work is conducted in the context of the framework program (<<accord-cadre>>) between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
to:
 
This work is conducted in the context of the framework program (accord-cadre) between INRIA and France Telecom R&D, and is partially funded by France Telecom under the external research contract 46131097.
February 12, 2007, at 10:24 AM by 134.206.10.138 -
Changed line 28 from:
 
' This work is conducted in the context of the framework program (<<accord-cadre>>) between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
to:
 
This work is conducted in the context of the framework program (<<accord-cadre>>) between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
February 12, 2007, at 10:23 AM by 134.206.10.138 -
Changed line 28 from:
 
'This work is conducted in the context of the framework program ("accord-cadre") between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
to:
 
' This work is conducted in the context of the framework program (<<accord-cadre>>) between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
February 12, 2007, at 10:23 AM by 134.206.10.138 -
Changed line 28 from:
 
'This work is conducted in the context of the framework program ("accord-cadre") between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
'
to:
 
'This work is conducted in the context of the framework program ("accord-cadre") between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
February 12, 2007, at 10:22 AM by 134.206.10.138 -
Changed lines 24-28 from:
to:

About

 
'This work is conducted in the context of the framework program ("accord-cadre") between INRIA and France Telecom R&D. This work is partially funded by France Telecom under the external research contract #46131097.
'
January 31, 2007, at 02:52 PM by 84.97.21.8 -
Changed line 11 from:
to:
January 24, 2007, at 01:36 PM by 134.206.10.123 -
Changed lines 1-4 from:

Welcome the Fractal Aspect Component (FAC) project!

About the Fractal Aspect Component project

to:

Welcome the Fractal Aspect Component (FAC) project!

January 21, 2007, at 02:01 PM by 84.97.27.170 -
Changed lines 9-11 from:
From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not w.r.t. other components, an aspect connector or a regular component binding is employed.
to:
From an architectural point of view, and with the help of Fractal ADL, FAC advocates the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component. Then, whether the concern is crosscutting or not w.r.t. other components, an aspect connector or a regular component binding is employed.
January 20, 2007, at 10:09 PM by 84.97.27.170 -
Changed lines 11-12 from:

Documentation on FAC

to:
January 20, 2007, at 10:07 AM by 84.97.27.170 -
Changed line 26 from:
  • A Safe Aspect-Oriented Programming Support for Component-Oriented Programming. N. Pessemier, L. Seinturier, L. Duchien and T. Coupaye. In 11th International ECOOP Workshop on Component-Oriented Programming (WCOP'06), Nantes, France, July 2006. BIB
to:
  • A Safe Aspect-Oriented Programming Support for Component-Oriented Programming. N. Pessemier, L. Seinturier, L. Duchien and T. Coupaye. In 11th International ECOOP Workshop on Component-Oriented Programming (WCOP'06), Nantes, France, July 2006. BIB
January 20, 2007, at 10:05 AM by 84.97.27.170 -
Added line 26:
  • A Safe Aspect-Oriented Programming Support for Component-Oriented Programming. N. Pessemier, L. Seinturier, L. Duchien and T. Coupaye. In 11th International ECOOP Workshop on Component-Oriented Programming (WCOP'06), Nantes, France, July 2006. BIB
January 20, 2007, at 10:04 AM by 84.97.27.170 -
Changed lines 9-10 from:
From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed.
to:
From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not w.r.t. other components, an aspect connector or a regular component binding is employed.
January 20, 2007, at 10:03 AM by 84.97.27.170 -
Changed lines 7-8 from:
By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

to:
By unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

January 18, 2007, at 10:05 PM by 84.97.27.170 -
Changed lines 7-10 from:
By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.
to:
By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

January 18, 2007, at 10:05 PM by 84.97.27.170 -
Changed lines 5-7 from:
FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.
to:
FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

January 18, 2007, at 10:04 PM by 84.97.27.170 -
Changed lines 8-10 from:

_--By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

to:
By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.
January 18, 2007, at 10:04 PM by 84.97.27.170 -
Changed lines 5-10 from:

_--FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed._--

to:
FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

_--By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed.
January 18, 2007, at 10:03 PM by 84.97.27.170 -
Changed lines 5-10 from:
FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.
By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.
From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed.
to:

_--FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed._--

January 18, 2007, at 10:03 PM by 84.97.27.170 -
Changed lines 5-10 from:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed.

to:
FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.
By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.
From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed.
Changed line 25 from:
  • A Model for Developing Component-based and Aspect-oriented Systems. N. Pessemier, L. Seinturier, T. Coupaye and L. Duchien. In 5th International Symposium on Software Composition (SC'06), Vienna, Austria, March 2006. BIB
to:
  • A Model for Developing Component-based and Aspect-oriented Systems. N. Pessemier, L. Seinturier, T. Coupaye and L. Duchien. In 5th International Symposium on Software Composition (SC'06), Vienna, Austria, March 2006. BIB
January 18, 2007, at 09:59 PM by 84.97.27.170 -
Changed lines 1-2 from:

[ Welcome the Fractal Aspect Component (FAC) project!]

to:

Welcome the Fractal Aspect Component (FAC) project!

January 18, 2007, at 09:58 PM by 84.97.27.170 -
Changed lines 1-3 from:

Welcome to Fractal Aspect Component project!

to:

[ Welcome the Fractal Aspect Component (FAC) project!]

About the Fractal Aspect Component project

January 18, 2007, at 09:57 PM by 84.97.27.170 -
Changed lines 8-9 from:

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, the fact that the concern is crosscutting or not w.r.t. other components is decided by the use of aspect connector instead of regular component binding.

to:

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, whether the concern is crosscutting or not, w.r.t. other components, an aspect connector or a regular component binding is employed.

January 18, 2007, at 09:55 PM by 84.97.27.170 -
Changed lines 8-9 from:

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows each concerns, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, the fact that the concern is crosscutting or not w.r.t. other components is decided by the use of aspect connector instead of regular component binding.

to:

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows to each concern, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, the fact that the concern is crosscutting or not w.r.t. other components is decided by the use of aspect connector instead of regular component binding.

January 18, 2007, at 09:54 PM by 84.97.27.170 -
Changed lines 17-22 from:

Download

  • Download the Julius implementation of FAC
  • CVS repository
to:

Download & CVS

  • Forge access to download and CVS.
January 18, 2007, at 09:51 PM by 84.97.27.170 -
Changed lines 4-5 from:

FAC is an extension of the to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

to:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

Changed line 12 from:
  • New in Fractal? Please visit the first.
to:
  • New in Fractal? Please visit the Fractal web site first.
January 18, 2007, at 09:50 PM by 84.97.27.170 -
Added line 12:
  • New in Fractal? Please visit the first.
January 18, 2007, at 09:40 PM by 84.97.27.170 -
Changed lines 24-25 from:
  • A Model for Developing Component-based and Aspect-oriented Systems.
N. Pessemier, L. Seinturier, T. Coupaye and L. Duchien. In 5th International Symposium on Software Composition (SC'06), Vienna, Austria, March 2006. BIB
to:
  • A Model for Developing Component-based and Aspect-oriented Systems. N. Pessemier, L. Seinturier, T. Coupaye and L. Duchien. In 5th International Symposium on Software Composition (SC'06), Vienna, Austria, March 2006. BIB
January 18, 2007, at 09:38 PM by 84.97.27.170 -
Changed lines 8-26 from:

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows each concerns, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, the fact that the concern is crosscutting or not w.r.t. other components is decided by the use of aspect connector instead of regular component binding.

to:

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows each concerns, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, the fact that the concern is crosscutting or not w.r.t. other components is decided by the use of aspect connector instead of regular component binding.

Documentation on FAC

Download

  • Download the Julius implementation of FAC
  • CVS repository

Publications about FAC

  • A Model for Developing Component-based and Aspect-oriented Systems.
N. Pessemier, L. Seinturier, T. Coupaye and L. Duchien. In 5th International Symposium on Software Composition (SC'06), Vienna, Austria, March 2006. BIB
January 18, 2007, at 09:32 PM by 84.97.27.170 -
Changed lines 4-6 from:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

to:

FAC is an extension of the to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

From an architectural point of view, and with the help of Fractal ADL, FAC allows the multidimensional decomposition of concerns with components. FAC allows each concerns, crosscutting or not, to be represented as a plain component or an architecture of plain components. Then, the fact that the concern is crosscutting or not w.r.t. other components is decided by the use of aspect connector instead of regular component binding.

January 18, 2007, at 09:28 PM by 84.97.27.170 -
Changed lines 4-5 from:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development.

to:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development (AOSD). A discussion on why there is a need for an unification of CBSD and AOSD can be found in this page.

January 18, 2007, at 09:25 PM by 84.97.27.170 -
Changed lines 4-6 from:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development.

to:

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development.

By Unifiying components and aspects, no disctinction is made between the behavior of an aspect and a plain component. As a result, only a new composition mechanism is introduced to support aspect-oriented composition. This aspect composition is realized by an aspect connector in Fractal. The aspect connector is composed of several concepts wich we detail in the overview of FAC.

January 18, 2007, at 04:13 PM by 134.206.10.123 -
Changed lines 1-12 from:

Welcome to PmWiki!

A local copy of PmWiki's documentation has been installed along with the software, and is available via the documentation index.

To continue setting up PmWiki, see initial setup tasks.

The basic editing page describes how to create pages in PmWiki. You can practice editing in the wiki sandbox.

More information about PmWiki is available from http://www.pmwiki.org .

to:

Welcome to Fractal Aspect Component project!

FAC is an extension of the Fractal component model to support AOP. It is built as an unification of Component-Based Software Development (CBSD) and Aspect-Oriented Software Development.