class_management_system

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

commit 7416a7dae535a870a4e91fc072af7b4fdf702436
parent a77981f56e9c68687fb54a2700de6f7d8e0b1712
Author: John Kubach <johnkubach@gmail.com>
Date:   Mon,  4 Feb 2019 23:37:29 -0500

add project specification document

Diffstat:
Adeliverables/.gitignore | 1+
Adeliverables/projectSpecification/body.md | 48++++++++++++++++++++++++++++++++++++++++++++++++
Adeliverables/projectSpecification/titlepage.md | 22++++++++++++++++++++++
3 files changed, 71 insertions(+), 0 deletions(-)

diff --git a/deliverables/.gitignore b/deliverables/.gitignore @@ -0,0 +1 @@ +*.pdf diff --git a/deliverables/projectSpecification/body.md b/deliverables/projectSpecification/body.md @@ -0,0 +1,48 @@ +# Project Summary + +The purpose of this system is to aid the faculity & staff members involved in +curricular proposals. The system will store and keep revisions of the files +used in constructing a proposal. The system will also allow users to email +their complete proposals to other users for review. + +# Project Goals + +The goals of this project are as follows: + +1) Streamline the process of creating, editing, and completing a proposal. +2) Collect all required documents of a proposal into one central database. +2) Provide version control for each proposal and its separate documents. + +# Product Features + +1) **System**: The system will be set up on a Linux server. +2) **User accounts**: Users will log in with their Rowan email and a password. +3) **Database**: A database to contain the locations of files, as well as relationships +between files. + * Database will also store any other relevant information (version, author, etc). +4) **Curricular Proposals**: + * Create / modify curricular proposals. + * Upload and store relevant 'parts' to a given proposal: + * Cover sheet + * Template + * Library form (optional) + * Consult letter(s) + * Approve / Deny curricular proposals. + * Browse through and search for existing proposals. + * Keep version numbers and revision notes of proposals. +5) **Interface**: Interaction with system via a web front-end. +6) **Email**: Composition and sending of emails via SMTP. + +# Limitations + +1) A proposal may have been updated by the time someone reviews the version sent to them. +2) A document must be edited in a program such as Word. There is no integrated editor. + +# Stretch Goals + +1) Google Oauth integration for login. +2) Integration with open source workflow creation tools. +3) Automatically convert from multiple formats (.doc, .docx) to .pdf. +4) Automatically notify relevant users of a proposal change. +5) Auto generate cover sheets using database fields. (title, department, etc.). +6) Integration with Rowan’s new curriculum system. diff --git a/deliverables/projectSpecification/titlepage.md b/deliverables/projectSpecification/titlepage.md @@ -0,0 +1,22 @@ +% C.P.M.S. (Curricular Proposal Management System) +% Project Specification +% February 5, 2019 + +## Team Members + +* Alaina Smith +* Alexander Kulpin +* Jeff Podwats +* John Kubach, *Team Leader* +* Josh Jackson, *Scrum Master* +* Kyle Baterd + +## Project Links + +**Github**: +<https://github.com/rowancsseniorprojectgroup2tuesday9-30/RowanCurricularProposalManagementSystem> + +**Slack**: +<https://seniorprojectgroup2.slack.com> + +\pagebreak