class_management_system

Senior Project - Spring 2019
Log | Files | Refs | README

body.md (2026B)

      1 # Project Summary
      2 
      3 The purpose of this system is to aid the faculty & staff members involved in 
      4 curricular proposals. The system will store and keep revisions of the files 
      5 used in constructing a proposal. The system will also allow users to email 
      6 their complete proposals to other users for review.
      7 
      8 # Project Goals
      9 
     10 The goals of this project are as follows:
     11 
     12 1) Streamline the process of creating, editing, and completing a proposal.
     13 2) Collect all required documents of a proposal into one central database.
     14 2) Provide version control for each proposal and its separate documents.
     15 
     16 # Product Features
     17 
     18 1) **System**: The system will be set up on a Linux server.
     19 2) **User accounts**: Users will log in with their Rowan email and a password.
     20 3) **Database**: A database to contain the locations of files, as well as relationships 
     21 between files. 
     22     * Database will also store any other relevant information (version, author, etc).
     23 4) **Curricular Proposals**: 
     24     * Create / modify curricular proposals.
     25     * Upload and store relevant 'parts' to a given proposal:
     26         * Cover sheet
     27         * Template
     28         * Library form (optional)
     29         * Consult letter(s)
     30     * Approve / Deny curricular proposals.
     31     * Browse through and search for existing proposals.
     32     * Keep version numbers and revision notes of proposals.
     33 5) **Interface**: Interaction with system via a web front-end.
     34 6) **Email**: Composition and sending of emails via SMTP.
     35 
     36 # Limitations
     37 
     38 1) A proposal may have been updated by the time someone reviews the version sent to them.
     39 2) A document must be edited in a program such as Word. There is no integrated editor.
     40 
     41 # Stretch Goals
     42 
     43 1) Google OAuth integration for login.
     44 2) Integration with open source workflow creation tools.
     45 3) Automatically convert from multiple formats (.doc, .docx) to .pdf.
     46 4) Automatically notify relevant users of a proposal change.
     47 5) Auto generate cover sheets using database fields. (title, department, etc.).
     48 6) Integration with Rowan’s new curriculum system.