Addressing Non-functional Requirements for Embedded Applications with Platform Based Aspect Design

Aspect Oriented Programming (AOP) and Aspect Oriented Modeling (AOM) have been proposed as development methodologies when dealing with non-functional requirements for embedded systems, which usually represent cross-cutting concerns in relation to a "functional" application. In this paper, based on the observation that non-functional aspects need to be developed from a system-level perspective, we note that application-level AOP is not sufficient to address non-functional requirements (as it usually ignores execution platform constraints). We then propose a development process that considers AOM in conjunction with two standard development approaches for embedded systems: Model Based Development and Platform Based Design. The proposed methodology is illustrated by means of an example with logical execution time requirements.