Evidence is mounting that aspect-oriented programming is useful for (re-)structuring the many concerns that software is designed to address. Many of these concerns often arise in the problem domain, and, therefore, there is a growing effort to examine 'early aspects' - to identify and represent concerns that arise during software requirements engineering and design, and to determine how these concerns interact. But can one seek to identify aspects too early? While identifying concerns during requirements elicitation may indeed be profitable, the notion of crosscutting concerns, indeed of crosscutting requirements, may only make sense when elements of a solution also begin to be explored. There are two consequences of this: a case for more interleaving of the processes of requirements engineering and design, and a case for the explicit development of specifications that map the problem and solution structures. We elaborate and discuss this thesis, and offer an alternative research agenda for aspect-oriented requirements engineering.

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Finkelstein, A. and Sommerville, I., "The Viewpoints FAQ", BCS/IEE Software Engineering Journal, 11 (1): 2-4, January 1996.
	2	Gregor Kiczales , Erik Hilsdale, Aspect-oriented programming, Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering, September 10-14, 2001, Vienna, Austria
	3	Bashar Nuseibeh , Jeff Kramer , Anthony Finkelstein, A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification, IEEE Transactions on Software Engineering, v.20 n.10, p.760-773, October 1994  [doi>10.1109/32.328995 ]
	4	Bashar Nuseibeh, Weaving Together Requirements and Architectures, Computer, v.34 n.3, p.115-117, March 2001
	5	D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972  [doi>10.1145/361598.361623]
	6	Polya, G., How to Solve It, Princeton University Press, 1945.
	7	Peri Tarr , Harold Ossher , William Harrison , Stanley M. Sutton, Jr., N degrees of separation: multi-dimensional separation of concerns, Proceedings of the 21st international conference on Software engineering, p.107-119, May 16-22, 1999, Los Angeles, California, United States
	8	Peri Tarr , William Harrison , Harold Ossher , Anthony Finkelstein , Bashar Nuseibeh , Dewayne Perry, Workshop on multi-dimensional separation of concerns in software engineering (workshop session), Proceedings of the 22nd international conference on Software engineering, p.809-810, June 04-11, 2000, Limerick, Ireland  [doi>10.1145/337180.337827]
	9	Awais Rashid , Ana Moreira , Joāo Araújo, Modularisation and composition of aspectual requirements, Proceedings of the 2nd international conference on Aspect-oriented software development, p.11-20, March 17-21, 2003, Boston, Massachusetts  [doi>10.1145/643603.643605]

• Open signaling for ATM, internet and mobile networks (OPENSIG'98) ACM SIGCOMM Computer Communication Review   29, 1
  Andrew T. Campbell ,  Irene Katzela ,  Kazuho Miki ,  John Vicente
  
  
• Active bridging ACM SIGCOMM Computer Communication Review   27, 4
  D. Scott Alexander ,  Marianne Shaw ,  Scott M. Nettles ,  Jonathan M. Smith
  
  
• Active electronic mail Proceedings of the 2002 ACM symposium on Applied computing
  S. Karnouskos ,  A. Vasilakos
  
  
• Object-oriented database management system for process control systems—development and evaluation Proceedings of the 1999 ACM symposium on Applied computing
  Ryuji Wakizono ,  Toshikazu Kawamura ,  Takehiko Tsuchiya ,  Takahiro Hatanaka ,  Tatsuji Tanaka
  
  
• Data structures for quadtree approximation and compression Communications of the ACM   28, 9
  Hanan Samet