Download Syllabus Management System

Syllabus Management System
Matt Bernstein, Paul Capelli, Jared Segal
Agenda







Viewing a Syllabus on OAK
Objectives Hierarchy
Proposed Solution
Infrastructure
Application Architecture
Test Scenario Creation / Execution
Demonstration
Finding a Syllabus on OAK
Finding Your Syllabus on OAK Isn’t Always Easy
Task
Result
Search for all syllabi
520 results, none of
them what you are
looking for
Search by
Description
Database error
Try to guess syllabi
No results
Screenshot
(too many)
Proposed Solution



Web Application – Running on Apache web server using
Java and MySQL
Content Management System – Organizes syllabi within a
structured database
User Roles and Responsibilities – Determine ways in
which syllabi are displayed and edited



Students and the public can view limited syllabi
Faculty can fill syllabi with data
Department chairs and administrators can assign syllabi and
manage the system
What is a syllabus?
Accreditation Board
(ABET)
• Syllabi are required for accreditation
to determine validity of curriculum
Student Perspective
• A collection of data regarding a
course and its content / policies
• Student will seek to obtain grading
policies and topics
Objectives Hierarchy
Objective /
Importance %
Syllabus
Management
System
Students and
the Public 33%
View syllabi by
department
50%
Search for and
view syllabi
50%
Faculty 33%
Create syllabi
100%
Department
Chairs 33%
Assign syllabi
to staff 70%
Satisfy ABET
requirements
30%
Infrastructure
Java Enterprise Applications
EAR
EJB
WAR
• Enterprise Archive File
• Encompasses both EJB and WAR
• Used to deploy application on the web server
• Enterprise Java Beans – Class which stores data
• EJB is a Java Archive (JAR) - Collection of classes/methods
• Specifies the data for the application needed by web pages
• Web Archive File
• Incorporates Java Server Pages (JSP), images, stylesheets (CSS)
• Contains the controller, which fetches data from EJB
Model – View – Controller
Our Implementation: FwController
Features of Our Design





Login / User Authentication
User Roles & Responsibilities
Search
DHTML
Dynamic ABET Report
Login / User Authentication
User Roles & Responsibilities
Admin – Can assign and create syllabi, add and remove users,
view by department and search
Department Chair – Can assign and create syllabi for only
his/her department, view and search
Faculty – Can edit syllabi to which he/she is assigned, view and
search
Student and Public – Can view and search for syllabi, see
limited syllabi data. Students may or may not have addition
access to syllabi information
Search


A Keyword to Syllabus Table is generated from the Syllabi
database
Search queries are broken up into keywords and the table
is used to map these to syllabi
Computer
Programming
Digital
Signal
EECE 263
CS 231
CS 101
EECE 116
CS 258
CS 103
EECE 116L
CS 270
DHTML
Provides an attractive user interface
Clicking
a button
on the page
 •Images
/ forms
are displayed
dynamically on
the page
makes
this appear.
Reduces
savesa server
 •User
does clutter,
not require
page refresh to
resources
take the next action

• Asynchronous JavaScript And XML
(AJAX) technique
Try Me
Dynamic ABET Report




Downloaded iText Source
library
Added iText library to
Geronimo server repository
Call library from code
Dynamically build PDF
Test Scenario Creation
Test
Executed
Test Driven Development
• Scenarios written after
Design but before
Development
Results
Recorded
Retest
Test
Scenario
Complete
Code
Modified
Metrics

Total Lines of Code: 4115







Controller – 996
Jsphelper – 147
Model – 1002
EJB – 665
JSPs – 1305
100+ Builds
31524 lines in Geronimo log file and counting…
Demonstration
http://syllabus.vuse.vanderbilt.edu:8080