Notes

Practices of extreme programming:
1: Pair programming:
It is the agile software development technique where two programmers they work together at one workstation. In pair programming, one writes the code and others observers and reviews each code.

Advantages of peer programming:
I: Best practices and better technique
II: Develops personal skills
III: Good communication and teamwork
IV: More efficient
V: Fewer coding mistakes

Disadvantages of peer programming:
I: It costs more man-hours to produce same features
II: cannot evaluate our own code
III: Ego may arise with each member to push their own ideas

2: Planning game:
It is based on information exchange between team of developers to estimate stories according to time and financial criteria. Strict and defined plan results the planning game.

Advantages of planning game:
I: Proceeds well organized meeting and cooperation between customers and software developers
II: Ensure customer satisfaction, better design and smooth project development

Disadvantages of planning game:
I:
II:


3: Simple Design:
It is one of the basic practices of extreme programming which is based on design phase. It is a methodology where rules is to keep things as the name suggests, simple.
Advantages of Simple design:
I: Easy to understand
II: Time saving
III: keeps programmers in track
Disadvantages of Simple design:
I: Design flaws

4: Coding standards:
Coding standards keeps the code consistent and easy for the entire team to read and refactor. Here code looks like the same encourages collective ownership.

Advantages of coding standards:
I: reduces the amount of time that developers spend
II: increase user satisfaction
III. Quality code




Disadvantages of coding standards:
I: difficult to know which code to use
II: can’t find specific code that we needed
III: issues with negation and findings

5: Continuous integration:
Continuous integration creates a solution for a situation like the following: a company is working on a large project for which the customer should receive comprehensive, complex software. Individual teams develop different sections of the application and the developers program individual functions. After months of work, perhaps years, everything has to be put together – and then problems arise. In this situation, it can take months until the bugs are detected and fixed, and all code snippets are put together. All the while, final testing and deployment is rapidly approaching.

With continuous integration, integrating new code takes place much earlier, not when all participants have completed their sections. Instead, developers add their finished code to the mainline once or several times a day – the source code is then open to all programmers. Since these are always relatively small sections of code, the integration is also rather short. A developer should only need a few minutes to make their work available to the rest of the team. If an error is discovered, it can be detected immediately, and in the best case, quickly corrected.




Advantages of continuous integration:
I: Early troubleshooting possible
II: Constant feedback
III: No overstraining with a single large integration at the end
IV: Accurate recording of changes
V: Constant availability of a functioning, current version
VI: Promotes granular working
Disadvantages of continuous integration:
I: Conversion of familiar processes
II: Requires additional servers and environment
III: Development of suitable test procedures necessary
IV: Waiting times may occur when multiple developers want to integrate their code around the same time

6: System metaphor:
Metaphors are used in different kind of interactive products in order to easily understand what a product is for and how to use it.

The advantages of using metaphors are:
Firstly the opportunity of the individual to learn the systems and products easier.
Secondly it helps the users to comprehend the model applied.
Finally due to their innovation it expands the number of active users’ range (Rogers et al 2011).


The disadvantages are:
Metaphors break the cultural protocols.
It implements conflict with the design principles and it can oblige designers on how to conceptualise a problem.
It averts the user to use computers without the use of metaphors.
It limits the imagination and it leads the designers to sometimes use bad existing designs into new products (Rogers et al 2011).