1. Student Application System Andy Teng Dali Wang Hyoungju Yun James Zujie Shi John Rinderle Maria Stattel Ron Urwongse Timothy Mak 9.26.2001

2. Student Application System Mission To make Carnegie Mellon’s Student Services accessible online To make Carnegie Mellon’s Student Services accessible online “No-stop shopping” – Bill Elliot VP of Enrollment “No-stop shopping” – Bill Elliot VP of EnrollmentResult Convenient and broad access to the CMU community Convenient and broad access to the CMU community

3. History 1988 - Original system developed to only allow administrators access. 1988 - Original system developed to only allow administrators access. Developed under VMS Vax mainframe and INGRES Database (Relational Technologies/CA) Developed under VMS Vax mainframe and INGRES Database (Relational Technologies/CA) Early 90’s – System moved from Vax to Sequent Unix Server Early 90’s – System moved from Vax to Sequent Unix Server Mid 90’s – System again moved from Sequent to HP Unix. Mid 90’s – System again moved from Sequent to HP Unix. 1996 – Pilot program of web application begins 1996 – Pilot program of web application begins 1998 – Web system goes into full implementation 1998 – Web system goes into full implementation

4. Services Provided to users Administration Quick access to registration and administrative tools Quick access to registration and administrative tools Admissions Board Access to student information, scholarship information Access to student information, scholarship informationFaculty Organized access to E-grades, course schedules, regulations Organized access to E-grades, course schedules, regulationsStudents Access to course information, school account information Access to course information, school account information

5. User Requirements Confidentiality Confidentiality Reliability Reliability Accessibility of Records Accessibility of Records Up-to-date information Up-to-date information Usability Usability

6. Hardware Architecture HP 9000 Unix Server Running Netscape HP 9000 Unix Server Running Netscape HP Unix Server running INGRES DB HP Unix Server running INGRES DB NT Server running IIS NT Server running IIS Multiple Sun Solaris Servers running legacy applications Multiple Sun Solaris Servers running legacy applications Multiple NT Servers running Java servlets through web interface Multiple NT Servers running Java servlets through web interface

7. Hardware Architecture cont’d

8. Usage Architecture

9. System Requirements Kerberos password to identify user Kerberos password to identify user Provide controlled access based on end- user identity Provide controlled access based on end- user identity Enter data in required format Enter data in required format

10. Usage Scenario for Student

11. Log-in Screen Requirement

12. Student Information On-line

13. Project Timeline Client Meetings 9.21.2001Meeting with Martha Baron, Director of Information Services Class Presentations 9.26.2001Project Briefing 1 10.31.2001Project Briefing 2 11.14.2001Project Briefing 3 12.5.2001Project Briefing 4

14. SNA Project Teams SNA Step 1- James Zujie Shi, Tim Mak SNA Step 1- James Zujie Shi, Tim Mak SNA Step 2- Maria Stattel, Dali Wang SNA Step 2- Maria Stattel, Dali Wang SNA Step 3- Andy Teng, Hyoungju Yun SNA Step 3- Andy Teng, Hyoungju Yun SNA Step 4- John Rinderle, Ron Urwongse SNA Step 4- John Rinderle, Ron Urwongse

15. Team Activities Weekly Meeting Recurring Team Meetings- Wednesdays from 2-3pm Team Meetings to Date 9.19.2001First Team Meeting, assigned project roles 9.22.2001Presentation discussion and layout 9.26.2001Discussed final paper, future meetings schedule

16. Next Steps Meet again with Martha Baron to discuss in detail the SNA Step 2 process Meet again with Martha Baron to discuss in detail the SNA Step 2 process Speak with other professionals involved in the system design Speak with other professionals involved in the system design Begin working on final paper Begin working on final paper