Project: Student Scheduling System Team#: 06

Project: Student Scheduling System Team#: 06 Client Interaction Report Answer 1: Questions the Team#6 asked:  Can you expand the description of the project?  Are there any artifacts you can provide us?  Does the project cover only undergraduate students or does it cover both undergraduate and graduate students?  Do you have maintenance staff for the maintenance process after delivery? What are their skills?  Should the project enable administrative people to control graduation requirements specified by year?  Is there any constraint if a student wants to take elective courses earlier than scheduled time?  Do you have any graphs or diagrams showing the courses and their prerequisites?  Is there any minimum or maximum for the students to graduate?  Which time of the week are you available for our meetings?  Is the major problem with the transfer students and the students who fails some classes?  What type of classes do you have in the institute?  Which way do you think is the best to keep in contact?  What kind of student types in the institute? Questions the client asked:  Are you informed about the current scheduling system?  Can we arrange web-meetings every week?  Are there any missing points for you about understanding the current study plan?  Will there be sufficient amount of documentations to help me recall any requirement to inform you about?  Can we run the project system on USC server before we install it to our server?  When is the Exploration Commitment Review? Answer 2: Current process is completely manual. That’s why client’s organization doesn’t have any special IT infrastructure for the proposed system.

Hardware:

System probably will not be installed on Stevens Institute’s server in this year. So we have to use USC’s server for this project.

Software:

Data base and Web server: no specific requirements, but we know that technical maintainer will be able to use (maintain) MySQL and PHP servers.

All other details of infrastructure will be discussed in the next meeting. Client promised to clarify some detail. Answer 3:

Artifact Description Requested/ Planned Shown/Rec Delivery Date eived Study Plan for CS ·It is a guide which highlights what subjects a student Given - undergraduates needs to take to complete his degree. (2008-2011) ·This plan mainly contains all the core CS courses in addition to other core requirements (Math/ Science/Humanities) ·All the optional courses can be filled in as long as they fulfill the requirement. Elective list ·It is a document which specifies all courses which can Given - (numerous) fulfill any particular course(s) requirement Course ·This catalog gives a detailed descriptions of every Given - Descriptions course and shows linkage to any other course (if any) ·This also shows which semesters a particular course would be offered. Tree Diagrams/ ·On the basis of the above artifacts, we have to Requested October 2012 Flow charts simulate or draw tree diagrams or flow charts for the undergraduate CS degrees. ·The idea is that one should be able to trace which courses are to be taken when and how these courses are related. ·This would give an idea as where a student stands at any given point. This is a static chart and would be the basis of our scheduling algorithm Basic prototype ·The above artifact would be paper based. Requested November ·This paper based static chart would a blue print for 2012 the basic prototype. Working model ·On the basis of the working prototype, an actual Requested Feb-March scheduling system, (possibly a web-app) would 2013 primarily take all the required inputs (entering year, intended grad year, credits per sem etc) and chalk out a custom schedule for the upcoming semesters. ·This would depend upon the student’s inputs and the availability of courses Answer 4:

Answer 5: New description of the project (changes highlighted with italic font):

Current System System Name: · What It Provides: · Problems or issues? Undergraduate majors often have a great deal of trouble figuring out a schedule of courses that will enable them to graduate in the desired number of years. This is especially true of transfer students, students who fail a course(s), and students in other situations. It sometimes takes students and their advisors hours to develop the students’ study plans. How it's Current process is completely manual. implemented: There is online unstructured data about what is required for the degree, which semesters each course is offered, etc.; students and their advisors use this information to produce what we call “study plans,” i.e., multi-year schedules of courses to take in order to satisfy degree requirements. Desired System Expected Benefits: Savings of a great deal of time and a great deal of frustration. Key Features: - System has two main users: program director (or administrator) and students. - System has to provide interface for entering degree requirements, which include different courses classifications (groups, levels, approved sequences). It also has to provide interface for input course prerequisites and availability in each semester. All these parameters may change according to year of entry. These changes are done by administrator. - Student have to enter: ·desired year of graduation, ·degree program, ·obtained credits (courses from Stevens Institute of Technology, transfer credits, advanced placement credits from high school), ·preferable elective courses to satisfy requirements, Then student have to get a study plan (schedule) which, if followed by the student, will lead to granting of the degree. Other In case of no possible schedule solution System should interact with a student and say what constraints prevent finding the schedule. If it is possible student may remove/change some constraints (such as number of years, preferable elective courses) and repeat search of the schedule.

System probably will not be installed on Stevens Institute’s server in this year. System should be prototyped on USC server. Changes descriptions:

·Current process is completely manual.

·There is online unstructured data about degree requirements.

·Keys features:

·main users (roles)

·description of each role activities

·System hosting.