Pattern Format and Relationships

This section comprises the pattern format for the e-Science patterns, which is presented in Section 4.2.1. In addition, Section 4.2.2 introduces the different relationships that we use to connect the e-Science patterns.

4.2.1. Pattern Format

We decide to focus on the most important attributes in the first step. Section 2.1 shows, that more useful attributes exist. Table 3 shows the specified format for the e-Science patterns. We describe a few attributes in more detail, where we think that this is required.

The name of the pattern is unique across the catalogue. Furthermore, the pattern name can describe the problem, the solution or the desired characteristics as described in Section 4.1.2. The pattern name has to be unique across the pattern catalogue. This helps to avoid misunderstandings, when natural scientists and IT professionals use the pattern name in their vocabulary, when they talk about e-Science solutions.

Attribute Explanation

Name Unique Identifier

Classification Layer of the eExperiment model, to which the pat-tern is allocated

Intent Summarizes the purpose of the pattern

Problem Captures the problem

Context Setting where the pattern can be applied Solution Explanation how the problem is solved Relationships List of relationships to other patterns Example An example where the pattern is applied

Table 3.:This is the format used to specify the e-Science patterns.

The attribute classification can take one of the values: Scientific Experiment Model, IT Experiment Model or Infrastructure.

The attribute example provides an example, where the pattern is applied. Often, this is only a reference to another paper or book, where the pattern is used.

4.2.2. Pattern Relationships

In Section 3.2.2 we introduced relationships, which were used in related works and we also stated which of them we want to reuse. Now we want to explicitly define, how we reuse the relationships and which semantics each relationship has. Since the relationships are used to support the decision making process, it is helpful to understand the role, which they play in the DSS (see Section 5.1.1). Figure 12 is used to make the explanation of the different relationships more tangible.

X

<Relationship Type>

Y Figure 12.:This is an example for a relationship.

<Uses> If a pattern X has a <Uses> relationship to Y, it can optionally make use of Y in its solution. For instance the heterogeneous data pattern uses the patterns data transformation or semantic mediation. The relationship <Uses> is not as strong as the <Requires> relationship.

<Requires> Pattern X requires Y. This means, that Y also has to be applied, when X is applied. This can be due to side effects, which arise when X is applied. There-fore, Y is required to solve these side effects. Additionally, the <Requires>

relationship can have the meaning, that Y has to be selected as a precondition, so that X can be applied. An example in the e-Science pattern catalogue for

the <Requires> relationship is found in the low data quality pattern. It is used, when the data quality of the currently available data sets is not sufficient for achieving reliable scientific results. This requires an action to solve this prob-lem and therefore the low data quality pattern has a <Requires> relationships to the patterns data quality gate and data quality improvement.

<Related To> <Related To> replaces the similar to/alternative relationship, which was de-scribed in Section 3.2.2. Whereas similar to/alternative connects patterns, which address a similar problem by using different solutions, the <Related To> rela-tionship goes beyond this. The <Related To> relarela-tionship connects X with Y, when Y is somehow related to X. For example Y addresses a similar problem by using a different solution or it is quite common to apply Y, when X is applied.

<Conflicts> X has a <Conflicts> relationship to Y, when Y solves a similar problem by using a different solution and they both cannot be applied together. In addition, X can have a <Conflicts> relationship to Y, even when they do not solve a similar problem. This just means that these patterns can never be applied together.

<Refined By> X is refined by Y. This means that Y is a more specialized version of X. For example Y is specialized for a domain or a specific case. Therefore, the user should check, if the refining pattern is more suitable.

4.2.3. Structure Elements

Figure 13.:This shows the visualization of a structure element.

In order to organize the patterns, we need to have additional structure elements. These structure elements are part of the e-Science pattern catalogue. They increase the usability by grouping similar patterns. In the textual description, the section build these structure elements, which organize the patterns. The graphical overview contains elements with dotted lines, that represent the structure elements as shown in Figure 13.

45

4. e-Science Pattern Catalogue

Figure 14.:This is an high level overview of the e-Science experiment model patterns.

In Figure 14 we give an overview of the structure of this section. This section comprises our e-Science patterns on the level of the scientific experiment model.

4.3.1. Natural Way of Doing Research

This section comprises the natural way of doing research patterns. Figure 15 gives an overview of the different research approaches.

Scientific

Figure 15.:This is an overview of the e-Science natural way of doing research patterns.

46