1. MEETING 4 MATT BERNSTEIN, PAUL CAPELLI, JARED SEGAL Syllabus Management System

2. Accomplishments Draft Requirements System Diagrams Email sent to Guy to get access to server – waiting for reply Framework for Final Report

3. Draft Requirements See handout… Follows IEEE specification Generated some questions  Ways in which we will authenticate with OAK, OASIS  Perhaps a function taking XML, web service (we can offer to develop this if it is agreeable)  Subject to potential change, such as increased database tables, etc.

4. Requirements Scope 1.2 Scope The Course Information Management System will be a data-driven web application for uploading, managing, and viewing information related to courses taught at Vanderbilt School of Engineering. The CIMS will provide multiple levels of users access to course information. The CIMS will allow for the searching of course information based on a text query or through links from major curricula. The objective of the CIMS is to provide an easier way to search through and access course information than current alternatives. The goals of a successful implementation will be easier access to course information and a uniform, more easily maintainable system for storing course information.

5. Requirements – Components of a Syllabus 3.1.2 Course Creation and Modification Form Inputs a. Department 1 This is the department in which the the course resides. b. Course Number 1 This is the number of the course in Department 1 c. Departments 2-5 These fields are for additional departments in which the course may be listed. Currently, there are courses in the School of Engineering that are listed in up to three departments. Having additional department fields allows for a course to be listed under all of these departments and provides for future cases in which a course is listed under even more departments. If a course is listed in fewer than five departments, then one or multiple of these fields is left blank. d. Course Numbers 2-5 These are the numbers of the courses in the additional departments. e. Course Title The title of the course. f. Hours Number of hours of credit. g. Professional Components How the class hours are broken down. h. Catalog Description The course description that appears in the course catalog.

6. Requirements – Components of a Syllabus i. Meeting day 1 First day that the course meets. j. Class time 1 The time that the class meets on the first day. k. Meeting days 2-5 Additional days that the class meets. This allows the system to handle classes whose schedule does not conform to the typical M-W-F or T-Th meeting schedule. l. Class times 2-5 The times that the class meets on the additional class days. m. Topics The general topics that will be covered in the course. n. Class schedule List of class dates and specific activities for these dates. o. Relationship outcomes and program criteria p. Professor teaching course The professor who is teaching the course and who authored the course information. q. Grading policy Details how the students will be graded. r. Other notes For anything else a professor wishes to include that was not its own field.

7. Requirements – Next Steps Finalize and freeze requirements document Obtain additional information regarding communication with OAK/OASIS Further fleshing out will occur as we look at design for the system (UML, object design)

8. System Diagrams Development of requirements led to system diagram development We will now go through these diagrams and discuss them Architecture Diagram, Activity Diagram, Class Diagram Drafts – please provide your input

9. Architecture Diagram

10. Activity Diagram

11. Class Diagram – Work in Progress