The Waterfall Model in Large-Scale Development

Petersen, Kai; Wohlin, Claes; Baca, Dejan

doi:10.1007/978-3-642-02152-7_29

Cited by 137 publications

(87 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This problem has spurred researchers to identify the challenges that can compromise the success of large-scale projects and to define methodologies and guidelines able to support the RE process in such projects. In the remainder of this section, we analyze the challenges identified in other studies [4,38,54,57,67,68] and discuss their impact on the TAS 3 project. Then, we investigate the guidelines proposed in those studies to address the challenges in Sect.…”

Section: Related Workmentioning

confidence: 99%

“…Further, these changes may produce traceability challenges and lead to confusion about which version of the requirements should be implemented and by whom [54]. Scope changes had a minimal impact on the TAS 3 project for two reasons.…”

Section: Related Workmentioning

confidence: 99%

“…The requirements engineering process may take too long or the scope of the requirements may be too large for the rest of the project to handle [54]. In TAS 3 the requirements engineering phase was initially too short, since the project was architecture driven.…”

Section: Related Workmentioning

confidence: 99%

“…The main reason for which project planning is not considered in these studies (with the exception of Petersen et al [54] who argue that ''waterfall model'' practices are not suitable for large projects) is that RE is recognized as a fundamental phase of the software development process. On the other hand, gap analysis has not been taken into account in other studies since their focus is on projects whose ultimate goal is to deploy a software product rather than develop innovation.…”

Section: Related Workmentioning

confidence: 99%

See 3 more Smart Citations

Requirements engineering within a large-scale security-oriented research project: lessons learned

Gürses

Seguran²,

Zannone

2011

Requirements Eng

View full text Add to dashboard Cite

Requirements engineering has been recognized as a fundamental phase of the software engineering process. Nevertheless, the elicitation and analysis of requirements are often left aside in favor of architecture-driven software development. This tendency, however, can lead to issues that may affect the success of a project. This paper presents our experience gained in the elicitation and analysis of requirements in a large-scale security-oriented European research project, which was originally conceived as an architecture-driven project. In particular, we illustrate the challenges that can be faced in large-scale research projects and consider the applicability of existing best practices and off-the-shelf methodologies with respect to the needs of such projects. We then discuss how those practices and methods can be integrated into the requirements engineering process and possibly improved to address the identified challenges. Finally, we summarize the lessons learned from our experience and the benefits that a proper requirements analysis can bring to a project.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Requirements engineering within a large-scale security-oriented research project: lessons learned

Gürses

Seguran²,

Zannone

2011

Requirements Eng

View full text Add to dashboard Cite

show abstract

“…Roadmapping, in turn, lays out those investments over time. Projects from the portfolio plan or roadmap are then fed into new product development processes such as the stage-gate process [8,9] and waterfall development processes [10]. Creating product family maps that leverage a series of platforms (product, technology, brand, etc.)…”

Section: Introductionmentioning

confidence: 99%

Design Roadmapping: A Framework and Case Study on Planning Development of High-Tech Products in Silicon Valley

Kim

Chung

Beckman

et al. 2016

Journal of Mechanical Design

View full text Add to dashboard Cite

We propose a framework for design roadmapping that parallels existing product roadmapping and technology roadmapping processes. It leverages three needs we have observed in organizations as they use existing roadmapping processes: (1) to focus on development of customer and user experiences (UX), not just on features; (2) to increase engagement of designers early in the planning process; and (3) to provide a means for rapidly responding to changes in the environment. Design roadmapping is an attempt to reconcile differences that arise when customer/user needs are not considered simultaneously with technology choices. The proposed design roadmapping process assists project prioritization and selection. The process aggregates design experience elements along a timeline that associates key user needs with the products, services, and/or systems the organization wishes to deliver. To illustrate the design roadmapping process, we conducted a case study in which we applied the design roadmapping process to projects undertaken by a large corporation's innovation lab located in research centers in San Francisco and Mountain View, CA, in partnership with corporate stakeholders located in Asia. The five-step design roadmapping procedure is provided along with detailed information. The decisions from the design roadmapping process have been incorporated into the company's commercial plans. Key findings in this corporate case study bolster the positive impact of design roadmapping in moving strategic thinking from a technology/ feature-driven process to one that is design/experience-driven. It shows how firms might weigh choices between user needs, design principles, and technological innovation.

show abstract

Customer Interaction in Software Development: A Comparison of Software Methodologies Deployed in Namibian Software Firms

Iyawa

Herselman

Coleman

2016

E J Info Sys Dev Countries

View full text Add to dashboard Cite

Software methodologies provide guidelines for the development of software applications. Studies reveal that customer interaction in the software development process improves the chances that software applications will meet customers’ needs. Despite a number of software methodologies introduced and a comparison of these methodologies, there is a dearth of studies that empirically investigate customer interaction between these software methodologies within the Namibian context. The purpose of this study was to examine the differences in customer interaction between software methodologies deployed in Namibian software firms. The study adopted a qualitative, case study approach. Data was collected through standardized, open‐ended interviews. The findings show that the methodologies deployed in Namibian software firms include the waterfall model, Scrum, iterative model, eXtreme Programming (XP), and rapid application development (RAD). The findings also reveal that although there was in‐depth customer interaction in Scrum, the iterative model, XP and RAD, customer interaction in the software development process could also be challenging. The findings provide useful insights in software methodologies deployed in Namibian software firms and the experience within the Namibian context. An implication for software project managers and software developers is that customer interaction should be properly managed to ensure that the software methodologies for improving software development processes are effectively deployed.

show abstract

The Waterfall Model in Large-Scale Development

Cited by 137 publications

References 7 publications

Requirements engineering within a large-scale security-oriented research project: lessons learned

Requirements engineering within a large-scale security-oriented research project: lessons learned

Design Roadmapping: A Framework and Case Study on Planning Development of High-Tech Products in Silicon Valley

Customer Interaction in Software Development: A Comparison of Software Methodologies Deployed in Namibian Software Firms

Contact Info

Product

Resources

About