Requirements engineering as a success factor in software projects

Hofmann, Hubert F.; Lehner, Franz

doi:10.1109/ms.2001.936219

Cited by 353 publications

(190 citation statements)

References 8 publications

Supporting

Mentioning

173

Contrasting

Unclassified

Order By: Relevance

“…The example given in Figure 6 is based on the work of Sommerville and Sawyer (1997) and is supported by our findings in (Hall et al 2002b). The work of (Boehm 2001), (StandishGroup 1995), (Thayer and Dorfman 1990;El Emam et al 1996) and (Hofmann and Lehner 2001) also highlight the importance of this sub-goal.…”

Section: Re Guidelinesmentioning

confidence: 99%

Defining a Requirements Process Improvement Model

2005

View full text Add to dashboard Cite

show abstract

Section: Re Guidelinesmentioning

confidence: 99%

Defining a Requirements Process Improvement Model

2005

View full text Add to dashboard Cite

show abstract

“…Ways to perform successful RE activities were studied [1,2,8,12] and many different techniques and approaches related to elicitation were determined [7,21,17,25].…”

Section: Requirements Engineeringmentioning

confidence: 99%

“…Unfortunately, not all succeed. Deficient and lowquality requirements may be the major reason for software project failures [3,4,7,8,14,21,23]. Software requirements quality is related to correctness, unambiguity, completeness, consistency, ranking, verifiability, modifiability, and traceability [9,13].…”

Section: Introductionmentioning

confidence: 99%

Are software engineers' responses to incomplete requirements related to project characteristics?

Albayrak

Kilic³

2009

2009 Second International Conference on the Applications of Digital Information and Web Technologies

View full text Add to dashboard Cite

show abstract

“…What is needed is a domain specific set of principles and practices that can serve as a checklist for getting started [44].…”

Section: An Agile Application Examplementioning

confidence: 99%

Agile Project Management Methods for ERP: How to Apply Agile Processes to Complex COTS Projects and Live to Tell about It

Alleman¹

2002

Extreme Programming and Agile Methods — XP/Agile Universe 2002

View full text Add to dashboard Cite

Abstract:The selection, procurement, and deployment of an Enterprise Resource Planning (ERP) system is fraught with risk in exchange for significant business and financial rewards [26]. In many cases the packaged ERP product does not provide the entire solution for the business process. These gaps can be closed with third party products or by customizing existing products. Management of this customization, as well as the selection of the core ERP system has traditionally been addressed through high-ceremony, science-based, project management methods [13]. Well-publicized failures using this approach creates the need for new methods for managing ERP projects [11]. This compendium paper describes an alternative to the traditional high-ceremony IT projects management methods. Although many of the methods described are not new assembling them into a single location and focusing on a single issue provides the tools to make decisions in the presence of uncertainty, focus on the critical success factors, and address the managerial and human side of project management Agility allows the project management methods as well as the system to be adaptively tailored to the business needs.

show abstract

Requirements engineering as a success factor in software projects

Cited by 353 publications

References 8 publications

Defining a Requirements Process Improvement Model

Defining a Requirements Process Improvement Model

Are software engineers' responses to incomplete requirements related to project characteristics?

Agile Project Management Methods for ERP: How to Apply Agile Processes to Complex COTS Projects and Live to Tell about It

Contact Info

Product

Resources

About