*Extreme Programming:
| characteristics | strengths | weaknesses | applicability |
| *Pair programming - Ensures quality code. One programmer is thinking whether the approach will work, about testing, or ways to simplify the code while the other programmer writes the code. *Simple design - Keep the design as simple as possible for the moment and don't add features that ar not needed for current functionality. *Small releases - There is a short time between versions | *Emphasis on teamwork and communication: As with the TSP, this is very important in improving the performance of just about every software team. *Emphasis on customer involvement: A major help to projects where it can be applied. *Simple design: Though obvious, worth stressing at every opportunity | *as automated acceptance tests rather than specification documents leads to lack of necessary documentation. *Can be very inefficient—if the requirements for one area of code change through various iterations, the same programming may need to be done several times over. *Only works with senior-level developers( no chance for junior worker to gain experience). | *Used in Project Management *Used in XP and Web Development *Used for situations when customers may not have a firm idea of what the system should look like |
No comments:
Post a Comment