GBA 573 Final Project - PowerPoint PPT Presentation

About This Presentation
Title:

GBA 573 Final Project

Description:

GBA 573 Final Project Prepared by Ross Niswanger Transfer of Student Records to OPMIS Problem Statement Current database record keeping is a dual-entry process. – PowerPoint PPT presentation

Number of Views:39
Avg rating:3.0/5.0
Slides: 18
Provided by: RossBNi
Learn more at: http://carl.sandiego.edu
Category:
Tags: gba | azure | final | project | windows

less

Transcript and Presenter's Notes

Title: GBA 573 Final Project


1
GBA 573 Final Project
  • Prepared by
  • Ross Niswanger

2
Transfer of Student Records to OPMIS
3
Problem Statement
  • Current database record keeping is a dual-entry
    process.
  • With the advent of a Windows-Based OPMIS program
    (STUDENT), redundant data information can be
    eliminated
  • Goal is to incorporate STUDENT electronic data
    with paper files and eliminate as much of the
    paper-trail as possible.

4
Current Situation
  • Currently use Binnacle to track Midshipmen
    information electronically, for use by the staff.
  • Binnacle information is a repeat of information
    require by CNET that is held within OPMIS.
  • System was developed because of old OPMIS being a
    single-user system with no ability for network
    usage.
  • System was designed in house to run on Windows.
    (Microsoft Access)

5
Binnacle
6
Binnacle
7
Binnacle
8
Along Comes STUDENT
  • New OPMIS program instituted this summer.
  • LAN-enabled Windows program. (10 users)
  • User-Friendly in many aspects
  • Duplicates many of the functions of Binnacle

9
STUDENT
10
STUDENT
11
STUDENT
12
Current Issues
  • 191 Data Fields in Binnacle that are also kept in
    OPMIS
  • 6 or 7 Fields in Binnacle not utilized in OPMIS
    (but used by Unit or Battalion Staff)
  • Many errors through lack of communication between
    the two databases
  • Would like to reduce amount of paperwork kept
    within Student Files
  • Certain Reports generated by Binnacle
    (Duplication possible with STUDENT?)

13
Feasibility
  • Currently use Binnacle as database for Unit use.
  • All data required by CNET within STUDENT.
  • Data not required by CNET to be transported to
    another (smaller) database, or not used anymore.
  • Reports can be generated by using SQL, and can
    get to all data kept by STUDENT.
  • Bottom Line Feasible to implement STUDENT as
    main database for UNIT use.

14
Requirements
  • Installation of Software on all staff machines
  • Training staff on how to use software
  • Training staff on how to use software to get the
    information required (reports) (paradigm shift)
  • Creation of shared drive for keeping electronic
    documents generated by/for students
  • Hard copies of required signed documents

15
Design/Development
  • STUDENT already designed
  • Functions within Binnacle not handled by STUDENT
    to be offloaded and issue pressed with CNET to
    allow user fields to be added to STUDENT
  • Paradigm Shift!

16
Implementation
  • Sudden Change
  • Want to eliminate Binnacle in one fell swoop and
    force use of STUDENT
  • Help to ensure Paradigm Shift

17
Questions?
Write a Comment
User Comments (0)
About PowerShow.com