| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-DAk3ahn7Yqi4DY4VKX5b7A" |
| name="new_supporting_material,_vLvAUGjFEd2PJ-nlV-86WA" guid="-DAk3ahn7Yqi4DY4VKX5b7A" |
| changeDate="2008-08-12T16:24:47.387-0700" version="7.5.0"> |
| <mainDescription><p>
 |
| The Test Driven Development practice describes how to use TDD to create a high quality version of the implementation.
 |
| It should be used in conjunction with other practices or process elements to deliver high quality software. This
 |
| example illustrates one possible way of utilizing the TDD practice in conjunction with other practices.
 |
| </p>
 |
| <p>
 |
| This digram describes an evolutionary approach to developing the software by considering just a small part of the
 |
| system. A brief amount of time is spent considering the possible design, the code is implemented via the TDD practice
 |
| and&nbsp;the design is reviewed and refactored until high quality software is achieved. The new part of the system is
 |
| then integrated with the rest of the system, and another small part of the system is selected for development.&nbsp;
 |
| </p>
 |
| <p>
 |
| <img height="587" alt="" src="./resources/tdd_in_context.jpg" width="598" />
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |