1. Syllabus Management System Matt Bernstein, Paul Capelli, Jared Segal

2. Agenda  Viewing a Syllabus on OAK  Objectives Hierarchy  Proposed Solution  Infrastructure  Application Architecture  Test Scenario Creation / Execution  Demonstration

3. Finding a Syllabus on OAK Finding Your Syllabus on OAK Isn’t Always Easy TaskResultScreenshot Search for all syllabi520 results, none of them what you are looking for Search by Description Database error Try to guess syllabiNo results(too many)

4. 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

5. 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

6. Objectives Hierarchy 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% Objective / Importance %

7. Infrastructure

8. Java Enterprise Applications EAR Enterprise Archive File Encompasses both EJB and WAR Used to deploy application on the web server EJB 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 WAR Web Archive File Incorporates Java Server Pages (JSP), images, stylesheets (CSS) Contains the controller, which fetches data from EJB

9. Model – View – Controller

10. Our Implementation: FwController

11. Features of Our Design  Login / User Authentication  User Roles & Responsibilities  Search  DHTML  Dynamic ABET Report

12. Login / User Authentication

13. 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

14. 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 CS 231CS 258 Programming CS 101CS 103CS 270 Digital EECE 116EECE 116L Signal EECE 263

15. DHTML  Provides an attractive user interface  Images / forms are displayed dynamically on the page  User does not require a page refresh to take the next action Try Me Clicking a button on the page makes this appear. Reduces clutter, saves server resources Asynchronous JavaScript And XML (AJAX) technique

16. Dynamic ABET Report  Downloaded iText Source library  Added iText library to Geronimo server repository  Call library from code  Dynamically build PDF

17. Test Scenario Creation Test Executed Results Recorded Code Modified Retest Test Scenario Complete Test Driven Development Scenarios written after Design but before Development Test Driven Development Scenarios written after Design but before Development

18. 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…

19. Demonstration http://syllabus.vuse.vanderbilt.edu:8080