19,175 research outputs found

    Iterative criteria-based approach to engineering the requirements of software development methodologies

    Get PDF
    Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous

    Using contextual goal models for constructing situational methods

    Get PDF
    Situation and intention are two fundamental notions in situational method engineering (SME). They are used to assess the context of an ISD project and to specify method requirements in this context. They also allow defining the goals of the method chunks and the conditions under which they can be applied. In this way, the selection and assembly of method chunks for a particular ISD project is driven by matching situational method requirements to method chunks’ goals and context descriptions. In this paper we propose the use of contextual goal models for supporting all SME steps. Our approach is based on iStar2.0 modeling language that we extend with contextual annotations.Peer ReviewedPostprint (author's final draft

    A situational approach for the definition and tailoring of a data-driven software evolution method

    Get PDF
    Successful software evolution heavily depends on the selection of the right features to be included in the next release. Such selection is difficult, and companies often report bad experiences about user acceptance. To overcome this challenge, there is an increasing number of approaches that propose intensive use of data to drive evolution. This trend has motivated the SUPERSEDE method, which proposes the collection and analysis of user feedback and monitoring data as the baseline to elicit and prioritize requirements, which are then used to plan the next release. However, every company may be interested in tailoring this method depending on factors like project size, scope, etc. In order to provide a systematic approach, we propose the use of Situational Method Engineering to describe SUPERSEDE and guide its tailoring to a particular context.Peer ReviewedPostprint (author's final draft

    Contingent Information Systems Development

    Get PDF
    Situated approaches based on project contingencies are becoming more and more an important research topic for information systems development organizations. The Information Services Organization, which was investigated, has recognized that it should tune its systems development approaches to the specific situation. A model has been developed, dealing with the matching between prevailing contingency factors and the preconditions of already existing situated approaches. Furthermore, a generic process model for systems development, including the information systems operations stage, is proposed. This model makes it possible to derive from it specific systems development strategies. A number of basic development strategies, specific for the Information Services Organization, are described. Preconditions, specific for this organization, are added to the standard situated approaches

    Understanding requirements engineering process: a challenge for practice and education

    Get PDF
    Reviews of the state of the professional practice in Requirements Engineering (RE) stress that the RE process is both complex and hard to describe, and suggest there is a significant difference between competent and "approved" practice. "Approved" practice is reflected by (in all likelihood, in fact, has its genesis in) RE education, so that the knowledge and skills taught to students do not match the knowledge and skills required and applied by competent practitioners. A new understanding of the RE process has emerged from our recent study. RE is revealed as inherently creative, involving cycles of building and major reconstruction of the models developed, significantly different from the systematic and smoothly incremental process generally described in the literature. The process is better characterised as highly creative, opportunistic and insight driven. This mismatch between approved and actual practice provides a challenge to RE education - RE requires insight and creativity as well as technical knowledge. Traditional learning models applied to RE focus, however, on notation and prescribed processes acquired through repetition. We argue that traditional learning models fail to support the learning required for RE and propose both a new model based on cognitive flexibility and a framework for RE education to support this model

    Unpacking the curvilinear relationship between negative affectivity, performance, and turnover intentions: The moderating effect of time-related work stress

    Get PDF
    This study explores the relationships of negative affectivity with two frequently studied outcome variables job performance and turnover intentions. Conventional wisdom holds that negative affectivity has a harmful impact on both job performance and intentions to leave; however, we propose a more nuanced perspective using empirical and theoretical arguments (e.g., self-regulation theory) to highlight the functional effects of negative affectivity. To test our hypotheses, we collected self-reported and supervisor-reported data from seven organizations in Pakistan. The findings based on data collected from 280 employees show that while negative affectivity is detrimental for job performance, this effect is mitigated as negative affectivity increases. It further shows that the linear negative main effect of negative affectivity on job performance is more pronounced when employees experience less time-related work stress. Finally, the curvilinear relationship between negative affectivity and turnover intentions is moderated by time-related work stress. The relationship has a U shape at high levels of time-related work stress, whereas at low levels it has an inverted U shape. A discussion of the limitations, future research, and implications for theory building and practice conclude the article
    • …
    corecore