Aspect-Oriented Requirement Engineering (AORE) is an emerging software engineering paradigm with increasing attention from academic as well as industrial communities. AORE aims at the systematic identification, modularization, composition and analysis of crosscutting concerns that manifest in requirements. It is believed that systematically managing crosscutting concerns early on at the requirement engineering stage can provide valuable insight at the architecture design and implementation stages and can help identify and thus manage crosscutting concerns at these stages. Moreover, identifying crosscutting concerns in requirements can help to reveal the scope of each concern in a software system, to detect potential conflicts between concerns and to facilitate trade-off negotiation early on. Hundreds of papers regarding AORE have been published in AORE communities. However, few of them address crosscutting concerns in real world requirements. Whether the proposed AORE approaches are productive when applied to real world requirements is unknown. In this thesis, we conduct an AORE case study consisting of an experiment using a real world software requirement specification in order to examine how crosscutting concerns present in real world requirement documents, explore the difference between crosscutting concerns in requirements and crosscutting concerns in code, and reason whether identifying and thus managing crosscutting concerns from real world requirements is a productive practice. / Thesis (Master, Computing) -- Queen's University, 2009-09-21 15:09:27.262

Requirement engineering is the most important phase within the software development phases since it is used to extract requirements from the customers which are used by the next phases for designing and implementation of the system. Because of its importance, this thesis focuses on the term aspect oriented requirement engineering, which is the first phase in aspect oriented software development used for the identification and representation of requirements gathered in the form of concerns. Besides the overall explanation of aspect oriented requirement engineering phase, detail attention is given to a specific activity within AORE phase called conflict resolution. Several techniques proposed for conflict resolution between aspects is discussed along with an attempt to give a new idea in the form of an extension of the already proposed model for conflict resolution. The need for extension to the already proposed model is justified by the use of a case study which is applied on both the models i.e. on the original model and on the extended model to compare the results. / Krav engineering är den viktigaste fasen inom mjukvaruutveckling faser eftersom det är användas för utvinning av krav från kunder som används av de följande faserna för utformning och genomförandet av systemet. På grund av dess betydelse, denna avhandling fokuserar på sikt aspekt orienterade krav på teknik, som är den första fasen i aspekt Orienten mjukvaran utveckling används för identifiering och representation krav som samlats in i form av oro. Förutom det övergripande förklaring av aspekt oriented Kravet tekniska fasen, detalj uppmärksamhet ges till en specifik verksamhet inom AORE fasen kallas konfliktlösning. Flera metoder som föreslås för konfliktlösning mellan aspekter diskuteras tillsammans med ett försök att ge en ny idé i form av en utvidgning av redan föreslagna modellen för konflikt resolution. Behovet av förlängning av redan föreslagna modellen är motiverad av att använda en fallstudie som appliceras på båda modellerna dvs i den ursprungliga modellen och om den utvidgade modell för att jämföra resultat. / faysal_hameed@hotmail.com, ijazbutt1@hotmail.com