IS2000: Conceptual Model

To begin the modelling process we represent the IS2000 system as single component with communication ports for interaction with the outside world.

is2000_01.png

From this initial model, we implement the strategy: "introduce separate components for acquisition, image processing and image exporting".

is2000_02.png

We now use use the strategy: "encapsulate domain-specific hardware".

  • Decompose Acquisition component to ProbeControl and the rest.
  • Decompose Imaging component to DataCollection and the rest.
is2000_03.png

From this model we implement the strategies: "decouple the user interaction model" and "separate components and modules along dimensions of concern".

is2000_04.png

For the exporting component we use the strategy: "encapsulate domain-specific image data"

  • Separate the component responsible for domain-specific communication of image data ('Comm').

Also, the strategy "separate time-critical from non time-critical components" is now utilised.

  • Separate ImageProcessingActivities (ImageProcessing for time-critical and PostProcessing for non time-critical)
is2000_06.png

Finally, we implement the strategy "use a flexible pipeline model for image processing".

  • Incoming data is bundled into packets
  • The packets are processed in the image processing pipeline
is2000_07.png
Protocols for Packetizer and PacketPipe
is2000_08.png
Packetizer behaviour
is2000_09.png
RequestDataPacket protocol
is2000_10.png
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License