in requirements engineering, everything is an aspect
This keynote is intended to provoke a discussion on crosscutting in early stages of software development. Both proponents and opponents of Early Aspects are invited to attend. The speaker works in requirements engineering (RE) and is not directly involved with work on Early Aspects. Nevertheless, RE is certainly early. The speaker believes that in RE, one never sees any cross-cutting concerns, but there are plenty of concerns there and these are all requirements. The speaker is of the view that, in the early stages, requirements are not well enough structured, and that, any concern can be identified as crosscutting as opposed to not crosscutting. Consequently, it is hard to define which concerns are crosscutting and which are not. Everything is just a concern. Nevertheless, there will certainly be crosscutting concerns later when the required system is built.
requirements engineering crosscutting concerns non-crosscutting concenrs