Prepared by: Man 0 war 777 Use case name: View courses offered by the department Primary actor (s): Academic Staff Brief description: The staff will be able to view the courses offered by the department upon logging into the system. Preconditions (what must be true before the use case can start): The staff must first log in to the University’s online registration system; the system then authenticates the staff’s information before granting access. Postconditions (what must be true when the use case ends): All courses offered by the department must be displayed. Normal Flow of Events 1. The staff logs into the University’s registration system using a username and password 2. The system authenticates the staff’s log in information 3.
At the main menu, the various departments are displayed 4. The staff selects its department, and a list of all courses offered in the department is displayed Alternative flows (show each separately and tie to Normal Flow of Events) Exceptional Flows: If staff enters an incorrect log in information, the system will prompt for the correct information. After the third trial, the system will lock the user out and inform the user to contact the administrator. Prepared by: Man 0 war 777 Use case name: Add or remove courses offered by the department for the semester Primary actor (s): Academic Staff Brief description: At the add / remove courses screen, the staff is able to add or courses offered for the semester or remove the ones not offered for the same semester. Preconditions (what must be true before the use case can start): The courses to be added or deleted must be available for the staff to proceed. In other words, if the staff wants to remove a course from the list, the course must already be in the system for this task to be performed.
The Essay on Information Systems Barrier analyses: Task Information Systems
Design of an organization is an important facilitator of strategic information systems schemes. Yet ancient IS structures are not aligned with the age of information systems since they cannot cope with the ever increasing change and the fast horizontal indulge and usage of expansive information technologies (Boar, 2001). A design of an organization that takes into account the ideas of internal ...
Postconditions (what must be true when the use case ends): The course (s) to be added must be updated on the system, likewise the one (s) to be removed. Normal Flow of Events 1. After logging into the system with the main menu displayed, the staff selects the applicable department 2. The system displays a list of courses offered by the department 3.
To remove a course, the staff selects the applicable course (s) to be removed from the Add/Remove Course window 4. Clicks the Remove Course button 5. The system updates the database upon removing the course 6. To add a course, the staff selects a course from a list of available courses in the Add/Remove Course window 7. Clicks on the Add Course button 8.
The system removes the course from the list and updates the database Alternative flows (show each separately and tie to Normal Flow of Events) If a new course is to be introduced in the department and needed to be added to the system, the staff will click on the Add New Course button, which will bring up an Add New Course window. Here, the staff enters the course information in the necessary toolboxes provided, and the system updates the list of courses offered by the department. Exceptional Flows: If the staff inputs an incorrect course while trying to add, the system should display an error message. For example, “Course not found, Do you want to add course? Prepared by: Man 0 war 777 Use case name: Changing course information Primary actor (s): Academic Staff Brief description: The staff will be able to modify information about the courses offered using the Course Change screen. Preconditions (what must be true before the use case can start): Postconditions (what must be true when the use case ends): Modification of the course (s) should reflect on the system when viewed by the staff. Normal Flow of Events 1.
To perform this task, it is assumed that the staff is already logged into the system. 2. At the main menu, the staff selects the particular department 3. The system displays list of available courses in the Courses window 4. The selects the course to be modified from the list 5. The system displays the course to be modified in a Course Modification window 6.
The Essay on Functional Education System Unmotivated Student
Sam Bertolami British Literature 4 th Period 8-10-00 When I accepted the position of Secretary of Education I was asked to design and create an education system that is works. Unfortunately it is my belief that no one person can create a fully functional system of education. The problem with the current educational system is not the teachers, principals, supplies, or budgets [Though the latter two ...
The staff enters the appropriate information to be changed, and clicks on the save button 7. The system updates the information on the database to reflect the change Alternative flows (show each separately and tie to Normal Flow of Events) If for any reason, a course is cancelled, the staff can perform this task at the modification window to reflect the change. Exceptional Flows: The system should display an error message if the staff inputs a time that conflicts with another class taught by the same instructor or the location and time the class meet conflicts. For example, “Class and time conflicts, verify the information.” Prepared by: Man 0 war 777 Use case name: View current available courses Primary actor (s): Students Brief description: At the Course screen, the students will be able to view available courses for the current semester to facilitate registration process.
Preconditions (what must be true before the use case can start): The student must be a returning or newly admitted student whose information has been included on the university’s database. Postconditions (what must be true when the use case ends): The available courses are viewed by the student. In other words, the student is able to view the courses available for the semester in which registration is desired. Normal Flow of Events 1.
The student access the university’s website, navigates to the registration screen 2. At the registration screen, the student is required to log in to the system with a user name and password 3. The system validates the student’s entry and displays the registration main menu 4. At the main menu, the student selects the “View Available Courses” option amongst the list on the menu 5. The student selects the desired course with the course number, and clicks the view button 6.
The Essay on Academic Cheating Students System Cheated
Academic cheating is a major problem on all levels and has negative results on everyone involved. The person cheating is learning nothing by taking the easy way out and the people being cheated off of from are being cheated themselves. There are no solutions that are both total and cheap, one or the other must be sacrificed to some extent. Although academic cheating is a problem that reaches ...
The system displays the course’s availability. For instance, time and location Alternative flows (show each separately and tie to Normal Flow of Events) If logging into the system for the first time, the system prompts for user name and password registration for authentication purposes. Exceptional Flows: If the student enters a wrong user name or password after three trials, the system will temporarily lock the account for security purposes, and displays a message telling the user to contact the network administrator with contact information. Prepared by: Man 0 war 777 Use case name: Add/Drop course (s) Primary actor (s): Students Brief description: After logging into the system, the students should be able to add and drop to and from their course schedules from the Add/Remove screen.
Preconditions (what must be true before the use case can start): The system will ensure that the student intending to add a course has been cleared of any unpaid fees or fines. Postconditions (what must be true when the use case ends): The course (s) added to or dropped from the course schedule is displayed on the screen, updated on the system and verified by the student before logging off. Normal Flow of Events 1. The student logs into the system with a user name and password 2. System validates the student input before granting access 3. At the View Available Courses’s creen, the student selects the desired course to be added 4.
Then clicks on the Add Course button 5. The system automatically adds the course to the student’s temporary schedule of courses 6. To remove a course, the student clicks on the on the “View Schedule” button on the View Available Courses’s creen 7. The system responds by removing the selected course from the schedule, and displays the new schedule on the Course Schedule screen Alternative flows (show each separately and tie to Normal Flow of Events) If logging into the system for the first time, the system prompts for user name and password registration for authentication purposes. Exceptional Flows: If the student enters a wrong user name or password after three trials, the system will temporarily lock the account for security purposes, and displays a message telling the user to contact the network administrator with contact information.
The Term Paper on Group Member System Student Information
System Development ITC 712 Project Proposal Prepared for: Mr. Samsudin Md. Strip Prepared by: Lizawati Bakri (2003215593) Mohd. Farhan Md.Fudzee (2003661166) Shadil Akimi b. Zainal Abidin (2003215952) Masters of Science in Information Technology (MSc. IT) CS 770 Project Title: "STARIS" Sekolah Tuanku Abdul Rahman Information System Due date: 1 August 2003 TABLE OF CONTENTS 1) Introduction To The ...
