Please use this identifier to cite or link to this item:
|Title:||Improving Software Product Line Engineering using AOP, LEL and UML|
|Abstract:||Software product lines are a booming approach to software reuse. Software product lines enable modular and huge scale reuse. The success of a software product line approach directly depends on how well feature variability within the group is implemented and managed all through the development lifecycle. In order to obtain the profit of software product lines, their designs need to be stable. To an important scope, the development of product lines is difficult by crosscutting concerns. It is generally assumed that aspect-oriented programming promotes better modularity and changeability of product lines than conventional variability mechanisms. Aspect-oriented programming may grow the design level of software, the reusability of components and the implementation of separation of concerns. Modeling variability is a center problem in software product line engineering. So modeling variability with aspect-oriented techniques is a clear idea which has been exploited before to some scope. Report discusses a new approach aspect oriented technique for the modularization of concerns that facilitates variability implementation, management and tracing by aspect-oriented technique. The relationship between variability, commonality and variation point in a software product line bears similarities to the relationship between crosscutting concerns, core concerns and joint point in aspect oriented modeling respectively. One of goal of this research is to improve software product line using aspects so as to enable software reuse, design functionality and flexible extensibility of requirements. Domain analysis has been recommended by many researchers in the reuse research as an essential process for achieving successful reuse. Reuse of products, processes and all kinds of knowledge has been recognized as an objective in software engineering, in order to build up reliable and high quality software systems on schedule and within budget. This duality of issues calls for methods as domain analysis to systematically build reusable elements. In this report a detailed description of domain analysis including domain analysis phases, domain analysis methods and quality attributes of domain analysis methods are given. There are many methods for domain analysis during reuse. These include FODA, JODA, ODM, DSSA and DADP methods. They all differ in the quality attributes they support. The quality attributes supported by two domain analysis methods namely joint object oriented domain analysis and domain analysis|
|Appears in Collections:||Masters Theses@CSED|
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.