Sharif Digital Repository

Situational Method Engineering (SME)1approaches help construct bespoke software development processes according to the specifications of the project at hand, but they are time-consuming and costly. A Software Process Line (SPrL) tackles this problem by allowing software processes to be constructed for specific project situations through reusing core process assets. Model-Driven Development (MDD) has been used for automating SPrL Engineering (SPrLE); however, existing model-driven SPrLE methods are deficient as to their coverage of key MDD features. We propose a novel model-driven SPrLE approach that aims to address these shortcomings; it can be regarded as a framework that specifies the... 

Process-centered Software Engineering Environments, or PSEEs, are intended for the definition, modification, and enactment of software process models, they thus bring software development processes into effect. Even though research efforts in process-centered software engineering abound, PSEE technology has not received the attention that it deserves. In order to create a concise but effective and practically applicable evaluation framework for PSEEs, this paper first presents a survey of PSEEs and highlights the current state of the art of the technology. The PSEEs which have been reviewed herein have been regarded as software systems, and as such, have been characterized in terms of their... 

A Software Process Line (SPrL) is potentially suitable for constructing software development methodologies by reusing core assets. However, adopting this approach without prior assessment of its suitability can lead to failure. The aim of this paper is to identify a set of requirements that can be used for deciding whether to adopt the SPrL approach in an organization. Identification of the requirements was accomplished in two stages: the characteristics important in method tailoring were first identified via a Systematic Mapping Study (SMS) that focused on analyzing 43 primary studies; the degree of importance of the identified characteristics was then determined using a questionnaire... 

Repetitive decomposing of the objective concept hierarchically, developed for design involves a human intentional activity, ranging from management to physical works. This model proved the empirical rules in Industrial Engineering. In addition to these "design" process characteristics, the "test" process is found to be a defect attenuating process with the attenuation rate of its error rate of the second kind. As these are applicable to any software process, they are very useful  

The need for constructing software development methods that have been tailored to fit specific situations and requirements has given rise to the generation of general method fragments, or process patterns. Process patterns can be seen in some third-generation integrated methodologies (such as OPEN) and in Method Engineering approaches where they are used as process components. They have also been presented as components in generic software development lifecycles where they represent classes of common practices in a specific domain or paradigm; object-oriented process patterns are well-known examples. Agile methodologies, however, are yet to be thoroughly explored in this regard. We provide a... 

Scrum is currently the most widely used agile methodology. However, it is regarded as a framework rather than a concrete process. Unfortunately, the resources available on Scrum do not explicitly define its variable parts and do not offer proper guidance on how to resolve those variabilities. Process (re)configuration is thus left to Scrum Retrospective sessions; this can delay the vital decisions that can significantly improve the process before problems arise. This paper aims to address the problems associated with configuring/reconfiguring Scrum by identifying all the variabilities (variation points) in the Scrum framework, along with the situations where a variation point can be resolved... 

Scrum is currently the most widely used agile methodology. However, it is regarded as a framework rather than a concrete process. Unfortunately, the resources available on Scrum do not explicitly define its variable parts and do not offer proper guidance on how to resolve those variabilities. Process (re)configuration is thus left to Scrum Retrospective sessions; this can delay the vital decisions that can significantly improve the process before problems arise. This paper aims to address the problems associated with configuring/reconfiguring Scrum by identifying all the variabilities (variation points) in the Scrum framework, along with the situations where a variation point can be resolved... 

The Software Product Line (SPL) approach is a paradigm for systematic reuse of software products, and a Software Factory is a SPL aimed at the industrialization of software development. Based on the notion that a software/RE process can be developed via an engineering process (much akin to engineering other types of software), this research aims to provide a feature-based RE process factory to develop RE processes based on the characteristics of the project at hand (project situation). In our approach, the project situation is modeled as the problem domain through using the i* modeling language (resulting in a situation model). A feature model can encapsulate all the features in an SPL;... 

Business intelligence (BI) is a managerial concept helping managers and organizations to manage information and make factual decisions. Some have introduced Business Intelligence as a process of turning data into information and then into knowledge. This concept has become a popular trend for businesses interested in adding value to their decision making processes. Measurement of maturity in implementing Business Intelligence process in organizations is considered a critical issue. Business intelligence like software development is a process, which expressed in terms of components such as artifacts and workflows. Capability Maturity Model Integrated (CMMI) is developed to define different... 

Model-Driven Development (MDD) is a promising approach to software development, mainly due to the pivotal role of models in its process, and the high potential it provides for automated model/software generation. Since software processes can themselves be considered as software, any technique or approach applied in the context of software development is also of potential use in the development of software development processes. Accordingly, the MDD approach can potentially be applied in the context of Situational Method Engineering (SME) - a branch devoted to the study of developing bespoke software development processes and methods based on the specific characteristics of the development... 

Various agile software development methodologies, practices, and techniques have been proposed in the last decade; some present novel ideas, while many are simply made up of tasks and techniques borrowed from prominent agile methodologies. Each of these methodologies prescribes a set of practices and techniques which are deemed appropriate for application in a specific context. However, there exists no single method which fits all project situations. This has resulted in the advent of Situational Method Engineering (SME) approaches, which are used for developing software methodologies that are tailored to fit the specific circumstances of the project situation at hand. Since tool support has... 

Information systems are expected to satisfy increasingly ambitious requirements, while reducing time-to-market has become a primary objective. This trend has necessitated the advent of development approaches that are better equipped and flexible enough to cope with modern challenges. Model-Driven Architecture (MDA) and Situational Method Engineering (SME) are approaches addressing this requirement: MDA provides promising means for automating the software process, and revitalizes the role of modeling in software development; SME focuses on project-specific methodology construction, mainly through assembling reusable method fragments (process patterns) retrieved from a method base. We provide... 

OMG's Model Driven Architecture (MDA) has deeply influenced modern-day software development, not only by providing promising means for automating the software process, but also through revitalizing the role of modeling in software development, the importance of which had been neglected during the recent euphoria over lightweight development methods. However, MDA's need to remain reasonably abstract means that it is more a software development approach rather than a standalone methodology, and therefore needs methodology support to be practically useful. Several MDA-based methodologies exist today, yet the need remains for the definition of an instantiable MDA-based development process. We...