7.The 10 Commandments

1.The goal must be kept in the form of a proposition

 This is one of the basics.Establish the goal in a way that a simple yes or no question would suffice.For example "is the system safe?".

2.The top goal should assume the scope of the system

When discussing the dependability of a system it is wise to identify the full range of the system.If not, the topic of the discussion will slowly fade out and lead to confusion.Establish the top goal so that it assumes the full scope of the system.

3.Organize the system life cycle and input-output documents of each phase

The fundamental blocks of D-Case are the documents created in the lifecycle of a system.Organize these documents accordingly and start to write a D-Case. 

4.Assumptions are to be made only when necessary

Only place the documents that can be used as assumptions, in the assumptions section.If not, the range affected by the assumption would vary and collapse the structure of the discussion.

5.Grasp the general concept of the D-case structure

In some cases the number of documents involved in the D-Case increases and the D-Case becomes relatively large.Therefore it is best to grasp the general concept and then discuss.Do not just focus on the simple tree structure of D-Case but focus on the whole forest full of trees.

6.Use typical discussion structures

When you are trying to explain something to somebody, there are some instances where your explanation will not get through to the other party no matter how hard you try.In these instances you are probably using your own method of explanation without a properly structured discussion.D-Case too has such instances and it is important that we explain in an easy to understand fashion with a properly structured discussion.

7.Consider the relationship with the other systems when describing

A system does not exist on its own, it almost always has some sort of a relationship with other systems.So when writing a D-case make sure you take the other systems into account too. 

8.Always think beyond the normal boundaries when describing

Always assume that the discussions in a D-Case assumes beyond the scope of the D-Case itself.In the open world unforeseen situations always occur.When writing a D-Case we have to think beyond the normal assumptions.

9.There is no perfect D-case, always aim for a better D-case

It is impossible describe the dependability of a system completely.Accuracy itself depends on the personnel and varies with time and different conditions.Setting a valid scope, setting accurate assumptions, addressing all potential risks can not be done.So we should accept the incompleteness of D-case and focus on writing better D-Cases.

10.Your opinion is of value to us.