increase university acceptance rate objective
play

Increase university acceptance rate Objective In order to - PowerPoint PPT Presentation

Increase university acceptance rate Objective In order to increase the acceptance rate in the local university, our team aims to create a GUI that will implement the functions necessary to achieve the required 10% increase in the


  1. Increase university acceptance rate

  2. Objective • In order to increase the acceptance rate in the local university, our team aims to create a GUI that will implement the functions necessary to achieve the required 10% increase in the student recruitment process of that university.

  3. Motivation • To assist the local University to grow its admission • To manage information of prospective students • Having this information in a usable database application will allow the staff to focus advertising based on: ➢ geographic location ➢ academic program ➢ academic performance ➢ desired start date ➢ other factors

  4. Project Overview ➢ 3-Part Submission: - Set scope and objectives - Requirements Analysis & Application abilities - ER Conceptual/Relational Models & ER Diagram - Database creation + Data population scripts - Stored Procedures to carry out Bus. Functions - Normalization - Physical DB Design - GUI

  5. Statement of Proposal To create and implement a database and accompanying interface that will allow the University staff to complete their work efficiently enough to increase admission into the University by 10% by the year 2020.

  6. Software Used Technology stack: a) Dia Diagram Editor - Create the E-R diagram b) MySQL & MySQL Workbench - Create the database, stored procedures, data, queries and business functions c) Visual Studio- create the application and link it to the database Communication & Collaboration Medium: Google Docs + Google Hangouts

  7. Functional requirements 1) The database application shall allow staff the ability to create a user account 2) The database application shall give staff the option to use the student view in the event they receive information outside the system and would like to include it themselves without logging in

  8. Functional requirements Cont. 3) The database application shall allow staff the ability to run standardized reports 4) The database application shall allow staff to customize queries for returning desired data elements 5) The database application shall allow staff to update user accounts for other staff, as needed

  9. Functional requirements Cont. 6) The database application shall allow prospective student to have the ability to submit the following basic information: 1. Name (first, last, MI) 2. Address (email, Street#, Apt#, City, State, Zip) 3. Phone# (mobile, home) 4. Academic Program of Interest 5. Proposed Start Semester 6. Current GPA 7. Standardized Test Scores (ACT, SAT, GRE) 8. Current Student Type (In State, Out of State)

  10. Functional requirements Cont. 7) The database application shall allow prospective student to have the ability to view program requirements for degrees offered 8) The database application shall allow prospective student the ability to access scholarship/financial aid information 9) The database application shall allow prospective student the ability to request information about placement and club opportunities 10) The database application shall allow prospective student to have the ability to request information about student life opportunities

  11. Scope of work For the scope of the project, we will do all the work necessary to prepare, design, create, and implement a database application that will store the contact information of prospective students and streamline its use.

  12. E – R Model

  13. Relational Model

  14. Mapping E-R Model to Relational Model

  15. Implementing all business functions in SQL •Relation SQL Statements •Sample Data Loading SQL Statements •Sample Data Loading SQL Statements •SQL Statements for 10 Business Functions

  16. Indexes • Primarily focused on improving read times for prospect related data • Assumptions were made, for example, the MySQL InnoDB storage engine automatically indexes primary keys and foreign keys on tables during table creation. • Below is an example of a covering index that was created to remove a logical step from data retrieval. Not only will the search on the where clause be improved but the data that is often selected will already be stored on the index when • SEARCH_STUDENT_BY_EMAIL • SEARCH_STUDENT_BY_STUDENT_TYPE /*Prospect*/ /*email is there by default of table creation scripts*/ ALTER TABLE `unccdbs`.`prospect` ADD INDEX `prospectID` (`prospectID` ASC, `fName` ASC, `mName` ASC, `lName` ASC, `stNo` ASC, `stName` ASC, `aptNum` ASC, `city` ASC, `state` ASC, `zip` ASC, `email` ASC);

  17. GUI • We created a windows form application which is a prototype run on a local machine. • Assumptions: • MySQL local database • Sever = localhost; • Database = UNCCDBS; • UID = root • password = itcs6160! • Language: C# • Created in Visual Studio

  18. GUI • We created a single form interface for students to input their personal information

  19. GUI • We created an administrator interface with the following functionalities: • Create/Update User Account

  20. GUI • We created an administrator interface with the following functionalities: • Login

  21. GUI • We created an administrator interface with the following functionalities: • Select Task

  22. GUI • We created an administrator interface with the following functionalities: • Mark Emailed Prospects

  23. GUI • We created an administrator interface with the following functionalities: • Run Reports

  24. Functions Example • The Application has been constructed in a layered architecture and the Run Reports page is considered as an example. • Validations have been placed wherever possible to retrieve the correct result. • Prompts have been placed to guide the staff to select the correct fields. • Run Reports

  25. Credits ● Introduction- Tamika Bennett ● Project overview – Tim Glukhoman ● Business Functions-Lei Xu ● ER diagram- Swathi Angadala ● Relational model - Janice Frederickson ● ER Model Mapping to Relational Database - Kettyl Amoakon ● Table creation and Normalization – Madlen Ivanova ● Stored procedures, 10 business functions – Varsha Nair ● Indexing – Maritza Mills ● GUI functionality – Patrick Theodossiou ● Function example – Praneesh Jayaraj ● Conclusion, future work – Branden Rosenlieb

  26. Moving Forward In the remaining months prior to the upcoming admissions cycle, there are several changes that will be made, such like converting the local hosted application to web-based one. Additional functionalities of the application are also expected to be added to incorporate suggestions from the student and staff communities.

  27. Thank you for your attention!

  28. Process Flow • Define scope and objectives Objective • Describe our motivation Motivation • Describe the software that we used for this project and for Software used what purpose Software used • • • • •

Recommend


More recommend