1 / 16

D3.5 Component-oriented design of common test case

D3.5 Component-oriented design of common test case. Michiel Ronsse RUG-ELIS. Purpose of the case. Validation of the SEESCOA methodology and technologies  SEESCOA Camera Surveillance System (SCSS) This deliverable: analysis design DISCLAIMER:

lesley-finley
Télécharger la présentation

D3.5 Component-oriented design of common test case

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. D3.5 Component-oriented design of common test case Michiel Ronsse RUG-ELIS

  2. Purpose of the case • Validation of the SEESCOA methodology and technologies  SEESCOA Camera Surveillance System (SCSS) • This deliverable: • analysis • design • DISCLAIMER: • we are not developing a fully operations camera surveillance system • we are no security experts, and we may have overlooked some important properties.

  3. SCSS and this deliverable • All university partners work on the same case • Design as proposed is the result of 6 meetings during the last 3 months • There is some overlap with other deliverables, e.g. the User Interface part

  4. Requirements - SEESCOA • embedded system • components • real-time • distributed

  5. Requirements - SCSS • digital • local intelligence • offers services (storage, motion detection, administration) • networked (IP/Ethernet) • dynamic, fault tolerant • evolvable • no security (yet) • different users • administrator • operator • different user interfaces • hardware: PC with IP, Palm with IR,... • Type: user (guard), operator, debugger

  6. General overview UI: Workstation UI: PDA Controller Service Camera

  7. Hardware • Camera has local intelligence • PC/104 with • National Semiconductor MediaGX @ 200MHz • 32MB RAM • 16MB Flash • Embedded Linux • JVM: Kaffe • Sony DFW-VL500 with FireWire

  8. Components • Camera + VideoStreamDecoder • Switch, Delay • Mosaic • Zoom Behaviour • Motion Detection • Storage • Controller • User Interface • Client

  9. Image generating components • Camera: • captures images using a hardware camera • settings can be controlled using a prioritizer • VideoStreamDecoder: • receives video information from a camera and generates a RGBA or B/W image • is provided by the camera • acts as a proxy • Mosaic: • multiplexes several video inputs in a new video channel • Switch • Delay

  10. Zoom behaviour component • Contains logic to control the zooming of multiple camera in one room CA1 VSD1 UI1 ZB1 ZB2 CA2 VSD2 UI2

  11. Motion detection component • Analyses a video stream and raises alarm if motion is detected VSD1 Delay Switch SC CA VSD2 MD

  12. Storage component • Responsible for storage/retrieval/query of • events (e.g. alarm) • video sequences • Implemented using two components: • storage controller component • contains the storage logic • storage component • is responsible for the communication with a database

  13. User interface components • UI is used to interact with the SCSS from the outside world • Supports different devices  different User Interface Renderer components, consisting of a 2DUIRenderer and a 2DLayoutManager • All user controllable components have to provide a User Interface description written in XML

  14. Client components • Implements the application logic • Is not bound to any particular type of user interface. • Decides how the user can interact with the system.

  15. Controller component • Responsible for • booting the system • management of the SCSS components • notification of activation/deactivation of components • uploading of components • Acts as a directory service

  16. Future • Components will be implemented by the different partners • The case will be used for validating the SEESCOA methodology • The case will be extended (esp. the controller component): • component migration • remote update of components

More Related