Applicability and issues in traditional model of ERP implementations: an industry perspective

Kaushik, Sunil; Bharadwaj, Ashish; Awasthi, Vinay; Sharma, R.

doi:10.19101/ijacr.2017.730004

Cited by 2 publications

(1 citation statement)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Before 2001 [1]- [13], the software industry used traditional software development processes (i.e., Classical waterfall model, iterative waterfall model, spiral model, RAD model). While these traditional models are known to be cost saving for bigger, off-shore projects, there is criticism that exists [13]- [25]. Due to these criticisms and the high ratio of software failures that used traditional models, it led to a change in software process development in 1999.…”

Section: Introductionmentioning

confidence: 99%

Strengths and Weakness of Traditional and Agile Processes - A Systematic Review

Mirza¹,

Datta²

2019

JSW

View full text Add to dashboard Cite

In the software industry, there are several processes and methodologies that exist. The traditional processes and Agile methodologies have their own strengths and weaknesses. Agile methodologies overcome some of the weaknesses of traditional processes. Although in the recent years Agile methodologies have been used by software development companies, there is still a high ratio of software failures when compared with core engineering processes. The adoption of these processes in software development could alleviate software failures. This systematic study reviews the strengths and weaknesses of both traditional processes and Agile processes. The search strategy resulted in 91 papers, of which 25 primary studies are investigated between 2012 and 2019. The detailed search strategy has been presented in this study along with future directions.In a tertiary study done in [18], it has been revealed that test driven development (TDD) has a very positive impact on external quality of a product. The quality attribute included external quality, complexity, code size, etc. However, no conclusion was made on the impacts of TDD on code size. Test driven development is one of the most advantageous approaches that has produced several successful products

show abstract

Section: Introductionmentioning

confidence: 99%