{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

Week 4 Paper [XP].docx - SWEN 603 Spring 2017 Week 4 Short...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
SWEN 603 Spring 2017 Week 4 Short Paper – Extreme Programming Extreme Programming (XP) is yet another well-versed subtype of agile software development. With its many individualized practices and characteristics, XP is both appealing and, at times, disadvantageous in certain settings. It is important to understand the methodology as a whole in order to recognize its potential and applicability in the software development world. XP is an iterative and incremental development (IID) method based on communication, simplicity, feedback, and courage (Larman, 2004). It uses twelve existing development practices, such as refactoring and pair programming, to quickly produce high-quality software (Dalalah, 2013). The process itself is composed of four phases: planning, design, coding, and testing. These phases are completed by utilizing the many aforementioned core development practices. Figure 1 . The eXtreme programming process (Fruhling & De Vreede, 2006) A very lightweight and flexible methodology, XP emphasizes the minimization of documentation, as well as the importance of programming with little design beforehand. This is depicted in Figure 1, along with the recognition of heavy user involvement and the ‘on-site customer.’ These processes and practices are what make XP so beneficial, with its ability to adapt to change being at the forefront. Unlike traditional programming methodologies, XP thrives in a frequently changing environment. Requirements are rarely defined and maintained from the initiation of a project, making adaptability an important quality. As shown in Figure 2, the
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
utilization of iterations and their heavy user integration and feedback allows for quick acclimation to any adjustments made during the development process. These planning and
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}