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

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

Early aspects: aspect-oriented requirements engineering and architecture design

This paper reports on the third Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, which has been held in Lancaster, UK, on March 21, 2004. The workshop included a presentation session and working sessions in which the particular topics on early aspects were discussed. The primary goal of the workshop was to focus on challenges to defining methodical software development processes for aspects from early on in the software life cycle and explore the potential of proposed methods and techniques to scale up to industrial applications

A Knowledge-based Decision Support System for RP&M Process Selection

Due to the large variety of RP&M material/machines and the. strengths/weaknesses associated with different RP&M processes, the decision·to select a suitableRP&M system becomes increasingly difficult. This paper presents a knowledge-based approach for the selection ofsuitable RP&M material/machine to meet specific. requirements ofRP&Mapplications. The system receives input data on the CAD modelandthe user's specifications,andgenerates outputs that provide the most appropriate combination ofRP&Mmaterial/machine.·Optimal orientations, together with estimated manufacturing time and cost, are considered and given in the final outcome to help the user make the choice.Mechanical Engineerin

Modeling the object-oriented software process: OPEN and the unified process

A short introduction to software process modeling is presented, particularly object-oriented modeling. Two major industrial process models are discussed: the OPEN model and the Unified Process model. In more detail, the quality assurance in the Unified Process tool (formally called Objectory) is reviewed

Developing a goal-oriented SDI assessment approach using GIDEON - the Dutch SDI implementation strategy - as a case study

In 2008, the Dutch government approved the GIDEON document as a policy aiming at the implementation of the National Spatial Data Infrastructure (NSDI) in the Netherlands. The execution of GIDEON should take place by pursuing seven implementation strategies which lead to the achievement of the GIDEON goals. GIDEON also expresses the need to monitor the progress of implementing its strategies and realization of its goals. Currently, the work has been started on monitoring the GIDEON implementation strategies. However, there is still a lack of knowledge and methods to monitor GIDEON goals realization. The challenge is to come up with an approach to assess to what extent these goals are achieved. As a response to the challenge of assessing the GIDEON goals, this paper explores the possibility of using the Multi-view SDI assessment framework (Grus et al., 2007). This paper presents and discusses the method that applies the Multi-view SDI assessment framework, its indicators and measurement methods to create a GIDEON assessment approach. The method of creating a GIDEON assessment approach consists of several procedural steps: formulating specific GIDEON objectives, organizing a one-day workshop involving focus group of specific stakeholders responsible for creation and execution of NSDI, asking the workshop participants to select from a long list those indicators that best measure the achievement of each GIDEON goals. The key step of GIDEON approach is a one-day workshop. The workshop participants represented all organizations that cooperated and/or created GIDEON. The workshop consisted of two parts: first part explained the context of a challenge of assessing GIDEON, second part included participants activity to select and come to the consensus on the list of indicators that would best measure GIDEON goals realization. Additionally, the participants were asked to evaluate and express feedback on the usefulness of the method of creating GIDEON assessment approach. The results show that several indicators that relate to specific SDI goals could be selected by a significant number of workshop participants. The indicators that have been selected are not the final ones yet, but provide a guideline and form a base of what has to be measured when assessing GIDEON goals. Involving the representatives of all parties committed to GIDEON into the process of GIDEON assessment approach creation will strengthen its robustness and acceptance. The results of the feedback form filled by each participant show that the presented method is useful or very useful to create GIDEON assessment approach. Additionally, some of the participants provided already their own indicators which are very specific for Dutch SDI monitoring.The method presented in this research, assuming that SDI goals are defined and the organizations that participate in SDI creation are known, can be applied in any other country to develop country-specific and practical SDI assessment approach

A Taxonomy for a Constructive Approach to Software Evolution

In many software design and evaluation techniques, either the software evolution problem is not systematically elaborated, or only the impact of evolution is considered. Thus, most of the time software is changed by editing the components of the software system, i.e. breaking down the software system. The software engineering discipline provides many mechanisms that allow evolution without breaking down the system; however, the contexts where these mechanisms are applicable are not taken into account. Furthermore, the software design and evaluation techniques do not support identifying these contexts. In this paper, we provide a taxonomy of software evolution that can be used to identify the context of the evolution problem. The identified contexts are used to retrieve, from the software engineering discipline, the mechanisms, which can evolve the software software without breaking it down. To build such a taxonomy, we build a model for software evolution and use this model to identify the factors that effect the selection of software evolution\ud mechanisms. Our approach is based on solution sets, however; the contents of these sets may vary at different stages of the software life-cycle. To address this problem, we introduce perspectives; that are filters to select relevant elements from a solution set. We apply our taxonomy to a parser tool to show how it coped with problematic evolution problems