Latest revision as of 00:08, 6 November 2011

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 defines 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 task 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.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<batch id="0">
    <waitAction>
        <waitTime>100</waitTime>
    </waitAction>
    <tagAction>
        <execDuration>200</execDuration>
        <number>20</number>
        <prefix>eef</prefix>
        <tagGen>GEN2</tagGen>
        <tagType>CustomEPC96</tagType>
    </tagAction>
    <waitAction>
        <waitTime>100</waitTime>
    </waitAction>
    <gpiAction>
        <port>0</port>
        <signal>true</signal>
    </gpiAction>
</batch>

The Scenario

Describes how the PathItems are connected to each other best weight loss to simulate a assembly line in a factory.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<scenario>
    <pathUnit>
        <readerID>0</readerID>
        <travelTime>400</travelTime>
    </pathUnit>
    <pathUnit>
        <readerID>0</readerID>
        <travelTime>400</travelTime>
    </pathUnit>
    <pathUnit>
        <readerID>0</readerID>
        <travelTime>400</travelTime>
    </pathUnit>
</scenario>

The Components

Describes the affected devices in the PathItems. That can be RFID readers and in the future some more devices along a assembly line.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<componentList id="0">
    <readerComponents id="0">
        <reader>
         <numAntennas>1</numAntennas>
        <numGPIs>4</numGPIs>
        <numGPOs>4</numGPOs>
        <propertiesMap>
            <entry>
                <key>servermode</key>
                <value>true</value>
            </entry>
            <entry>
                <key>inet_address</key>
                <value>127.0.0.1:10101</value>
            </entry>
            <entry>
                <key>llrp_inet_address</key>
                <value>127.0.0.1:5084</value>
            </entry>
        </propertiesMap>
        <readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName>
        <readerName>LLRPreader</readerName>
        <readerType>LLRPReader</readerType>
        </reader>
    </readerComponents>
    <readerComponents id="1">
        <reader>
            <numAntennas>1</numAntennas>
        <numGPIs>4</numGPIs>
        <numGPOs>4</numGPOs>
        <propertiesMap>
            <entry>
                <key>servermode</key>
                <value>true</value>
            </entry>
            <entry>
                <key>inet_address</key>
                <value>127.0.0.1:10102</value>
            </entry>
            <entry>
                <key>llrp_inet_address</key>
                <value>127.0.0.1:5085</value>
            </entry>
        </propertiesMap>
        <readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName>
        <readerName>LLRPreader2</readerName>
        <readerType>LLRPReader</readerType>
        </reader>
    </readerComponents>
</componentList>

The LoadTestSuite

Describes how many Scenarios are executed and how are the Batches are connected to the scenarios, the speed new batches are created and how long the wait time will be until it's executed again.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<loadTestSuite>
    <fileUnits>
        <fileName>scenario.xml</fileName>
        <fileType>SCENARIO</fileType>
    </fileUnits>
    <fileUnits>
        <fileName>scenario2.xml</fileName>
        <fileType>SCENARIO</fileType>
    </fileUnits>
    <fileUnits>
        <fileName>batch.xml</fileName>
        <fileType>BATCH</fileType>
    </fileUnits>
    <testUnit>
        <batchID>1</batchID>
        <rampTime>4000</rampTime>
        <scenarios>
            <id>1</id>
            <id>2</id>
        </scenarios>
    </testUnit>
    <testUnit>
        <batchID>1</batchID>
        <rampTime>4000</rampTime>
        <scenarios>
            <id>1</id>
        </scenarios>
    </testUnit>
    <testUnit>
        <batchID>1</batchID>
        <rampTime>4000</rampTime>
        <scenarios>
            <id>1</id>
            <id>2</id>
        </scenarios>
    </testUnit>
</loadTestSuite>

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

The BatchGenerator

It uses the Batch as input data and creates the BatchItems which are floating through the Scenario.

The PathItem

A thread which will take a Batch as input and execute the diet pills the defined operations in it.

The LoadTestProcessor

A Thread which takes the LoadTestSuite as input and creates all the necessary objects to operate.