---
source_files:
  - Common/DTS.Common/Interface/SensorDatabase/ISensorDatabaseView.cs
  - Common/DTS.Common/Interface/SensorDatabase/ISensorDatabaseViewModel.cs
generated_at: "2026-04-17T16:24:55.024203+00:00"
model: "zai-org/GLM-5-FP8"
schema_version: 1
sha256: "9929fdf19b3f1666"
---

# SensorDatabase

### Purpose
This module defines the view and view model contracts for the Sensor Database feature within the DTS application. It follows the MVVM (Model-View-ViewModel) pattern, providing empty marker interfaces that extend base view/viewmodel interfaces to establish a type hierarchy for Sensor Database components in the system.

### Public Interface

**`ISensorDatabaseView`** (interface)
- Extends: `IBaseView`
- Signature: `public interface ISensorDatabaseView : IBaseView`
- Description: Marker interface for Sensor Database views. No members defined; relies entirely on inherited contract from `IBaseView`.

**`ISensorDatabaseViewModel`** (interface)
- Extends: `IBaseViewModel`
- Signature: `public interface ISensorDatabaseViewModel : IBaseViewModel`
- Description: Marker interface for Sensor Database view models. No members defined; relies entirely on inherited contract from `IBaseViewModel`.

### Invariants
- Both interfaces must always be assignable to their respective base types (`IBaseView`, `IBaseViewModel`) for polymorphic handling in the MVVM infrastructure.
- Implementations are expected to provide the actual functionality through the base interface contracts.

### Dependencies
- **Depends on**: `DTS.Common.Base` (for `IBaseView` and `IBaseViewModel`)
- **Depended on by**: Unknown from source alone (likely Sensor Database feature implementations)

### Gotchas
- These are marker interfaces with no custom members. All behavior contracts come from the base interfaces. The purpose of these empty interfaces appears to be type discrimination for Sensor Database-specific views/viewmodels, but the rationale for not adding any Sensor Database-specific members is unclear from source alone.

---