Software Defined Transceiver

From CS486wiki
Jump to navigationJump to search

Software Defined Transceiver

Contents

  • INTRODUCTION
  • PURPOSE
  • SCOPE
  • IMPLEMENTATION DETAILS
  • RESTRICTIONS AND CONSTRAINTS
  • MODULE DESIGN
  • CLASS DIAGRAM
  • DATABASE
  • USER INTERFACES
  • PROJECT DEPLOYMENT
    • Login
    • Main Form
    • Terminal
    • OnlineStatus
    • Position Lookup
    • Schedule
    • Transaction
    • Chat Client
    • Kiss Konsole
    • Environment
    • Database deployment
    • Running the Application

Introduction

Purpose

The software defined transceiver control program allows logging of detected signals with VHF/UHF/Microwave amateur Contests and Radio Astronomy. Each logged signal record has a number of attributes including received frequency, date, time, signal type, received geographical grid square and received call sign. Control program also has following features: searching positions in the database, seeing online and offline terminals, scheduling a band for later use, chatting within LAN with other workstations.

Scope

The scope of the project is implementation of the database and the user interface for following functionalities: recording transaction into database, scheduling a band for later use, looking up a location in the database, chatting with other workstations.

Implementation Details

This project implemented by using MySQL and C#. MySQL Server 5.1 and Microsoft Visual Studio 2008 are used as development environment for this project.

Restrictions and Constraints

This project works fine with a database implemented in one machine and user interface is run also in that machine. To make it one central server database and terminals that have application for interface to database, MySQL Server configurations should be different. ODBC connector should be configured differently. Logging system is designed as logging all action to the database. It might cause space problem. So the logging system can be implemented by using log files instead of using database.

Module Design

===Class Diagram

Team Members

  • Nimet Duru Cilsal
  • Beril Burcu Huroglu
  • Can Vurmaz

Part 1: Administrator’s Perspective

Part 2: Developer’s Perspective