Sharif Digital Repository

Aspect-Oriented Software Development (AOSD) concentrates on separation of global cross-cutting concerns, or aspects. The weaknesses of Object-Oriented Software Development (OOSD) in localizing orthogonal concerns simultaneously leads to distributing them across several modules, and thereby creating modules that have to deal with various concerns. This usually results in poor modularization and difficulties in tracing certain requirements (especially nonfunctional requirements) to their implementations. The AOSD approach determines the common aspects that exist across modules created through OOSD, and modularizes them. Thus, AOSD takes the next step in creating modular software. Applying this... 

The adaptive nature of agile processes and their conformance to the turbulent nature of business and organizational environments has been greeted with enthusiasm by both project and stakeholder communities. Through deviating from conventional linear and plan-driven frameworks, Agility aims at accommodating the dynamicity of its target environment at the process level during the project lifecycle. This deviation from standard frameworks confronts process management and project framework activities with key challenges. While existing frameworks and standards provide adequate support for linear process management, the agile approach lacks a coherent framework that defines and outlines process... 

Software Product Line Engineering (PLE) and Agile Software Development are two leading approaches in the software industry. Despite the inherent differences between the two approaches, they are intended to fulfill common goals, such as: Reducing time to market, increasing customer satisfaction, promoting product quality, managing changes in requirements, and lowering the costs of development. In addition, each of them has certain positive features which address the other’s weaknesses. As a result, it seems reasonable to integrate the two approaches in order to produce a combined method which fulfills the common goals while addressing the weaknesses. Agile Product Line Engineering (APLE) is a... 

Methodology engineering is a branch of software engineering which deals with the design, development, and modification of methodologies, and the techniques and tools for developing information systems. Methodology engineering requirements demand the support of Computer Aided Methodology Engineering (CAME) tools. Recently, method engineering focus has shifted towards Situational Method Engineering (SME); i.e. context-specific methodology development. The emergence of SME approaches has brought about various methods for methodology development; including ad hoc, paradigm-based, extension-based and assembly-based approaches. In the assembly-based strategy, appropriate method chunks are... 

Software Reuse, the use of (pre)existing artifacts to create new systems, can reduce development costs and improve software quality and productivity. With a primary investment, Software Product Line facilitates a systematic reuse of the common parts of an specific domain in developing similar systems of that domain. On the Contrary, Agile Methods who value working software over comprehensive documentations and such investments is not done, lack reuse in developing similar systems. Here the question arises: why do we completely or almost miss such reuse when the only focus is on creating working software? When such investments or additional works like documentation are not done? Is there any...