Software engineering presentation for CS

software engineering presentation/ extreme programming

1. EXTREME PROGRAMMING(XP) BY Hassan Dastagir (40124) Sarim Amjad (39978 )

2. Content : XP Value of XP XP Process

3. What is XP? Extreme Programming(XP). Is a approach or methodology towards the Agile development. It is used improve software quality( testing,feedback,listening,design ). Provide ease to software development team. Customer needs are met effectively(Pair programming,Continuous integration).

4. What is XP? Like other Agile methods, XP is a software development methodology broken down into work sprints. Agile frameworks follow an iterative process—you complete and review the framework after every sprint, refine it for maximum efficiency, and adjust to changing requirements.

5. cont!! Values of XP

6. Cont!! There are 5 values in XP Communication Simplicity Feedback Courage Respect

7. 1.Communication Is a primitive,must value.(can’t proceed further) Communication between client and developer or stake holder. Requirement understood. It should be frequent communication to make Req clear. Concise and precise idea should be delivered to avoid ambiguity.

8. 2.Simplicity It restrict the design for immediate need(for prioritize need). No future prediction only for prioritize need for now. Unnecessary requirement are eliminated For example A to B travel.

9. 3.Feedback Conduct continuous unit testing Margin between expected and real (error margin) Error margin obtained by condting unit testing Evaluate the result and that is feedback Most important feedback is of client by presenting test unit. By checking behaviour or requirement and add on things.

10. 4.Courage There should be courage in individual of team. To stand against the things which are affecting the efficiency of software. Work should be disciplined and casual approach should be dropped. Courage should be required when unseen thing is given by client.

11. 5.Respect Every individual should be respected There should be respect in member of development team There is also should be respect between client and development team.

12. XP Process The following are the processes in extreme programming: Planning Design Coding Testing

13. Planning In the  planning stage of XP, you’re determining if the project is viable and the best fit for XP. User stories to see if they match the simplicity value and check in to ensure that the customer is available for the process. If the user story is more complex, or it’s made by an anonymous customer, it likely won’t work for XP. What stage of development you’re in. XP is best for early stage development, and won’t work as well for later iterations.

14. Planning Once you’ve confirmed the project is viable for XP, ‌create a release schedule—but keep in mind that you should be releasing early and often to gain feedback. To do this: Break the project down into iterations and create a plan for each one.  Set realistic deadlines and a sustainable pace.  Share updates as they happen, which empowers your team to be honest and transparent.  Share real-time updates that help the team ‌identify, adapt, and make changes more quickly. 

15. 2. Design When you’re just starting out with extreme programming, begin with the simplest possible design, knowing that later iterations will make them more complex. Do not add in early functionality at this stage to keep it as bare bones as possible. XP methodology teams will often use class-responsibility-collaboration (CRC) cards to show how each object in the design interacts. By filling out each field in the card, you’ll get a visual interaction of all the functions as they relate and interact. CRC cards include: 

16. 2. Design Class (collection of similar objects) Responsibilities (related to the class) Collaborators (class that interacts with this one ) CRCs are useful for stimulating the process and spotting potential problems. Regardless of how you design, you’ll want to use a system that reduces potential bottlenecks. To do this, be sure you’re proactively looking for risks. As soon as a potential threat emerges, assign one to two team members to find a solution in the event that the threat takes place.

17. 3 . Coding But coding rules are fairly strict in XP. Some of these rules include: All code must meet coding standards. Using a unit test to nail down requirements and develop all aspects of the project. Use continuous integrations to add new code and immediately test it. Only one pair can update code at any given time to reduce errors. Collective code ownership—any member of the team can change your code at any time.

18. 4. Testing You should be testing throughout the extreme programming process. All code will need to pass unit tests before it’s released . If you discover bugs during these tests, you’ll create new, additional tests to fix them. Later on‌, you’ll configure the same  user story  you’ve been working on into an acceptance test. During this test, the customer reviews the results to see how well you translated the user story into the product.

19. XP Process