Beruflich Dokumente
Kultur Dokumente
Team 9
Zhen Xu
Ziji Guo
Tianshuang Gao
Jiamin Ding
4CYTE
Introduction:
4CYte is an easy to use interactive multi-year schedule planner for university
students and advisers. It provides a convenient platform for building and reviewing
class schedules. The design is a web based client-server model, which provides easy
access for users and makes the tool easier to maintain.
The tool has 3 users:
Admin: The Admin users main function is to maintain the database of users
and classes. The Admin can use the admin page to add and remove courses and set
rules such as prerequisites for courses. The admin may also need to use 3rd party
tools to maintain the database and fix any problems.
Adviser: The adviser users job is to review schedules that are submitted by
students. The adviser will review schedule and submit feedback to the student. An
adviser can flag a schedule for review, add comments to a schedule, and/or send an
email to the student. This allows for efficient reviewing and editing of schedules and
shorter turnaround time between an adviser and student.
Student: The student users role is to create a schedule to refer to during
their time at a university. A student can submit this schedule to adviser for review and
easily edit the schedule if there are any conflicts. The schedule is saved in a database
so a student can always return and make changes at anytime and nearly anywhere.
Screen Sketch
Interface items:
1) 4CYte is the name of our program.
2) This is where the business admin inputs their user login id to enter the
system. People can enter either email or username.
3) This is where the password is entered.
4) If the actor has entered a valid username and password will be able to
login to the system. If valid this will take the business admin to the
business admin screen, else it will have a dialog appear and say that the
credentials are not correct.
5) This is where the new users create their accounts and someone who
forgot their password to find it.
People can chose their identity to login as. There are three opinions.
Student, adviser and admin.
!
Interface item:
1. Single Semester Plan Box: It shows what's the number of the current selected
semester. Click this it brings the user to courses selection page.
2. Semester selection: Pull it down to choose the semester S/SS/F 20XX
3. Course list: it shows what have been chosen for this semester. Connect to the
database directly and download the latest version of data.
4. Student information box: It shows All kinds information of the user. Connect
to the database directly and download the latest version of data. Student is
able to edit his/her information by simply click on the text.
5. Student ID(9 digits)
6. Student name
7. Majors of students
8. Minor major of students
9. Classification of students. Such as, freshman, sophomore
10.Total credits the student has gained.
11.Advisers feedback: It shows the feedback from adviser if available
12.Save button: Save all the edited information to server. Server will compare to
the old database and update if there is any changes.
13.Send button: Send this plan to adviser for further advisement.
!
Interface item:
1. Course list: It shows all the courses chosen.
2. Every single course.
3. Search box: it allows user to search a specific course
4. Type the course name here to search the course
5. Click this button to search
6. Comment section: Some comment and advice about this course; download
from the server if student selected a course.
7. Requirement List: the requirement for the course selected
8. Click here to add course to the list
!
Interface item:
1) Achievement name and description. Simple and interesting names that
can attract users immediately. And description that what uses should
complete to achieve the objective.
2) Users can check their achievements they have made by two ways.
Summary and Recent.
3) We will add interesting and inspiring pictures that match the contents of
each the achievement.
4) This is where to record the date when uses complete the achievement
and how many points they gets.
5) Return Arrow: return to student UI.
!
Interface item:
1. Menu Bar. The menu bar will contain the standard functions for controlling
the program such as Logout, Help, etc. We believe as the project progresses,
we may need to add additional options to the menu bar.
2. Multiple Semester Box. The multiple semester box contains all of the
individual semester boxes. It's purpose is to make it easy to navigate through
all of the semester boxes by using a scrollbar.
3. Individual Semester Box. The individual semester box contains the semester
4.
5.
6.
7.
8.
number, the year/season, the courses that a student has submitted for that
semester, and the amount of credits in that submission. The purpose is to give
the advisor a concise picture of a students schedule. The advisor is will use this
information to evaluate the schedule for that semester.
Student Information Box. This box contains useful information on the
student that submitted the schedule. The advisor can use this information to
decided if the student meets certain criteria (e.g. Junior classification) for
certain courses.
Comment Box. The comment box is a useful tool for the advisor to leave any
special notes for a student concerning the submitted schedule (e.g. CPRE 381
and ComS 309 are difficult to take in the same semester)
Review Check Box. The review check box is a simple toggle box. The
purpose is to flag the current schedule in the event the advisor finds a problem.
If a schedule is flagged for review the student must revise the schedule.
Email Check Box. This is another simple toggle box. It's purpose is to flag the
system to send an optional email. The email will contain the status of the
schedule(e.g. Review or Passed) and any comments the advisor included in the
comment box.
Save Button. This button saves any changes such as comments that the
advisor has made. If the email check box is toggled, the system will send the
student an email
!
Interface item:
1. Major selection: it allows the admin to choose the major he/she wants to
browser and add/modify the courses under it.
2. Rule : Setup rule for the specific course.
3. The selected: The reminder of what current course is under edition.
4. Action Box: the combo box gives various choice of what kind rules needs to be
defined from pre-requisite, co-requisite, classification, sex and etc.
5. Choice Box: the combo box give various choice depends on the choice made in
Action Box. For example: if pre-requisite is chosen, then it will show all courses that
available. If the classification is chosen, then it shows up with freshman, sophomore,
junior and senior.
6. Cancel button: delete the rule.
!
13.Account Management button: It brings admin to AccountManagement page.
14.Database Maintenance button: It brings admin to DatabaseMaintenance page.
!
Interface item:
1.Search Box: allow admin to search a specific user by name.
2.User list: list all the users.
3.Add button: add another user.
4.Information list: including name, role(student/adviser), ID, Sex,Major and etc.
5.Delete button: delete the user.
6.Return button: return to the admin UI
7.Menu bar: allow admin save work to server, disconnect with server, reconnect
to server.
!
Interface item:
1.User list: it lists all the users that registered in the database.
2.Name: the user's name.
3.Role: which role the user plays. Student/adviser/admin.
4.Information: basic information that necessary to identify the person from sex,
ID to class.
5.Courses list: the list that contains all the courses.
6.Courses name and courses number
7.Description: it gives the basic information of the course.
8. Return: return to the admin UI
Non-functional requirements
Performance:
We do not foresee any major problems with performance. The application will be pretty
small in size and should be reasonably responsive. The only major problem may be to many users
loading the server and database at the same time. This can be alleviated by adding additional
server hardware and load balancing if needed.
Scalability:
Our plan is to include only a limited course set to prove the concept. Once we have proved
the concept we can add additional courses and departments. The design should easily be scalable
to additional servers. For programming purposes, it only covers three majors (EE,Coms, Cpr E).
In the long term, it will cover all the majors and courses on the A+. In even longer term that I can
imagine, the all university can use the program to help their students to plan for the future.
Reliability:
The design is relatively simple; therefore we believe that the service should be reasonably
reliable and available. As long as there are no hardware or security problems the service and
stored data will also be reliable.
On the other hand, the accuracy of the information is important as an out-dated information
can mislead students.
Maintainability:
By using just a single web application and database, the tool will be easy to update and/or
add fixes. We will only need to update the the server(s) that hold the data and serve the program.
In case of future expansion, the program will be designed as extendable as possible.
Portability:
Our program design has a high level of portability. We believe any machine capable of
processing web pages and java applets will be able to use the program.
The language chosen is Java which is highly portable. As long the server runs proper web
server environment, it will work. From the user perspective, the issue might be the web browser.