BCSE301L_SOFTWARE ENGINEERING

Overview of Software Presented By,

Engineering Dr.Baiju B V
Assistant Professor
Prepared by Dr. Baiju B V, SCOPE
SCOPE, VIT, Vellore
1
 EXTREME PROGRAMMING (XP)
• Extreme Programming (XP), the most widely used approach to agile software
development, originally proposed by Kent Beck.
• Extreme Programming uses an object-oriented approach as its preferred
development paradigm and encompasses a set of rules and practices that occur
within the context of four framework activities:
Planning
Design
Coding
Testing.
• According to the Alliance, “Extreme Programming (XP) is an agile software
development framework that aims to produce higher quality software and
higher quality of life for the development team”.
• XP is built upon values, principles, and practices, and its goal is to allow small to
mid-sized teams to produce high-quality software and adapt to evolving and
changing requirements.
Prepared by Dr. Baiju B V, SCOPE 2
• Extreme Programming takes the effective principles and practices to extreme
levels.

Prepared by Dr. Baiju B V, SCOPE 3

XP Values
• XP has simple rules that are based on 5 values to guide the teamwork
1. Communication
• Effective communication between
the team members helps to transfer
knowledge among them.
• XP particularly stresses the
importance of proper
communication, including face-to-
face discussion with the aid of
different drawing mechanisms,
including whiteboard discussion.

2. Simplicity
• Developers strive to write simple code bringing more value to a product, as it saves time
and effort.
• In extreme programming, the design addresses only the requirements and doesn’t predict
the future
Prepared by Dr. Baiju B V, SCOPE 4
3. Feedback
• Constant feedback helps to identify areas for
improvement.
• With the review of previous efforts, teams can
revise their practices.
• This also helps to maintain a simple design.
4. Respect
• To streamline effective communication and
feedback among the team members, mutual
respect among the team members is essential.
• This helps the team members to work together to
identify simple designs and solutions.
5. Courage
• Courage is more about taking action while tackling fearful situations.
• Giving and receiving honest feedback is necessary.
• Also, accepting that the solution provided to a problem or bug that received substantial
investments is a failure is equally required.
Prepared by Dr. Baiju B V, SCOPE 5
XP Principles
• Principles guide individuals in specific ways that make the values more transparent
and less ambiguous.

1. Incremental changes
• It's better to make small changes step-by-step than to let them accumulate and handle
them all simultaneously.
2. Embrace change
• Speaking of changes, if the client wants to modify the product, programmers should
support the idea and map out how they will incorporate the new changes.
Prepared by Dr. Baiju B V, SCOPE 6
3. Assumed simplicity.
• Developers need to focus on the job that is important at the moment and follow
YAGNI (You Ain’t Gonna Need It) and DRY (Don’t Repeat Yourself) principles.
4. Quality work.
• A team that works well, makes a valuable product and feels proud of it.
5. Rapid feedback.
• Team members understand the given feedback and react to it right away.

Prepared by Dr. Baiju B V, SCOPE 7

 XP PROCESS
• Extreme Programming
encompasses a set of
rules and practices
that occur within the
context of four
framework activities:
Planning
Design
Coding
Testing

Prepared by Dr. Baiju B V, SCOPE 8

1. Planning
• The planning activity (also called the planning game) begins with a requirements activity
called listening.
• Listening leads to the creation of a set of “stories” (also called user stories) that describe
required output, features, and functionality for software to be built.
• Each user story is written by the customer and is placed on an index card.
• The customer assigns a value (i.e., a priority) to the story based on the overall business
value of the feature or function.
• Members of the XP
team then assess
each story and
assign a cost
(measured in
development
weeks) to it.
• It is important to
note that new
stories can be
written at any
time. Prepared by Dr. Baiju B V, SCOPE 9
 • Customers and developers work
together to decide how to group
stories into the next release (the
next software increment) to be
developed by the XP team.
• Once a basic commitment
(agreement on stories to be
included, delivery date, and
other project matters) is made
for a release, the XP team
orders the stories that will be
developed in one of three ways:
(1) All stories will be implemented
immediately (within a few weeks)
(2) Stories with highest value will be
moved up in the schedule and
implemented first, or
(3) Riskiest stories will be moved up in
the schedule and implemented first.
Prepared by Dr. Baiju B V, SCOPE 10
• After the first project release (also called a software increment) has been delivered, the XP
team computes project velocity.
• Project velocity is the number of
customer stories implemented
during the first release.
• Project velocity can then be used to
help estimate delivery dates and
schedule for subsequent releases.
• The XP team modifies its plans
accordingly.

Prepared by Dr. Baiju B V, SCOPE 11

2. Design
• XP design rigorously follows the KIS (keep it simple) principle.
• XP encourages the use of CRC cards as an effective mechanism for thinking about the
software in an object-oriented context.
• CRC (class responsibility collaborator) cards identify and organize the object-oriented
classes that are relevant to the current software increment.
• CRC cards are the only design work product produced as part of the XP process.

Prepared by Dr. Baiju B V, SCOPE 12

• If a difficult design problem is encountered as part of the design of a story, XP
recommends the immediate creation of an operational prototype of that portion of the
design.
• A central notion in XP is that design occurs both before and after coding commences.
• Refactoring—modifying/optimizing the code in a way that does not change the external
behavior of the software means that design occurs continuously as the system is
constructed.
• In fact, the construction activity itself will provide the XP team with guidance on how to
improve the design.
3. Coding
• After user stories are developed and preliminary design work is done, the team does not
move to code, but rather develops a series of unit tests that will exercise each of the
stories that is to be included in the current release (software increment).
• Once the unit test has been created, the developer is better able to focus on what must be
implemented to pass the test.
• Once the code is complete, it can be unit-tested immediately, thereby providing
instantaneous feedback to the developers.
Prepared by Dr. Baiju B V, SCOPE 13
Prepared by Dr. Baiju B V, SCOPE 14
• A key concept during the coding activity is pair programming.
• XP recommends that two people work together at one computer to create code for a
story.
• This provides a mechanism for real-time problem solving (two heads are often better than
one) and real-time quality assurance (the code is reviewed as it is created).

• As pair programmers complete

their work, the code they
develop is integrated with the
work of others.
• This “continuous integration” strategy helps uncover compatibility and interfacing errors
early. Prepared by Dr. Baiju B V, SCOPE 15
4. Testing.
• The unit tests that are created should be implemented using a framework that enables
them to be automated (hence, they can be executed easily and repeatedly).
• This encourages implementing a regression testing strategy whenever code is modified
(which is often, given the XP refactoring philosophy).
• XP acceptance tests, also called customer tests, are specified by the customer and focus on
overall system features and functionality that are visible and reviewable by the customer.
• They are derived from user stories that have been implemented as part of a software
release.

Prepared by Dr. Baiju B V, SCOPE 16

Prepared by Dr. Baiju B V, SCOPE 17
Prepared by Dr. Baiju B V, SCOPE 18