Fixing publishing errors, moved .gif files from core.tech.slot.base/guidelines/resources to core.tech.common.base/guidelines/resources.
diff --git a/praclib/temp/core.gen.slot.base/.project b/praclib/temp/core.gen.slot.base/.project
new file mode 100644
index 0000000..76da8ab
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.gen.slot.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
index 2b80370..4a11e7a 100644
--- a/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
@@ -1,9 +1,9 @@
<?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.4/uma.ecore"
- xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf"
- epf:version="1.2.0" xmi:id="-mAo18f36rZ1R98kpZX7HMw"
- name="new_guideline,_K32gYAoBEdu0OeEVPFogVA" guid="-mAo18f36rZ1R98kpZX7HMw" changeDate="2006-07-10T15:11:18.051-0700"
+ xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
+ rmc:version="7.2.0" xmi:id="-mAo18f36rZ1R98kpZX7HMw"
+ name="new_guideline,_K32gYAoBEdu0OeEVPFogVA" guid="-mAo18f36rZ1R98kpZX7HMw" changeDate="2008-03-11T11:28:25.929-0700"
version="1.0.0">
<mainDescription><h3>
Design Mechanism Characteristics and Mapping
@@ -17,7 +17,7 @@
for them to survive thereafter.
</li>
<li>
- There might be a need for several very large objects to be stored permanently on disk for several months, never
+ There might be a need for several very large objects to be stored permanently on disk for several months, never
updated, but with sophisticated means of retrieval.
</li>
</ul>
@@ -47,7 +47,7 @@
</p>
<blockquote>
<p align="center">
- <img height="221" title="Figure 1. Mapping Analysis Mechanisms to Design Mechanisms and Classes"
+ <img title="Figure 1. Mapping Analysis Mechanisms to Design Mechanisms and Classes" height="221"
alt="Mapping Analyis Mechanisms to Design Mechanisms and Classes" src="./resources/co_dmec1.gif" width="372" />
</p>
</blockquote>
@@ -62,7 +62,7 @@
The <b>persistence</b> design mechanisms can be mapped to implementation mechanisms as Figure 2 shows:
</p>
<p align="center">
- <img height="216" title="Figure 2. How persistence design mechanism map to implementation mechanism"
+ <img title="Figure 2. How persistence design mechanism map to implementation mechanism" height="216"
alt="How persistence design mechanism map to implementation mechanism" src="./resources/co_dmec2.gif"
width="325" />
</p>
@@ -79,14 +79,14 @@
</p>
<blockquote>
<p align="center">
- <img height="110" title="Figure 3. Mapping structure after optimizing the mechanisms"
+ <img title="Figure 3. Mapping structure after optimizing the mechanisms" height="110"
alt="Illustration of mapping structure after optimizing the mechanisms" src="./resources/co_dmec3.gif"
width="418" />
</p>
- <p align="center" class="picturetext">
+ <p class="picturetext" align="center">
<strong>Figure 3. Mapping structure after optimizing the mechanisms</strong>
</p>
- <p align="left" class="picturetext">
+ <p class="picturetext" align="left">
The design decisions for a client class in terms of mappings between mechanisms. The <font
face="Courier New, Courier, mono">Flight</font> class needs two forms of persistency<strong>:</strong>
<strong>in-memory storage</strong>, implemented by a predefined library routine, and <strong>a
@@ -190,9 +190,7 @@
</h3>
<p>
As with analysis mechanisms, design mechanisms can be modeled using a collaboration, which may instantiate one or more
- architectural or design patterns (see <a class="elementLinkWithType"
- href="./../../../legacy.legacy.obsoleted_from_openup/guidances/guidelines/using_patterns_31FFED10.html"
- guid="_0cr7cACrEdu8m4dIntu6jA">Guideline: Using Patterns</a>).
+ architectural or design patterns.
</p>
<blockquote>
<p>
@@ -210,7 +208,7 @@
collaboration.
</p>
<p align="center">
- <img height="382" title="Figure 4. JDBC: Static View"
+ <img title="Figure 4. JDBC: Static View" height="382"
alt="Diagram of the figure titled Static View: JDBC shows the classes (actually, the classifier roles) in the collaboration. "
src="./resources/jdbc1.gif" width="571" />
</p>
@@ -244,7 +242,7 @@
A series of dynamic views follow, in Figures 5 thorough 9, to show how the mechanism actually works.
</p>
<p align="center">
- <img height="146" title="Figure 5. JDBC: Initialize" alt="Diagram of JDBC: Initialize" src="./resources/jdbc2.gif"
+ <img title="Figure 5. JDBC: Initialize" height="146" alt="Diagram of JDBC: Initialize" src="./resources/jdbc2.gif"
width="285" />
</p>
<p align="center">
@@ -290,7 +288,7 @@
</blockquote>
</blockquote>
<p align="center">
- <img height="253" title="Figure 6. JDBC: Create" alt="Diagram of JDBC: Crreate" src="./resources/jdbc3.gif"
+ <img title="Figure 6. JDBC: Create" height="253" alt="Diagram of JDBC: Crreate" src="./resources/jdbc3.gif"
width="478" />
</p>
<p align="center">
@@ -306,7 +304,7 @@
added to the database.
</p>
<p align="center">
- <img height="352" title="Figure 7. JDBC: Read" alt="Diagram of JDBC: Read" src="./resources/jdbc4.gif" width="600" />
+ <img title="Figure 7. JDBC: Read" height="352" alt="Diagram of JDBC: Read" src="./resources/jdbc4.gif" width="600" />
</p>
<p align="center">
<b>Figure 7. JDBC: Read</b>
@@ -334,7 +332,7 @@
face="Courier New, Courier, mono">DBClass</font>.
</p>
<p align="center">
- <img height="255" title="Figure 8. JDBC: Update" alt="Diagram of JDBC: Update" src="./resources/jdbc5.gif"
+ <img title="Figure 8. JDBC: Update" height="255" alt="Diagram of JDBC: Update" src="./resources/jdbc5.gif"
width="473" />
</p>
<p align="center">
@@ -364,7 +362,7 @@
pay to pull the persistence knowledge out of the class that encapsulates the data.
</p>
<p align="center">
- <img height="255" title="Figure 9. JDBC: Delete" alt="Diagram of JDBC: Delete" src="./resources/jdbc6.gif"
+ <img title="Figure 9. JDBC: Delete" height="255" alt="Diagram of JDBC: Delete" src="./resources/jdbc6.gif"
width="473" />
</p>
<p align="center">
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec1.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec1.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec2.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec3.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/co_dmec3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc1.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc1.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc2.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc3.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc4.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc4.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc5.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc5.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc6.gif
similarity index 100%
rename from praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif
rename to praclib/temp/core.tech.common.base/guidances/guidelines/resources/jdbc6.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi b/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
index 7a59a49..4601556 100644
--- a/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
@@ -4,7 +4,7 @@
xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
rmc:version="7.2.0" xmi:id="-P_LlxVe57r9XOTpngB2ddQ"
name="test_driven_dev_practice,_dLtGEJ-mEdyBk-WQzMU-FQ" guid="-P_LlxVe57r9XOTpngB2ddQ"
- authors="Jim Ruehlin" changeDate="2008-01-17T13:22:16.622-0800" version="7.2.0">
+ authors="Jim Ruehlin" changeDate="2008-03-11T11:19:16.989-0700" version="7.2.0">
<mainDescription><p>
The Test Driven Development practice reduces time to market by reducing the amount of time needed to integrate and
stabilize builds. It improves productivity by finding and fixing errors close to the time they're introduced. And it
@@ -44,8 +44,4 @@
TDD was originally part of Kent Beck's Extreme Programming process. It's now also used in many other Agile and
non-Agile contexts.
</p></mainDescription>
- <keyConsiderations>See&nbsp;<a class="elementLink"
-href="./../../practice.tech.test_driven_development.base/guidances/supportingmaterials/measurementsz_C281C60E.html"
-guid="_ApBRYMVFEdybJe13vGdZaA">Measurementsz</a>&nbsp;for information on adopting and measuring the team's capabilities in
-test driven development.</keyConsiderations>
</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
index 502fd87..923811c 100644
--- a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
@@ -3,7 +3,8 @@
xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
rmc:version="7.2.0" xmi:id="-FCFgETFie9XAhzcc9ZXfSg"
- name=",_q2WJkOFvEdys887i4S_24Q" guid="-FCFgETFie9XAhzcc9ZXfSg" changeDate="2008-02-22T09:59:43.225-0800">
+ name=",_q2WJkOFvEdys887i4S_24Q" guid="-FCFgETFie9XAhzcc9ZXfSg" changeDate="2008-03-11T11:12:11.347-0700"
+ version="7.2.0">
<mainDescription><p>
If you're just getting started with TDD or developer testing in general, you'll need to know why developer testing is a
good idea and the basics of what makes good developer tests. A good starting place is this <a
@@ -33,11 +34,9 @@
</li>
</ul>
<p>
- Once you're familiar with the basics of TDD, browse the capability pattern for the <a class="elementLink"
- href="./resources/test_driven_development_E3D820A5.html" guid="_k7ZugY8EEdy7q8CKc_B8eg">Test Driven Development
- Practice</a>. This illustrates the flow between the testing and implementation tasks during test driven development.
- Select a task to view more detail about what needs to be done to perform the task. If you'll be creating a capability
- pattern or delivery process that includes TDD, see <a class="elementLink"
+ Once you're familiar with the basics of TDD,&nbsp;select&nbsp;various tasks to view more detail about what needs to be
+ done to perform the task. If you'll be creating a capability pattern or delivery process that includes TDD, see <a
+ class="elementLink"
href="./../../../practice.tech.test_driven_development.base/guidances/examples/using_tdd_in_context_F77E5C22.html"
guid="_QeE7YMCsEdyHnYlsYwuJQw">Using the TDD Practice in Context</a>. This shows one example of how TDD can be used in
conjunction with other activities and capability patterns to create a pattern for developing software. This is only one
diff --git a/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi b/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
index dda390b..b3ea255 100644
--- a/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
+++ b/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
@@ -3,19 +3,18 @@
xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
rmc:version="7.2.0" xmi:id="-H6ob8eA7gz_mOsk8ulSFMQ"
- name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-01-03T16:01:19.313-0800"
+ name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-03-11T11:16:41.025-0700"
version="7.2.0">
<keyConsiderations><p>
- It is common to require that code pass all developer tests before it can be delivered in an integrated <a
- class="elementLink" href="./../../core.tech.slot.base/workproducts/software_build_slot_38848FEE.html"
- guid="_zjwzEKg_Edyn_rXSpKp-cg">[Software Build]</a>.
+ It is common to require that code pass all developer tests before it can be delivered in an integrated source code
+ repository.
</p>
<p>
Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.
</p>
<p>
- The&nbsp;<a class="elementLink" href="./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html"
- guid="_1QZI8EfUEdyiPI8btkmvmw">[Work Items]</a>&nbsp;is implicitly used in implementation tasks to manage which
+ The&nbsp;<a class="elementLink" href="./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html"
+ guid="_1QZI8EfUEdyiPI8btkmvmw">[Project Work]</a>&nbsp;is implicitly used in implementation tasks to manage which
requirements or change requests are being realized in the code.
</p></keyConsiderations>
<sections xmi:id="_gjLBUJfIEdyZkIR-s-Y8wQ" name="Run developer tests" guid="_gjLBUJfIEdyZkIR-s-Y8wQ">
