2008
DOI: 10.1007/978-3-540-68255-4_29
|View full text |Cite
|
Sign up to set email alerts
|

Toward Empowering Extreme Programming from an Architectural Viewpoint

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2013
2013
2014
2014

Publication Types

Select...
3

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 2 publications
0
3
0
Order By: Relevance
“…While MDD is referred to as a set of approaches in which code is automatically or semiautomatically generated from more abstract models [38], Ambler has argued that using modelling tools would require modelling skill set and specialized expertise [39]. However, Zhang & Patel showed through a case study that the productivity in number of source code lines per staff month increased in case of high percentage of automatically generated code compared to hand coding [40].…”
Section: Agile Model Driven Developmentmentioning
confidence: 99%
“…While MDD is referred to as a set of approaches in which code is automatically or semiautomatically generated from more abstract models [38], Ambler has argued that using modelling tools would require modelling skill set and specialized expertise [39]. However, Zhang & Patel showed through a case study that the productivity in number of source code lines per staff month increased in case of high percentage of automatically generated code compared to hand coding [40].…”
Section: Agile Model Driven Developmentmentioning
confidence: 99%
“…Agile methodologies such as Scrum, Extreme Programming (XP), Feature Driven Development (FDD), and the Dynamic Systems Development Method (DSDM), have gained enough attention for software development in recent years [1]. A number of organizations [2,3] that practice agile methods suggest that agile methods help during the software development process by emphasizing rapid development statements [4,5]. In fact, agile methods are more flexible and help to reduce risks of project failure.…”
Section: Introduction and Problem Backgroundmentioning
confidence: 99%
“…However, they need to follow several rules related to the agile manifesto, including those concerning less documentation and team member interactions, which provide for appropriate communication with customers and other users. However, some researchers and practitioners [4,6,7] highlighted a critical software problem -software security [8,10] and [11]. As mentioned in the abstract, like other agile methods, the Scrum model does not provide guidelines for dealing with the security aspects of software [12].…”
Section: Introduction and Problem Backgroundmentioning
confidence: 99%