Abstract
The actual realization of a design language form has been revealed to be non-trivial. Most of the design languages are very much tailored towards a specific application or application domain. Moreover, with the exception of very few hardly any of these language notations have been used outside their own research environment. The development of a more generic aspect oriented design language requires a wider and more thorough look at the requirements. This paper examines the design notation issues and discusses how it fulfils the requirements in principle and design and consequently would lead to a general purpose AOSD design language (AOSDDL) that will map AOSD design notations to the existing AOP languages.