removed slide references

08 Domain-Driven Design.md

@@ -5,29 +5,19 @@ In this lab you will be exploring the software domain for your assignment scenar
 
 You should complete the following steps, either in a small group or on your own:
 
-1. Describe the domain depicted in your scenario. This should be in the form of between 6 and 12 sentences in plain English that include the key terms commonly used in the domain _but no technical language at all_. There is an example on lecture slide 45 (the link to the presentation can be found at the top of this lab). This simulates the notes you would be taking in an early meeting with your client.
+1. Read the details of the assignment you have been allocated. This contains a number of statements in plain English that describe the domain as understood by the _client_ depicted in your scenario. This simulates the notes you would be taking in an early meeting with your client. Note that there are no computing-related technical terms.
 2. Extract the **Domain Language** and carefully define what is meant by each of the terms and expressions _in the context your your domain_. Be sure you remove any ambiguity. This simulates a detailed and probing discussion with the client.
+    1. Write the terms down.
+    2. For eahc of these describe what they mean so that a software engineer will understand.
 3. Finally you should use the information you have recorded so far to build a class diagram. This should include:
     1. The domain classes (or artefacts).
     2. Key attributes of each class (but only list the ones that directly relate to the domain discussed, this is not meant to be a database schema!).
     3. The associations between each class or artefact. Optionally you can also specify the multiplicity of each.
-
-This exercise will probably take one complete lab. For the rest of the week you should ensure you have completed the core labs from previous weeks in readyness for the start of the build next week. These labs are:
-
-1. Setup (plus local setup if you plan on using your own laptop).
-2. Templates and forms.
-3. Dynamic websites.
-4. TDD and Express.
-
-The extra labs will help you during the build and, if time allows, you should complete the following:
-
-1. TDD and APIs (especially if you are studying 304CEM).
-2. TDD and JavaScript, to help you implement TDD for code running in the browser.
-3. Async JavaScript which will improve your code structure and layout by introducing some of the more advanced JavaScript asynchronous constructs.
+4. From this information you should be able to produce a domain model to describe your scenario. Remember that this will include the _domain language_ but no other technical terms. 
 
 ## Soft Systems Methodology
 
-Can you apply the 7 step **Soft Systems Methodology** to the assignment scenario? Refer both to the lecture slides, including the bibliography at the end.
+In your second lab try and apply the 7 step **Soft Systems Methodology** to the assignment scenario. Refer both to the lecture slides, including the bibliography at the end.
 
 1. Enter the situation considered problematic
 2. Express the problem situation in a rich picture