2015
DOI: 10.15680/ijircce.2015.0301024
|View full text |Cite
|
Sign up to set email alerts
|

Software Development Risk Aspects and Success Frequency on Spiral and Agile Model

Abstract: ABSTRACT:Software companies face a lot of difficulties in choosing a correct development model when projects have to confront a lot of risk factors ranging from low to high. When software development becomes complex in nature due to risk, companies usual practice is to switch over to the only risk detection traditional model -the Spiral. Spiral model is considered to be the best conventional model for risk analysis. But in modern developmental style, all the development cycles around a single trend -the Agile.… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0
2

Year Published

2018
2018
2024
2024

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 7 publications
(5 citation statements)
references
References 4 publications
0
3
0
2
Order By: Relevance
“…However, while research is an interactive process that focuses on one specific capability, each of these capabilities are refined, matured, and then integrated (through development) into a larger complex workflow/system. In these systems it is very important to pay particular attention to the larger broader system/workflow that the capability will be a part of, to ensure that full system intricacies and interactions, and unexpected emergent consequences of AI/ML output are considered (Krishnan 2015). To effectively provide for bridging and interlacing R&D from a holistic system perspective, the systems engineering model must allow for evolutionary/emergent dynamics and distributed collaborative design, while also maintaining the broader system view (Dahmann and Baldwin 2008).…”
Section: Exploring Agile Systems Engineering For Researchmentioning
confidence: 99%
“…However, while research is an interactive process that focuses on one specific capability, each of these capabilities are refined, matured, and then integrated (through development) into a larger complex workflow/system. In these systems it is very important to pay particular attention to the larger broader system/workflow that the capability will be a part of, to ensure that full system intricacies and interactions, and unexpected emergent consequences of AI/ML output are considered (Krishnan 2015). To effectively provide for bridging and interlacing R&D from a holistic system perspective, the systems engineering model must allow for evolutionary/emergent dynamics and distributed collaborative design, while also maintaining the broader system view (Dahmann and Baldwin 2008).…”
Section: Exploring Agile Systems Engineering For Researchmentioning
confidence: 99%
“…Інформаційна складність визначається необхідністю врахування великого обсягу даних, опрацювання яких без допомоги сучасної обчислювальної техніки практично нездійсненна. У цих умовах число можливих рішень, як правило, дуже велике, і вибір найкращого з них «на око», без всебічного аналізу може призводити до грубих помилок [2].…”
Section: виокремлення невирішених раніше частин загальної проблемиunclassified
“…Its main advantage is its ability to respond to the changing requirements and the reduced time to delivery. This model is however very inefficient and difficult to employ for large projects [11].…”
Section: Web Gis Architecturementioning
confidence: 99%