ACMS v1.0.1 Project Presentation ACMS Version 1.0.1 A System for Academic Course Management and Scheduling via the World Wide Web CS 190 Spring 1997 Matthew J. Ho Page 1 of 15
ACMS v1.0.1 Project Presentation Problem Statement • No standard means of information and schedule dissemi- nation exists here at Brown • Wide variety of information distribution, leading to paper waste and paper consumption • Course instructors are beginning to use electronic resources; most, however, are not. • CCC - addressing computer use as teaching aids • University community needs to be provided with the skills necessary to compete in technological world CS 190 Spring 1997 Matthew J. Ho Page 2 of 15
ACMS v1.0.1 Project Presentation ACMS - Solution Overview • Academic or other group website creation and manage- ment facility, with site information • Secure, electronic calendaring database utilizing industry standards • Enhanced Personal Information Manager CS 190 Spring 1997 Matthew J. Ho Page 3 of 15
ACMS v1.0.1 Project Presentation Target Clients Brown University Computing and Information Services Potential Target Users The University Community: Students, Faculty, Staff CS 190 Spring 1997 Matthew J. Ho Page 4 of 15
ACMS v1.0.1 Project Presentation Functional Requirements AUTHENTICATION and SECURITY • Kerberos Version 4 (MIT Project Athena) • User authentication • Message authentication • Java Kerberos Version 4 interface and API CS 190 Spring 1997 Matthew J. Ho Page 5 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) WEBSITE CREATION and MANAGEMENT 1. Default preformatted website. 2. Preformatted syllabus or schedule from BOCA information 3. Allows modification of event data in site calendar: • List of events, each modifiable upon selection • Modification of event dates, descriptions, attachments 4. Commit of each event modification into a relational database 5. WYSIWYG display of HTML schedule as events are modified CS 190 Spring 1997 Matthew J. Ho Page 6 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) WEBSITE CREATION and MANAGEMENT (cont’d) 6. Event placement via mouse movements or keystrokes 7. Upload capabilities 8. Website map on-demand 9. Support for ACLs 10. Site access statistics 11. Site verification CS 190 Spring 1997 Matthew J. Ho Page 7 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) CALENDARING A specialized PIM with embedded RDBMS capabilities 1. Allow multiple views and filters of scheduled event data 2. Allow modification of event objects: times, descriptions, types 3. Scalable schedule views with granularity controls 4. Allow the addition of new events 5. Allow for repetition scheduling 6. Interface for RDBMS queries, returning accessible event data CS 190 Spring 1997 Matthew J. Ho Page 8 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) CALENDARING (cont’d) 7. Event alerting for all or selected events which occur while the ACMS client is running 8. Event alerting via email for all or selected events which occur within a specified time period while the ACMS cli- ent is not running CS 190 Spring 1997 Matthew J. Ho Page 9 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) vCalendar Version 1.0 “The Electronic Calendaring and Scheduling Exchange Format” The ACMS client/server system will be written to conform to industry standards for event/schedule data transport. ACMS data will conform to vCalendar standards, as defined by the versit Consortium and the Internet Mail Consortium vCalendar specification was written on September 18, 1996 A vCalendar whitepaper was published on January 1, 1997 CS 190 Spring 1997 Matthew J. Ho Page 10 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) vCalendar Version 1.0 “The Electronic Calendaring and Scheduling Exchange Format” The ACMS server will be able to reply to different event object formats: • Hypertext (Embedded object HTML) • SMTP Message (Electronic Email) • ACMS’ proprietary event packaging. Clients using the server will be able to precisely transport event data using the vCalendar standard with extensions for ACMS features, such as event type information. CS 190 Spring 1997 Matthew J. Ho Page 11 of 15
ACMS v1.0.1 Project Presentation Functional Requirements (cont’d) Error Handling and Status Reporting 1. ACMS will alert the user of usage errors during runtime in a reason- able manner. 2. ACMS will notify the users of system downtimes and maintainance. 3. System wide events will also be registered with ACMS for ACMS administrators, whereby email alerts can be setup. CS 190 Spring 1997 Matthew J. Ho Page 12 of 15
ACMS v1.0.1 Project Presentation Hardware and Operating System Req’s ACMS will consist of: 1. A Solaris 2.5 SPARC machine running NCSA httpd 1.5a. ACMS client software will be distributed via httpd to client machines. 2. A server of to-be-determined specifications running Sybase 11.0.1 or Oracle 7.x relational database back-ends. ACMS client software will require a Java capable environment. ACMS shall be written under the assumption that all client machines will be Java capable. CS 190 Spring 1997 Matthew J. Ho Page 13 of 15
ACMS v1.0.1 Project Presentation General Implementation Requirements 1. Languages: Java, C++ and Perl. 2. javadoc utility conformity; APIs and documentation will be writ- ten for all interfaces. 3. vCalendar specification conformity. 4. All time and date references will adhere to ISO 8601 standards. 5. ACMS will be written to support any character set registered with the Internet Assigned Numbers Authority (IANA), defaulting to the ASCII character set. ACMS will consequently support any lan- guage as specified in the vCalendar specification. CS 190 Spring 1997 Matthew J. Ho Page 14 of 15
ACMS v1.0.1 Project Presentation Data Flow Diagram Server ACMS Client Acceptance or Rejection Identification Authentication Kerberos Interface Query Result Main Query Client Data ACMS Database Interface Server Results CS 190 Spring 1997 Matthew J. Ho Page 15 of 15
Recommend
More recommend
