2017
DOI: 10.14569/ijacsa.2017.080453
|View full text |Cite
|
Sign up to set email alerts
|

Optimized Quality Model for Agile Development: Extreme Programming (XP) as a Case Scenario

Abstract: Abstract-The attributes of quality are that it is complex taxonomy, it cannot be weighted or measured but can be felt, discussed and judged. Early assessment and verification of functional attributes (requirements) are supported well by renowned standards while the nonfunctional attributes (requirements) are not.Agile software development methodologies are of high repute as the most popular and effective approaches to the development of software systems.Early requirements verification methodologies in Agile So… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0
1

Year Published

2018
2018
2023
2023

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 10 publications
(5 citation statements)
references
References 5 publications
(1 reference statement)
0
4
0
1
Order By: Relevance
“…Figure 2 describes the working steps of the extreme programming method which consists of 5 stages/phases. The first step is to initiate end-user needs which are translated and documented into story cards and project planning regarding the activities carried out in the next stages [25]. The second step is the analysis phase.…”
Section: Methodsmentioning
confidence: 99%
“…Figure 2 describes the working steps of the extreme programming method which consists of 5 stages/phases. The first step is to initiate end-user needs which are translated and documented into story cards and project planning regarding the activities carried out in the next stages [25]. The second step is the analysis phase.…”
Section: Methodsmentioning
confidence: 99%
“…Table 2 describes some of the commonly used approaches. Is an Agile methodology that emphasizes teamwork, communication, and high-quality software [70]. Promotes frequent releases, continuous testing, pair programming, collective code ownership, and customer involvement.…”
Section: Collaboration and Communicationmentioning
confidence: 99%
“…Class-Responsibility-Collaborator (CRC) card is used to design the software. CRC card is chosen because it makes the changing of the software design easy (Tabassum et al, 2017) and is suitable with OOP . Each card represents a class in the software.…”
Section: Designmentioning
confidence: 99%