corrected links to images (thx for providing the diagrams, @kitenco)

svenjohann · Jul 7, 2016 · 509afa2 · 509afa2
1 parent b9e6bf4
commit 509afa2
Show file tree

Hide file tree

Showing 5 changed files with 7 additions and 70 deletions.
diff --git a/src/main/asciidoc/patterns/improve/butterfly-methodology.adoc b/src/main/asciidoc/patterns/improve/butterfly-methodology.adoc
@@ -23,7 +23,7 @@ development with actual data.
 A problem can be the amount of hardware that is needed to keep all the temp-stores if you have a mass of data.
 Also it can be very expensive to implement the DAA.
 
-image::../../../resources/images/improvement-approaches/butterfly.png["Butterfly-Methodology", title="Butterfly-Methodology"]
+image::improvement-approaches/butterfly.png["Butterfly-Methodology", title="Butterfly-Methodology"]
 
 ===== Experiences
 

diff --git a/src/main/asciidoc/patterns/improve/chicken-little-strategy.adoc b/src/main/asciidoc/patterns/improve/chicken-little-strategy.adoc
@@ -1,31 +1,4 @@
 [[chicken-little-strategy]]
 ==== [pattern]#Chicken-Little Strategy#
 
-===== Intent
-
-
-===== Description
-
-
-===== Experiences
-
-
-===== Risks
-
-
-===== Applicability
-
-===== Consequences
-
-
-===== Also Known As
-
-===== Related Patterns
-
-* test
-
-===== References
-
-* test
-
-// end of list
+to be completed...
diff --git a/src/main/asciidoc/patterns/improve/composite-database-approach.adoc b/src/main/asciidoc/patterns/improve/composite-database-approach.adoc
@@ -16,7 +16,7 @@ grow as the migration progresses.  Eventually the target
 system should perform all the functionality of the
 legacy system and the old legacy system can be retired.
 
-image::../../../resources/images/improvement-approaches/composite.png["Composite-Database-Approach", title="Composite-Database Approach"]
+image::improvement-approaches/composite.png["Composite-Database-Approach", title="Composite-Database Approach"]
 
 During the migration, the old legacy system and its
 target system form a composite information system, as
@@ -58,12 +58,6 @@ the added complexity introduced by the co-ordinator.
 (taken from BISBAL, J. et.al.)
 
 
-===== Experiences
-
-
-===== Risks
-
-
 ===== Applicability
 
 The Composite Database approach is
@@ -75,10 +69,6 @@ some which are semi-decomposable and others which
 are non-decomposable, i.e.  what is known as a Hybrid
 Information System architecture.
 
-===== Consequences
-
-
-===== Also Known As
 
 ===== Related Patterns
 
@@ -89,4 +79,4 @@ Information System architecture.
 * BISBAL, J. et.al.; A Survey of Research into Legacy System Migration. Technical Report TCD-CS-1997-01, Computer Science Department, Trinity College Dublin, 1997. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.50.9051 
 
 
-// end of list
+
diff --git a/src/main/asciidoc/patterns/improve/database-first-approach.adoc b/src/main/asciidoc/patterns/improve/database-first-approach.adoc
@@ -21,7 +21,7 @@ legacy applications to access the database environment in the target side of the
 Fig. 1.  This gateway translates and redirects these calls forward to the new database service.  Results returned
 by the new database service are similarly translated for used by legacy applications.
 
-image::../../../resources/images/improvement-approaches/databaseFirst.png["Database-First-Approach", title="Database-First-Approach"]
+image::improvement-approaches/databaseFirst.png["Database-First-Approach", title="Database-First-Approach"]
 
 The main advantage of this approach is that once the legacy data has been migrated, the latest programming
 languages and reporting tools can be used to access the data providing immediate productivity
@@ -62,19 +62,6 @@ module by module, without an influence on the legacy system. As the migration is
 legacy system can be shut down. 
 
 
-===== Experiences
-
-
-===== Risks
-
-
-===== Applicability
-
-
-===== Consequences
-
-
-===== Also Known As
 
 ===== Related Patterns
 
@@ -85,4 +72,4 @@ legacy system can be shut down.
 * BATEMAN, A. und J.P.MURPHY: Migration of Legacy Systems. Working Paper: CA-2984, School of Computer Applications, Dublin City University, Ireland 1994
 * BISBAL, J. et.al.; A Survey of Research into Legacy System Migration. Technical Report TCD-CS-1997-01, Computer Science Department, Trinity College Dublin, 1997. http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.50.9051 
 
-// end of list
+
diff --git a/src/main/asciidoc/patterns/improve/database-last-approach.adoc b/src/main/asciidoc/patterns/improve/database-last-approach.adoc
@@ -22,7 +22,7 @@ employed to convert calls from the newly created
 applications and redirect them to the legacy database
 service, as shown in Fig. 1.
 
-image::../../../resources/images/improvement-approaches/databaseLast.png["Database-Last-Approach", title="Database-Last-Approach"]
+image::improvement-approaches/databaseLast.png["Database-Last-Approach", title="Database-Last-Approach"]
 
 If the legacy database service is to be migrated to a
 relational database management service, then the target
@@ -61,19 +61,6 @@ may be unacceptable
 (taken from BISBAL, J. et.al.)
 
 
-===== Experiences
-
-
-===== Risks
-
-
-===== Applicability
-
-
-===== Consequences
-
-
-===== Also Known As
 
 ===== Related Patterns