Updated Website
Change-Id: I05124474c8617bbbf7cd8220a23c255c34dedfc0
Signed-off-by: Neil Mackenzie <neil@birdsoftwaresolutions.com>
diff --git a/index.html b/index.html
index 66beef8..1b59c06 100644
--- a/index.html
+++ b/index.html
@@ -125,13 +125,13 @@
<h3> What is CoCaLiMo?</h3>
<p>From experience in the creation of calculation engines for regulatory logic we often find the following situation where different disciplines all store their knowledge
in different formats and tools which cannot interact. Like this:<br><br>
- <img src="CoCaMoPicture2.png" alt="" height="600" width="800"> <br><br>
+ <img src="cocamoPicture2.png" alt="" height="600" width="800"> <br><br>
Therefore things get lost in translation.<br><br>
Also when a data modellers changes the data model (for example to rename a column or attribute), there is no immediate communication that this affects another discipline ,
such as a test or computation which uses that attribute/column. <br><br>
In CoCaLiMo all disciplines store their information in one model like this:
<br><br>
- <img src="CoCaMoPicture1.png" alt="" height="600" width="800"> <br><br>
+ <img src="CocamoPicture1.png" alt="" height="600" width="800"> <br><br>
More detail is provided below on the different aspects of CoCaLiMo.<br>
<div class="row row-pb-md">
diff --git a/testing.html b/testing.html
index b48b758..d1dc20e 100644
--- a/testing.html
+++ b/testing.html
@@ -130,7 +130,7 @@
As this breakdown is stored as a model instance (it is an instance of a CoCaLiMo model) we can link items from the functional breakdown to actual regulatory rulebook text (which is also stored as an instance of a CoCaLiMo model).<br><br>
We can also link from parts of the breakdown model (like modules or scenarios) To actaul test scenario descriptions in AORTA, since these are also stored as instances of CoCaLiMo models. This allows full lineage between regulatory tests and regulatory requirements, and allows domain experts to help in shaping the structure of a set of test scenarios.
<br>
-<img src="functionalityModule.jpg" alt="" height="600" width="800"> <br>
+<img src="functionalityModule.jpg" alt="" height="300" width="800"> <br>
