Difference between revisions of "TagStreamerArchitecture"
From RifidiWiki
| Line 1: | Line 1: | ||
= Tag Streamer 2.0 = | = Tag Streamer 2.0 = | ||
| − | As we talk about Tag Streamer 2.0 we talk about a new Software. The software comes along with Objects and object orientated programming. One of the modern software development concepts is the "Model Viewer Controller" principle. It identifies 3 main parts of a | + | As we talk about Tag Streamer 2.0 we talk about a new Software. The software comes along with Objects and object orientated programming. One of the modern software development concepts is the "Model Viewer Controller" principle. It identifies 3 main parts of a program. |
* the Viewer | * the Viewer | ||
| Line 7: | Line 7: | ||
* the Controller | * the Controller | ||
| − | == | + | == The Viewer == |
The Viewer will be defined in a later phase of the implementation because the main part of Tag Streamer will be the execution of predefined XML files. | The Viewer will be defined in a later phase of the implementation because the main part of Tag Streamer will be the execution of predefined XML files. | ||
| − | == | + | == The Model == |
| − | The Model represents the input data. In Tag Streamer we can identify | + | The Model represents the input data. In Tag Streamer we can identify 4 parts. |
* the Batch | * the Batch | ||
| Line 18: | Line 18: | ||
* the LoadTestSuite | * the LoadTestSuite | ||
| − | === | + | === The Batch === |
| − | + | Describes what should be done on the PathItems along the Scenario. | |
| − | + | ||
| − | + | ||
| + | === The Scenario === | ||
| + | Describes how the PathItems are connected to each other to simulate a assembly line in a factory. | ||
| + | |||
| + | === The Components === | ||
| + | The affected Parts in the PathItems. That can be RFID readers and in the future some more devices along a assembly line. | ||
| + | |||
| + | === The LoadTestSuite === | ||
| + | Describes how the BatchGenerators are connected to the scenarios, the speed new batches are created and how long the wait time will be until it's executed again. | ||
== the Controller == | == the Controller == | ||
| − | The Controller specifies how the input data will be processed.A example "use case" is provided here: [[TagStreamerSpecification]] | + | The Controller specifies how the input data will be processed. A example "use case" is provided here: [[TagStreamerSpecification]]. |
As parts of the controller we can identify the following components: | As parts of the controller we can identify the following components: | ||
Revision as of 20:02, 29 January 2008
Contents
Tag Streamer 2.0
As we talk about Tag Streamer 2.0 we talk about a new Software. The software comes along with Objects and object orientated programming. One of the modern software development concepts is the "Model Viewer Controller" principle. It identifies 3 main parts of a program.
- the Viewer
- the Model
- the Controller
The Viewer
The Viewer will be defined in a later phase of the implementation because the main part of Tag Streamer will be the execution of predefined XML files.
The Model
The Model represents the input data. In Tag Streamer we can identify 4 parts.
- the Batch
- the Scenario
- the Components
- the LoadTestSuite
The Batch
Describes what should be done on the PathItems along the Scenario.
The Scenario
Describes how the PathItems are connected to each other to simulate a assembly line in a factory.
The Components
The affected Parts in the PathItems. That can be RFID readers and in the future some more devices along a assembly line.
The LoadTestSuite
Describes how the BatchGenerators are connected to the scenarios, the speed new batches are created and how long the wait time will be until it's executed again.
the Controller
The Controller specifies how the input data will be processed. A example "use case" is provided here: TagStreamerSpecification.
As parts of the controller we can identify the following components:
- the BatchGenerator
- the PathItem
- the LoadTestProcessor
