Requirements Elicitation Technique Selection

2009 ◽  
pp. 79-95
Author(s):  
Miguel I. Aguiree-Urreta ◽  
George M. Marakas
Keyword(s):  
System Development ◽  
Development Project ◽  
Requirements Elicitation ◽  
Development Projects ◽  
Critical Stage ◽  
Common Structure ◽  
Organizational Literature

Requirements elicitation has been recognized as a critical stage in system development projects, yet current models prescribing particular elicitation techniques are still limited in their development and application. This research reviews efforts aimed at addressing this issue, and synthesizes a common structure consisting of project contingencies, elicitation techniques, logic of fit, and a success construct, arguing for the need to more comprehensively study and organize each. As a first step in this research, models drawn from organizational literature are used to categorize project contingencies into dimensions dealing with their impact on the uncertainty and equivocality of the overall development project.

scholarly journals A viability criterion for computer system development projects

1984 ◽  
Vol 15 (3) ◽  
pp. 144-149
Author(s):  
J. Mende
Keyword(s):  
Computer System ◽  
Cost Of Capital ◽  
System Development ◽  
Development Project ◽  
Development Projects ◽  
Organizational Growth ◽  
Net Worth ◽  
Development Costs ◽  
Processing Cost ◽  
Informational Value

A manager facing the decision whether to proceed with a proposed computer system development project needs to determine whether its benefits are worth more than its costs. This can be done by applying a simple mathematical formula to calculate the project's 'net worth', as the sum of the annual benefits obtainable during the system's life span, less its development costs. The formula recognizes that a system's annual benefit, comprising enhanced informational value plus reduction In data processing cost, will change as a result of obsolescence, cost of capital, organizational growth and learning.

Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation

2017 ◽  
Vol 02 (02) ◽  
pp. 1750007
Author(s):  
Taiga Mitsuyuki ◽  
Kazuo Hiekata ◽  
Takuya Goto ◽  
Bryan Moser
Keyword(s):  
Software Development ◽  
Process Simulation ◽  
System Development ◽  
Development Project ◽  
Development Projects ◽  
Software Project ◽  
Conditional Response ◽  
Agile Process ◽  
Requirement Changes ◽  
The Impact

For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.

scholarly journals Mapping Situations within a System Development Project.: An Intervention Perspective on Organizational Change

1984 ◽  
Vol 13 (179) ◽  
Author(s):  
Giovan Francesco Lanzara ◽  
Lars Mathiassen
Keyword(s):  
Organizational Change ◽  
System Development ◽  
Development Project ◽  
Development Projects ◽  
Cognitive Constructs ◽  
Mapping System

<p>In this paper we propose some new tools for mapping system development projects. Maps -- as we propose them -- contain descriptions and interpretations of project situations:they are helpful in collecting and organizing relevant, often neglected knowledge and experience.</p><p>Maps are cognitive constructs containing pictures that actors make of the situation in which they are involved. They are typically made within the situation or transposed from similar situations and are used by the actors themselves as tools for exploring, for learning, for increasing awareness, for inventing solutions to problems, and for undertaking action.</p>

Requirements Elicitation for Complex Systems

2011 ◽  
pp. 27-52
Author(s):  
Chad Coulin ◽  
Didar Zowghi
Keyword(s):  
Complex Systems ◽  
System Development ◽  
Requirements Elicitation ◽  
Development Projects ◽  
Research Practice ◽  
Academic Environments ◽  
Current Trends ◽  
The Future ◽  
Future Direction

This chapter examines requirements elicitation for complex systems from a theoretical and practical perspective. System stakeholders, requirements sources, and the quality of requirements are presented with respect to the process, including an investigation into the roles of requirements engineers during elicitation. The main focus of the chapter is a review of existing requirements elicitation techniques and a survey of current trends and challenges. It is concluded with some views on the future direction of requirements elicitation in terms of research, practice and education. It is the intention of the authors that readers of this chapter will be sufficiently informed on the concepts, techniques, trends, and challenges of requirements elicitation to then apply this knowledge to system development projects in both industrial and academic environments.

Research On Risks Encountered By Institutions In European Development Project

2014 ◽  
Vol 1 (1) ◽  
pp. 517-520
Author(s):  
Diana Elena Ranf ◽  
Elida-Tomiţa Todăriţa ◽  
Dănuţ Dumitru Dumitraşcu
Keyword(s):  
Development Project ◽  
Development Projects ◽  
Application Form ◽  
Structural Funds ◽  
Development Opportunity ◽  
Centre Region ◽  
European Development ◽  
Way Of Thinking ◽  
Risk Categories ◽  
Implementation Stage

AbstractEuropean funds are a development opportunity for the Romanian organizations. The research in the article aims to identify the main risk categories that the beneficiaries from Centre Region have faced, and also the effects of not considering certain risk categories in the stage of filling out the application form and also in the implementation stage of the projects have had on the development of these projects. Identifying how the organisations have managed projects during the development projects 2003-2013 finds its usefulness in the following period that is knocking on our doors: 2014-2020 that should find us better prepared and more capable of proving seriousness and professionalism. Therefore, training in projects should not end once the structural funds have been attracted, but it should be regarded as destined to modernize our way of thinking and actions in helping organisations develop their businesses.

STAKEHOLDERS, SPATIAL LOCATIONS AND TIME HORIZONS IN AN EXTENDED SOCIAL COST-BENEFIT ANALYSIS: A CASE OF PIPALPANKHA WATER RESOURCE PROJECT

2009 ◽  
Vol 11 (02) ◽  
pp. 245-265 ◽  
Author(s):  
P. RAM BABU ◽  
NALLATHIGA RAMAKRISHNA
Keyword(s):  
Decision Making ◽  
Water Resource ◽  
Social Cost ◽  
Cost Benefit Analysis ◽  
Cost Benefit ◽  
Development Project ◽  
Development Projects ◽  
Benefit Analysis ◽  
Time Horizons ◽  
Spatial Locations

Cost-Benefit Analysis (CBA) has been serving as an important tool for decision making with regard to the development projects involving large investments. The Social Cost-Benefit Analysis (SCBA) is an extension of the CBA to certain social impacts, which hitherto were not measured. As the impacts of development projects on ecology and environment assumed importance, measuring the corresponding costs and benefits also began to assume significance. With the advancement in economic valuation techniques over time, measurement could be done and the framework of SCBA has been extended to incorporate the same. Moreover, unlike the CBAs, which do not account for the distributional aspects, the SCBA can potentially account for these. This paper presents a case study of extending the SCBA framework to include social and environmental impacts of a large water resource development project in India. It emphasises the distribution of project benefits and costs over stakeholders, spatial locations and time horizons so as to demonstrate the utility of extended SCBA in project decision making. It is observed that both the numeraire measure i.e. cost-benefit ratio, as well as the distributional analysis present a favourable case for the project.

scholarly journals Suppliers’ software development project start-up practices

2017 ◽  
Vol 10 (4) ◽  
pp. 880-896
Author(s):  
Helena Merikoski ◽  
Paula Savolainen ◽  
Jarmo J. Ahonen
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Project ◽  
Cycle Phase ◽  
Development Projects ◽  
Content Type ◽  
Business Context ◽  
Software Development Project ◽  
Business Goals ◽  
Start Up

Purpose The purpose of this paper is to present a life cycle phase of a software development project which is substantial for the success of the project. This paper visualizes the project start-up phase from suppliers’ perspective. Design/methodology/approach The method is a theory building from case studies. The data were collected from three software supplier firms by conducting process modeling separately in each firm. Findings The study resulted in a model of a supplier’s software project start-up which includes start-up practices and involved roles. The results indicate that project start-up is an integral and structured phase of project life cycle, which influences the execution of a software development project, especially from the supplier’s perspective in the project business context. Research limitations/implications The study focuses on the start-up phase of software development projects delivered to external customers. Therefore, developed project start-up model is applicable as such in software supplier firms. Practical implications The project start-up model presented in this paper indicates that project start-up is a complex and multi-dimensional activity in a supplier firm. This study suggests that if the project start-up phase is clearly defined, planned and followed in a supplier firm, it reduces confusion and miscommunication among the people involved in the project and helps to achieve the business goals of a project. Originality/value This study emphasizes that it is necessary to make a distinction between the perspectives of the customer and the supplier when studying projects in the project business context. The findings contribute the new knowledge for managing outsourced software development projects.

Sign in / Sign up

Export Citation Format

Share Document