Capability Pattern: Generic method pattern
The generic method pattern reflects a methodological structure that is imposed on all use case-specific method patterns. It is repeated for each abstraction level.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Context
Description

Introduction

As shown in Figure 1, the TIMMO-2-USE Generic Method Pattern consists of the six tasks called “Create Solution”, “Attach Timing Requirements to Solution”, “Create Timing Model”, “Analyze Timing Model”, “Verify Solution against Timing Requirements”, and “Specify and Validate Timing Requirements”. In essence, these tasks have the following purposes:

·         “Create Solution” describes the definition of the architecture without any timing information.

·         “Attach Timing Requirements to Solution” describes the formulation of timing requirements in terms of the current architecture.

·         “Create Timing Model” describes the definition of a formalized model for the calculation of specific timing characteristics based on properties of the current architecture.

·         “Analyze Timing Model” describes the actual execution and evaluation of all necessary “calculations” according to the timing model.

·         “Verify Solution against Timing Requirements” describes the comparison of the obtained analysis results with the specified timing requirements.

·         “Specify and Validate Timing Requirements” describes the identification of mandatory timing characteristics and their promotion to timing requirements for the next development phase.

 

By and large, these tasks are carried out at every level of abstraction of the EAST-ADL. Since the EAST-ADL, as well as TIMMO-2-USE, defines a phase for every level of abstraction these tasks are carried out for every level of abstraction: Vehicle, Analysis, Design, Implementation and Operational Level. As shown in Figure 2 there are two exceptions: The first exception is that at the beginning of the Vehicle Phase, a formal work product “Timing Requirements” is not available. The second exception is that at the end of the Operational Phase the task “Specify and Validate Timing Requirements” is not carried out.

 

Figure 1: TIMMO-2-USE Generic Method Pattern

 

Instantiation

As already indicated in the previous paragraph the TIMMO-2-USE Generic Method Pattern can be applied on all levels of abstraction defined by the EAST-ADL.

 

 

Figure 2: Instantiation of TIMMO-2-USE Generic Method Pattern

This instantiation is shown in Figure 2. In every phase of the methodology the corresponding tasks are conducted – except the “Specify and Validate Timing Requirements” in the Operational Phase. At the end of the Vehicle-, Analysis-, Design-, and Implementation Phase the work product “Timing Requirements” is passed to the following phase as basis for subsequent activities in that phase – except at the end of the Operational phase.

 

Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
PlannedYes
Repeatable
Illustrations