2010
DOI: 10.1145/1764810.1764814
|View full text |Cite
|
Sign up to set email alerts
|

Software development lifecycle models

Abstract: This history column article provides a tour of the main software development life cycle (SDLC) models. (A lifecycle covers all the stages of software from its inception with requirements definition through to fielding and maintenance.) System development lifecycle models have drawn heavily on software and so the two terms can be used interchangeably in terms of SDLC, especially since software development in this respect encompasses software systems development. Because the merits of selecting and using an SDLC… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
85
0
10

Year Published

2011
2011
2023
2023

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 233 publications
(96 citation statements)
references
References 4 publications
1
85
0
10
Order By: Relevance
“…Each requirement will go through complete cycle from gathering requirement, design and develop, until implementation [8]. Increment advantage is that in each cycle, client can provide feedback which help identify and resolve risk in advance [42]. Although the models have their own strengths and weaknesses, incremental model has the advantages of other models without their drawbacks [8].…”
Section: Literature Reviewmentioning
confidence: 99%
“…Each requirement will go through complete cycle from gathering requirement, design and develop, until implementation [8]. Increment advantage is that in each cycle, client can provide feedback which help identify and resolve risk in advance [42]. Although the models have their own strengths and weaknesses, incremental model has the advantages of other models without their drawbacks [8].…”
Section: Literature Reviewmentioning
confidence: 99%
“…According to [5,7,26], these models or standards can be used to determine all phases of the life cycle, but they contain particular characteristics that make them more suitable for specific phases. For instance, the waterfall is suitable for defining phases, because this model uses the feedback concept ensuring and revising the information integrity during a single phase [27]. Moreover, the traditional models ensure the information consistency in the direct flow according to representative life cycle model proposed by ISO/IEC TR 24748-1:2010 [28], i.e., if it is necessary to change some information in previous phases, these models are not able to manage the new information [29].…”
Section: Cross-systems Life Cycle Requirements Interoperation Issuementioning
confidence: 99%
“…Software engineering has been, since its existence, subject of research and improvement in several areas of interest, such as software development processes (SDPs) whose process models evolved from waterfall and nowadays may assume several forms [5]. The development of large software systems is another area of interest that has been, for decades, subject of research work; several topics can be pointed out such as the exploration of issues related to the management of large scale software development [6,7], software architecture [8][9][10], model-driven development [11,12], among others.…”
Section: Related Workmentioning
confidence: 99%