1. Overview of Solution The solution is a desktop Course-Planning Software application to replace their existing electronic Course Scheduling. This a. System Flow  Start up 1. Course-Planning Home Screen  Maintenance Flow 1. Admin/Director Selects from the menu what to maintain 2. Admin Selects to View / Add / Update / Delete a Professor 3. Admin Selects to View / Add / Update / Delete a Stream 4. Admin Selects to View / Add / Update / Delete a Subject 5. Admin Selects to Run a new Schedule and Admin/Director selects to View / Update / Delete existing Schedule  Session& Sales Flow 1. Admin selects to starts a session when logged into Course Planning System 2. Admin starts to do work on Professors 3. Admin starts to do work on Subjects 4. Admin starts to do work on Streams 5. Admin/Director starts to do work on Course Planning Schedule a. Admin adds a Professor b. Admin updates a Professor c. Admin deletes a Professor a. Admin adds a Subject b. Admin updates a Subject c. Admin deletes a Subject a. Admin adds a Stream b. Admin updates a Stream c. Admin deletes a Stream a. Admin hit New Schedule System automatically set up a New Schedule b. Admin/Director updates existing Schedule c. Admin deletes existing Schedule 6. Admin/Director ends session when logged out from Course Planning System 7. System displays errors if the validations occur b. System Features that meet the functional requirements specified in the Requirements Document.  Maintain Professors information (view, add, update, delete)  Maintain Students information (view, add, update, delete)  Maintain Streams information (view, add, update, delete)  Maintain Course Planning Schedule information (view, update, delete)  Make a Schedule  Admin/Director start session on Course Planning System  Admin/Director end session from Course Planning System o The system provides persistence and UI for displaying, adding, updating and deleting Professors. o The system provides persistence and UI for displaying, adding, updating and deleting Students. o The system provides persistence and UI for displaying, adding, updating and deleting Streams. o The system provides persistence and UI for displaying, updating and deleting Course Planning Schedule. o The system provides persistence and UI for making / displaying a automatically Schedules. o It allows getting data from database and create a new Schedule automatically. o It provides for persistence and UI for collection of all Professors and Students and Streams. o The system provides persistence and UI for starting a session on Course Planning System after entered correct user and password. o The system provides persistence and UI for Logout a session from Course Planning System.  Control access to all management functions (maintenance and scheduling) o System provides mechanism for maintaining Professors and Students and Streams and Schedules o System provides access control to functions based on Schedule c. System Features that meet the non-functional requirements specified in the Requirements Document.  Usability o The system has been designed to have an easy to use, standard UI that will meets these requirements:  Admin should be able to enter for adding Professors details  Admin should be able to enter for adding Student details  Admin should be able to effectively operate the system of 10 Professors in 90 seconds. of 10 Students in 90 seconds. with less than one hour of training.  Reliability  Performance o The system has been designed to be very reliable using industry standard technology o The system shall meet the following performance requirements:  All tasks should be performed in under 1 second.  All scheduling tasks should be performed in under 1 second.  Supportability  Interface  Training  Operations  Legal o The system uses industry standard technology so it will be able to be support by many technologies. o The system will support a standard interface for Swing Components for designing this System. o The system will provide on screen instructions. o The system will have training documentation. o The UI is designed to be easy for non-computer users to use and to make it easy to train new Admin/Directors. o The system provides a mechanism to create a New Schedule based on Professors and Students and Streams and Subjects. d. The system design meets the objectives as stated in the requirements.  The system will improve the accuracy of the Professors and  The system will improve the speed of create a New Schedule or Students used during create a New Course Planning Schedule looking up the Professors and Students and Streams in the database. Update/Delete existing Schedule.  The system will improve the speed of view/add/delete/update Professors or Students or Subjects or Streams or Schedules. 2. Technology Solution This system will be a Single System solution. It has these features:  Local Database  GUI Interface This system will use the following technologies:  Java  Java Swing UI framework  MySQL database  Run on Windows or MAC The system is designed to function on a Standalone application on Windows 10 based PC with 4G of memory and 200 GB hard drive. 3. User Interface This section describes the menus, screens provided by the system. This includes menu hierarchy diagrams, screen layout wire frames. Main Menu Main Course- Planning Menu Course Planning Menu Course Planning Add/Update/ Delete/View Professors Add/Update/ Delete/View Students Add/Update/ Delete/View Streams Add/Update/ Delete/View Subjects Add/Update/ Delete/View Schedules Course Planning Login DO Anything in Course Planning Menu End Session & Logout Screens Main Screen Screen Main (Login Screen) Description Displays when application starts and when other pages complete Fields Label Field Validation User Name Password User.password Required user.username Required Actions Submit – submit button hit after enter User Name and Password data if passes validation and return to Course Planning Menu View Professors Screen Screen View Professors Description Show all the Professors exists in the Database Fields Label Field First Name proff.firstname Last Name proff.lastname Email proff.email SSN Proff.ssn Messages <Field> is required Actions Add New Professor – Add New Professor button hit it returns to Add a New Professor Screen Update - it returns to Update Professor Screen Delete – deletes a professor if validation success and it returns to View Professors Screen View Students Screen Screen View Students Description Show all the Students exists in the Database Fields Label Field First Name student.firstname Last Name student.lastname Email student.email SSN student.ssn Messages <Field> is required Actions Add New Student – Add New Student button hit it returns to Add a New Student Screen Update - it returns to Update Student Screen Delete – deletes a Student if validation success and it returns to View Student Screen View Streams Screen Screen View Streams Description Show all the Streams exists in the Database Fields Label Field Stream Name stream.name Messages <Field> is required Actions Add New Stream– Add New Stream button hit it returns to Add a New Stream Screen Update - it returns to Update Stream Screen Delete – deletes a Stream if validation success and it returns to View Stream Screen View Subjects Screen Screen View Subjects Description Show all the Subject exists in the Database Fields Label Field Subject Name subject.name