Project Updates

• Relational DB
  • Author field will be in seperate DB and AuthorID will be part of VideoDB
  • enforces referential integrity
  • cascade update related files
  • cascade delete
  • normalization
• Outline of software program: 4 forms
  • Main menu
    • now playing window (visual/text)
    • play list of upcoming videos with start/end times
    • button links to DB, Scheduler, Setup
  • DB
    • list of video titles on left
    • DB entry fields info on right
    • abitlity to edit, add, delete entries
    • delete/edit confirmation dialog window
    • ability to sort videos by fields
    • ability to search videos by fields
  • Scheduler
    • monthly, weekly, daily calendar setup
    • list of titles to drag'n'drop into schedule
    • conflict resolution
  • Setup
    • configure the algorithms that auto-plays videos
    • percentage of commercial play
    • priority of length, novelty, and play count of videos to be auto-played
  
  February 15:
  
  • Any IO signals to external AV equipment should be sent each time they need to activated, regardless of their expected state. Outside factors could effect the their state, so the software needs to reaffirm the needed state.
  • Input form completed using a paradox database. System ODBC database created in Win2k for microsoft Access DB.
  • Goals for next time:
    • more database interaction
    • more work on system design
  February 8:
  
  • Explore the use of Together software to build ULM diagram (case/sequence diagram)
  • Database platform: decided to use Microsoft Access
  • Goals for next time:
    • produce input form to add entries into database
    • examine database design
    • work on system design