Determine technical capabilities – you may use any implementation technology as long as you will be able to do a demonstration of it. Create the build ERD based on business functionality required Det

Determine technical capabilities – you may use any implementation technology as long as you will be able to do a demonstration of it. Create the build ERD based on business functionality required Det
STudent Admissions, Records and Registration System STARRS Summary The project is to implement an on-line admissions and graduation clearance system for graduate students applying to the University. The current system allows students to apply online but the process by which the faculty reviews the applications is a paper process. For simplicity, in this project your team will design and build a system that will automate the workflow process in the admissions, registration and graduation system for Masters degree students. You can implement this project using any DBMS the team has access to, you must be able to demo the application in the final presentation. The key application components that need to be implemented: Online Application Process A graduate applicant goes to a “website” (any interactive interface) and enters their data into the database. Applicants can check their application status online – the status is one of three (i) application incomplete (ii) application complete and under review and (iii) decision (admit or reject). Admissions Process The graduate admissions committee reviews applications and decides — Admit, Admit with Aid, or Reject. This review process is to be automated, wherein the faculty reviewer can enter the scores into a review form. Online Registration Admitted students enroll at DBU (DataBase University) and are now considered Graduate students. Once the student joins DBU, they will use an online registration system (data pre-exists for courses, sections, faculty – you are not building data entry for this – i.e., data modeled in complete ERD, any required databases would be created and prepopulated with data for your application to access) to register for courses and their transcript is recorded in the database (courses and grades). Before they can register, they need to have their registration hold removed. Graduation Process Each student fills out an online form which lists the courses they will take to meet graduation requirements. When the student applies for graduation, the system must check to see if all graduation requirements are met. Once they are met, and the student is cleared to graduate they are then added to an alumni list. Again, for simplicity, only consider graduation clearance for the Masters program. Details of the applications and on the type of data (and the forms used for review) are provided next. STARRS: Project Details Details according to the process, types of users, and the typical queries (in addition to the queries required to implement the workflow process). Summary of the Overall Workflow Process: The Graduate Student database applications process goes all the way from application being received in the department to the student’s graduation clearance. Here is an outline of the process: 1. An application is received by the department, and an entry is made into the database (indicating date application was received, and the data for the student including academic data such as GPA). (Note that in practice, this data would download from Banner and uploaded into the tables.) The applicant is emailed a “password” to use to login to the STARRS system. Using this they can check the status of their application. (Note: For simplicity use their student ID as their password for access to STARRS.) 2. A decision is made by the Admissions Committee – decision can be Admit or reject. And admit can be ‘admit with aid’ or ‘admit without aid’ – the admission date is also included in the data. 3. An applicant can check on the status of their application by going to the “website” and entering their password. The status is “Application Received and Decision Pending”, or “Application Materials Missing” or “Admission Decision: Accepted” or “Admission Decision: Rejected”. 4.An admitted student shows up at DBU to enroll for courses and is officially a grad student in the department. The executive aide, henceforth referred to as the ‘Graduate Secretary (GS)’, officially enters the student into a ‘current graduate students’ database. Note that they must first be admitted by the GS before they can enroll. 5. Once admitted the student registers for courses using an online registration system. The students’ enrollment information is kept in the database – i.e., the courses enrolled in, year and semester, and grade (for courses they are under progress the grade is an IP). You are required to implement a rudimentary registration system. Students complete a form that lists the courses they wish to take to meet the degree requirements. 6. Student applies for graduation, and if cleared for graduation (the system does an ‘audit’ to check if the student meets degree requirements) the student is removed from the database (by the executive aide) and automatically added into the alumni database. 7. Alumni can visit the website and update their contact information and can also retrieve a list of the classes they have taken. Now let us take a closer look at the process, and information, involved in the workflow process for each of the applications that you have to examine for your project. A ‘graduate applicant’ visits the “webpage” for the admissions/applications. They are presented with an online application form which they proceed to fill out if they are applying to the graduate program. Once the application is complete their application is evaluated by a faculty committee and a final decision is made. The workflow description below is what you are required to implement in the project. Application Process Workflow: A graduate applicant visits a “webpage” and enters a form to fill in their application for admission. When they have completed filling in all the data they submit their application. The transcript is mailed by the applicant, and its receipt is noted in the database by the GS. The recommendation letters are entered online by the letter writers (you are not to build this) and receipt and a “recommendation score” entered by the GS (top 5%, 85-94%, 70-84%, below 70%). Note that because of the above two requirements, the student’s application can be incomplete even though the student has entered all their information. The application is considered to be complete when all required data has been entered by the applicant, and the transcripts and recommendation letters have been received. An applicant can check on the status. The status is updated by the admissions process. Data to be stored: There are two types of information that they need to fill out: Personal Information This includes their name, student number (in practice this would be system assigned), address (assume USA address – street address, city, state, zip code), work, mobile, home telephone numbers and email address. Academic Information – this includes details on their academic background. Degree sought: they specify which degree program they are applying for. For this project, we assume two programs: (1) Masters (MS) program, and (2) Masters of Engineering (MSE) program. Prior degrees. To simplify matters we will only keep track of a maximum of 2 degrees – their Bachelors degree and a (different) Masters degree (if applicable). The degree information should also specify the year they got their degrees, their GPA in that degree, the University/College that they received their degrees from. GRE scores. They should enter their total GRE score and their scores in each of the three categories: Verbal, Analytical and Quantitative. Prior Work experience: an applicant can specify in a sentence or two their past work experience. Admission Date they seek: they specify which semester and year they are applying for within the next year (e.g., W2023, S2022, F2022) – pick list?). Date of application – this is the date that they submit their application. It should be a system generated date. Area of Interest: an applicant specifies an area of interest. This is not required but they may choose to specify this. Transcripts — an applicant must have their transcript sent directly to DBU. This assumes that the transcript will be mailed, and the receipt will be noted in the system by the GS (i.e., the GS will go into this field and update it to record that the transcript has been received). Recommendation Letters — an applicant must specify the references who will write the recommendation letters. The information supplied should be the name of the letter writer, their email address, and their title and affiliation. (Note: no actual recommendation letter is sent out from your application). Similar to transcripts, as recommendation letters are received the GS updates the response received – top 5%, 85-94%, 70-84%, below 70%. Assume maximum of 3 letters can be submitted. After filling in all the data they submit their application and are henceforth an applicant entity in the system. In practice, when they submit their application the system would generate a unique password for them and email it to them. This password would be used by the applicant to query the system for their application status. For this project you will let the applicant query the system using their student number (need to handle the scenario that there is no student number match). Note that the system must also keep track of their current application status. Note: As is the case with the other applications, you should note that some of the data that has to be entered is a selection from a menu or a drop down. For example, an applicant cannot enter “autumn 2004” in the application date — rather their choices are limited to “Summer” or “Fall” or “Winter” and the year is the current year or the next year (i.e., next three semesters). Checking on their application status: A graduate applicant can check on the status of their application by visiting a specific “website.” They enter their student number.. The system should retrieve their status – the status can be Application Incomplete – materials missing. (the can be transcript or recommendation letters). Application Complete and Under Review/No Decision Yet Congratulations you have been admitted. The formal letter of acceptance will be mailed. Your application for admission has been denied. Note that the status of the application is updated by the graduate admissions committee or the graduate secretary (GS). Note that updating the status implies it is connected to the admission decision process which is explained next. Every applicant after the admissions review will end up as an admitted applicant or a rejected applicant. Note that an admitted applicant does not become a current graduate student until they actually enroll at DBU; consequently, not every admitted applicant is a current graduate student, but every current graduate student was an admitted applicant at some time (year). Admission (Application Review) Process The application review process requires (potentially) multiple users to enter data and to reach a decision. It changes the status of an applicant to a final status of admit or reject. The final decision (of admit, admit with aid or reject) is made by a user and not by the system – although the final decision must be stored in the system. Once an application is complete, it is ready for review for admission. The application is reviewed by a faculty admissions committee. Typically, the committee consists of 4-5 faculty. What if review is not from a committee member – no access!) The faculty committee will be given a list of completed (but decision pending) applications. This is in the form of a list of student numbers. When a reviewer logs in they can be presented with a list of pending applications which have not been reviewed (sort them by date received). They select an entry in the list (in way of your choice – click on it, enter student number on separate “website,” etc.) to bring up the review form for that applicant. Typically, several reviewers can evaluate an applicant; for simplicity, assume that each application is reviewed by a single reviewer. The review process starts when the reviewer brings up a student’s review form. Given a student number, the system must generate the Review form – the data for the form is taken from the database based on what the applicant has entered. In practice, the reviewer also looks at the student folder at the detailed transcript, letters, etc. – in this project you can assume that they only look at the online review form! A reviewer completes his review by filling out the various fields in the review form and making a recommendation. The recommendation can be one of four options and represents a ranking: (1) reject, (2) borderline (to mean they are not certain), (3) admit without aid, and (4) admit with aid. The four numbers 1 through 4 in a sense correspond to a ranking of the applicant. The reviewer can also add their comments (to make it simple assume that they can write about 100 characters in their comments) and recommend an advisor (again, you can simplify by assuming that this has to be one of the faculty in the faculty table). When the review is complete the application is said to have been “reviewed” – but a final decision has NOT been made. A final decision (of admit with aid, admit, or reject) is made by the committee as a whole – but in practice only the Chair of the admissions committee (the CAC) enters this decision into the system (which should only display admit or reject – the admit with aid is an internal note and is not actually entered into the banner system) with the help of the Grad Secretary (GS). When a final decision has been made, the status of the applicant is updated, and the application review process is now complete. Data to be stored: The academic information about the applicant is retrieved from the applicant’s entries in the on-line application process and the final status (the status should have been created by the earlier application) is decided in the admission process. However, the admission review process itself creates new data –this data is created during the review process. Some of this information is: Reviewer ranking/recommendation Reviewer comments Advisor (if admitted) Registration Process An admitted graduate applicant may choose to accept DBU’s admission and enroll at DBU – the student now becomes a current graduate student in the department. Once they are a student, they enroll in courses. When they apply for graduation an “audit” is performed on the courses and they are cleared for graduation if they meet the degree requirements. A detailed description of the workflow process follows. Workflow: An admitted student turns up at DBU and is formally admitted, i.e., admitted by the Grad Secretary (GS); in terms of the STARRS system. Once formally admitted and registered in the system as a graduate student, they enroll for graduate courses using a “web” registration system. The “web” registration system enables students to enroll for courses, and faculty (or the GS) to assign grades. A student will be able to use the online registration system to register for courses, and a faculty (or the GS) can use the system only to enter the final grades. The valid final grades are (A, B, C, F). At any time, the GS, a faculty member, or the student can query the system for the current transcript of the student. Courses currently in progress show up with a grade of IP (in progress). Graduation Process Workflow: After completing the requirements for the degree to which they are admitted, the student formally applies for graduation by visiting a “website” and “Apply for Graduation,” and entering their student number and selecting the degree to which they are applying. Once a student has applied for graduation, the system performs an ‘audit’. Specifically, the system checks to see if the student has satisfied all the degree program requirements. This requires that the system check the courses the student has taken and compare them with the program requirements (both course requirements and GPA requirements). The set of requirements that you should use are: student must take 10 courses (each is 3 credits), must complete at least 30 credit hours, and must take the three core courses CS510, CS511, IMSE5212, IMSE 513 and must have at most 2 grades below B, and must have a minimum GPA of 3.0. (Note: you can prepopulate data for this in your tables). If a student has met the program requirements, they are “cleared” for graduation. Else, they are “not cleared” for graduation. If they are not cleared, then the system must inform them why they have not met graduation requirements. Once a student is cleared for graduation, the GS formally process their application and they “graduate”. (Note that, similar to the admission review process, a student can be cleared for graduation, but they do not actually graduate until the GS enters this information into the system and formally clears them.) The process of graduation must be automated, i.e., the GS need only check the “cleared for graduation” students and approve their graduation by clicking on some selection. (In practice the GS actually looks through their folder and transcript.) When a student “graduates” they are removed from the Graduate student table and their information must be entered into an Alumni table. Note that only a summary of their academic information should be kept in the Alumni table. In a real system, the enrollment information for a student is not removed since they may re-enroll at DBU for another degree. Thus, a graduation process would only require that their data be tagged to indicate that they have graduated with a degree while keeping all their information intact. An alumni can only edit their personal information (such as email, address) by logging on to a “website” using their student number. Summary: Data to be stored for Registration and Graduation Processes: Data to be stored by this process includes: Student number, name, address, and the other personal information for the graduate student. Data should also include the degree they are enrolled in and their status (i.e., have they graduated, have they applied for graduation, cleared, etc.), their admit date (Semester and Year). The registration system must store data on the courses, the faculty teaching the course, the grades (if assigned), the schedule (semester and year). To simplify the registration system, you can assume the following. Each course has a title, a course number (dept followed by course number) that can be treated as a unique course number, a section number, the semester it is offered in, and the number of course credits (assume credits is 3). Assume that each course only has one section. Assume there are no prerequisites. The enrollment/registration information must store the course, the semester, course section, the student identification, the instructor information, and the grade. Note that a course offering is unique when one considers the course number and the semester and year that it was offered in. Faculty users (or the GS) should be able to enter the grade for courses they are teaching. Course enrollment information for graduate students. The enrollment information essentially reflects the course registration system, i.e., must store courses taken by the student, the semester and year, the final grade, the number of credit hours of the course. To simplify the registration process, assume that (a) there is no limit on the number of students in the class, and (b) assume that students can only register for graduate credit . Program requirements for the degree (in your project, only the MS degree) are stored in the system. No changes are allowed to the program requirements (e.g., will always be 30 credit hours). Alumni information must be stored. This information includes name, student number, year they graduated and degree, GPA, and personal information such as address, telephone, email etc. Alumni should also be able to view a list of the courses they have taken. Other Queries/Reports: To be implemented in Final Project: Other relevant queries that may be submitted to the system in order to generate specific reports. You can create a menu or “webpage” to select queries to run. Search for an applicant using their last name or student number. This query can be submitted by the GS or by a faculty reviewer. Update applicant’s or students’ academic and personal information – an applicant or the GS may choose to update their data at any time. Given the Semester, or Year or Degree program, generate the list of graduate applicants. This query can be submitted by the GS. Given the semester or year or degree program, generate the list of admitted students. This query can be submitted by the GS. Given the semester or year or degree program, generate statistics such as total number of applicants, total number admitted, total number rejected, average GRE score for admitted applicants. This query can be submitted by the GS. Given the semester or year or degree program, generate the list of graduating students (i.e., those cleared for graduation). This query can be submitted by the GS. Given the semester or year or degree program, generate the list of alumni and their email address. This query can be submitted by the GS Generate total list of current students (by degree or by admit year).This query can be submitted by the GS Change the advisor for a student, given the student’s student number. This query can be submitted by the GS Given a student’s student number, generate the list of courses and grades. This query can be submitted by the GS or by the faculty advisor or by the student. For a faculty advisor, generate list of all advisees. This query can be submitted by the GS or the faculty advisor. Users and Roles: Observe that there are different categories of users of the STARRS system, and each type of user has specific roles and authorizations. Each of these users should be presented with an appropriate interface through which they can perform their authorized tasks. Note: you create a user table and prepopulate – you do not build a add/change/delete user interface. GS Has complete access to applicant’s data and to current student’s data. They are responsible for (1) updating status of applicant, (2) admitting a student (i.e., changing an admitted applicant to a current student once the student enrolls at DBU), and (3) clearing a student for graduation. Faculty Reviewers (including Chair of the admissions committee — the CAC) They can review the student’s application – they have access to all the applicant’s information. They enter their review into a review form which is stored in the system. Reviewers does not include all the faculty. Faculty Advisors These are faculty in the department. They can view their advisees’ courses taken but cannot update the courses. This is the only access they are given. They can view all data about an applicant but cannot enter a review. Faculty Instructors They can enter grades for the students in the courses they are teaching (i.e., courses for which they are the instructor). Make sure you have some faculty (at least one) who are reviewers and advisors and instructors. Applicants. They can enter their graduate application form data and can check on the status of their application. They are not permitted to perform any other functions. Current Graduate Students They can view their class list and grades and can apply for graduation. They can update their personal information (address, email etc.) but no other information. Alumni They can log into the system and edit their personal data only. They should be able to view their courses and grades. Project Tasks: Create a complete ERD of the STARRS system. Create a set of BUSINESS requirements – data, function, and non-functional (summarize as a checklist of what you need to deliver) Determine technical capabilities – you may use any implementation technology as long as you will be able to do a demonstration of it. Create the build ERD based on business functionality required Determine the relational data base structure (keys, etc. Determine and load prepopulated data Create a test plan based on functionality Build and test – plan to divide work evenly and plan a priority list of order to build/test (i.e., better to have working functionality and missing components than all components built but not fully working!) Date of final – report out against checklist of business functionality – works, partially works (what works and what doesn’t), doesn’t work Perform demo Submit report and individual evaluations Weekly Status Single Document Current Week status is page 1 Following weeks in order back to first week is on the last page Content Title – “STARRS Project” Team Name Date of Status 1-2 sentence description of current status Color status – red, yellow, green Accomplishments for the prior week (milestone) Planned work for the next week (milestones) Issues – if any, what is the proposed resolution
Determine technical capabilities – you may use any implementation technology as long as you will be able to do a demonstration of it. Create the build ERD based on business functionality required Det
B usin ess R eq uir e m en ts 1 . A pplic a nt a . A pplic a nt C re atio n i . A n a pplic a nt m ust b e a ble to a cce ss a “ w ebsit e ” to s e e a ll a va ila ble a ctio ns th at c a n b e ta ke n i i. A n a pplic a nt m ust p ro vid e p ers o nal in fo rm atio n in th e fo rm ( s e e s e ctio n 9 f o r in fo d eta ils ) 2 . A pplic a tio n a . A pplic a tio n C re atio n i . A n a pplic a nt m ust p ro vid e a ca dem ic in fo rm atio n in th e fo rm ( s e e s e ctio n 1 0 fo r in fo d eta ils ) i i. A n a pplic a nt m ust p ro vid e a pplic a tio n s p ecif ic in fo rm atio n in th e fo rm ( s e e s e ctio n 1 1 fo r in fo d eta ils ) b . A pplic a tio n S ubm is sio n i . A fte r a n a pplic a nt s u bm it s th eir a pplic a tio n, th e “ w ebsit e ” p ro vid es th e a pplic a nt a s tu dent n um ber i i. A fte r s u bm is sio n, th e a pplic a tio n is e va lu a te d b y th e s yste m ( s e e s e ctio n 2 cii fo r a pplic a tio n s ta tu se s) c . A pplic a tio n S ta tu s i . B elo w flo w d ia gra m d escrib es th e a pplic a tio n s ta tu s 1 . I F A pp is m is sin g d ata T H EN A pplic a tio n In co m ple te 2 . E LS E “ A pplic a tio n C om ple te a nd U nder R evie w / N o D ecis io n Y et” i i. S ta tu s’ in clu de: 1 . A dm it 2 . A dm it w it h A id 3 . R eje ct d . A pplic a tio n Q uerie s i . A n a pplic a nt c a n q uery th e s ta tu s o f th eir a pplic a tio n fr o m th e “ w ebsit e ” u sin g th eir s tu dent n um ber i i. U pdate p ers o nal o r a ca dem ic in fo rm atio n 3 . G ra duate S ecre ta ry a . G S Q uerie s i . A G ra duate S ecre ta ry m ay u pdate [M ODIF Y ] th e a pplic a tio n s ta tu s i i. S earc h fo r a n a pplic a nt u sin g th eir la st n a m e o r S tu dent N um be r i ii. U pdate a n a pplic a nts ’ p ers o nal o r a ca dem ic in fo rm atio n i v . G iv e n a S em este r o r Y ear o r D egre e P ro g ra m , g enera te th e lis t o f g ra duate a pplic a nts v . G iv e n th e S em este r o r Y ear o r D egre e P ro g ra m , g enera te th e lis t o f a dm it te d s tu dents v i. G iv e n th e S em este r o r Y ear o r D egre e P ro g ra m , g enera te to ta l # o f a pplic a nts , to ta l # a dm it te d, to ta l # r e je cte d, a nd a vg G RE s co re fo r a dm it te d s tu dents v ii. G iv e n th e S em este r o r Y ear o r D egre e P ro g ra m g enera te a lis t o f s tu dents c le are d fo r g ra duatio n v iii. G iv e n th e S em este r o r Y ear o r D egre e P ro g ra m g enera te a lis t o f a lu m ni a nd th eir e m ail a ddre sse s i x . G enera te to ta l lis t o f c u rre nt s tu dents ( b y d egre e o r b y a dm it y e ar) x . C hange S tu dent’s F acu lt y A dvis o r, g iv e n a s tu dent n um be r. x i. G enera te th e lis t o f c o urs e s a nd g ra des, g iv e n a s tu dent n um be r. x ii. G enera te lis t o f a ll a dvis e es, g iv e n a fa cu lt y a dvis o r n am e 4 . A lu m ni a . A lu m ni Q uerie s i . R equest th eir tr a nscrip t i i. U pdate th eir p ers o nal in fo rm atio n u sin g th eir s tu dent ID to a uth entic a te ( s e e s e ctio n 9 ) 5 . C urre nt G ra duate S tu dent a . S tu dent E nro llm ent i . A S tu dent is e nro lle d o nce a pplic a tio n h as b een c o m ple te d a nd a pplic a tio n d ecis io n is a dm it te d o r a dm it t e d w it h a id . S ee s e ctio n 2 d o n a pplic a tio n s ta tu se s. b . S tu dent C ours e R egis tr a tio n i . A S tu dent m ay e nro ll in a c o urs e . S ee s e ctio n 1 2 o n c o urs e in fo rm atio n. c . S tu dent G ra duatio n A pplic a tio n i . A s tu dent m ay v is it th e “ w ebsit e ” a nd a pply fo r g ra d uatio n 1 . S yste m “ a udit s ” if s tu dent h as s a tis fie d p ro g ra m r e q uir e m en ts ( s e e s e ctio n 1 4 o n g ra duatio n r e quir e m ents ) a . I f th e s tu dent is n ot c le are d fo r g ra duatio n th ey a re i n fo rm ed w hat r e quir e m ents th ey a re m is sin g d . Q uerie s i . G enera te th e lis t o f c o urs e s a nd g ra des, g iv e n a s tu dent n um be r. i i. V ie w c o urs e lis t i ii. V ie w g ra des 6 . F acu lt y A dvis o r a . Q uerie s i . G enera te th e lis t o f c o urs e s a nd g ra des, g iv e n a s tu dent n um be r. i i. V ie w a ll d ata a bout a n a pplic a nt b ut c a nno t e nte r a r e vie w i ii. V ie w th eir a dvis e es’ c o urs e s ta ke n b ut c a nnot u pdate th e c o urs e s. i v . G enera te a lis t o f a ll a dvis e es 7 . F acu lt y In str u cto r a . Q uerie s i . G enera te th e lis t o f c o urs e s a nd g ra des, g iv e n a s tu dent n um be r. i i. E nte r g ra des fo r th e s tu dents in th e c o urs e s th ey a re te ach in g ( i. e ., c o urs e s fo r w hic h th ey a re th e in str u cto r). S ee s e ctio n 1 2 o n g ra d es. 8 . F acu lt y R evie w ers a . Q uerie s i . S earc h fo r a n a pplic a nt u sin g th eir la st n a m e o r S tu dent N um be r i i. G enera te th e lis t o f c o urs e s a nd g ra des, g iv e n a s tu dent n um be r. i ii. R evie w a s tu dent’s a pplic a tio n i v . E nte r th eir r e vie w in to a r e vie w fo rm w hic h is s to re d in th e s yste m . 9 . P ers o nal In fo rm atio n a . A ll p ers o nal in fo rm atio n m ust b e p ro te cte d fr o m u se rs w ho d o n ot h ave a cce ss. F or r e ad/w rit e a llo w ance s, s e e s e ctio n 9 c b . T he fo llo w in g in fo rm atio n m ust b e p ro vid e d b y a ll a pplic a nts i . N am e i i. A ddre ss 1 . S tr e et N um ber 2 . C it y 3 . S ta te 4 . Z ip i ii. P hone N um bers 1 . W ork 2 . M obile 3 . H om e i v . E m ail a ddre ss c . R ead/W rit e A llo w ance s fo r P ers o nal In fo rm atio n i . R ead O nly 1 . F acu lt y A dvis o r 2 . G ra duate S ecre ta ry i i. R ead/W rit e 1 . S tu dent 2 . A lu m ni 3 . A pplic a nt 4 . G ra duate S ecre ta ry 1 0. A ca dem ic In fo rm atio n a . P rio r D egre es ( m ax 2 ) b . D egre e y e ars c . G PA p er d egre e d . U niv /C olle ge o f e ach d egre e e . G RE S co re i . V erb al i i. A naly tic a l i ii. Q uantit a tiv e 1 1 . O th er A pplic a tio n In fo rm atio n a . P ro gra m S ought [M S o r M SE] b . A pplic a nt D ate R ece iv e d ( M M/D D/Y YY) c . A dm is sio n D ate R equest ( W 2023, S 2022 , o r F 2022) d . ( o ptio nal) A re a o f In te re st e . P rio r W ork E xp erie nce ( 1 o r 2 s e nte nce s) f . R eco m mendatio n L ette rs ( m ax 3 ) i . A uth ors 1 . N am e 2 . E m ail a ddre ss 3 . T it le 4 . A ff ilia tio n 1 2. D ata base U niv e rs it y a . S tu dents m ust b e a ble to e nro ll a nd r e gis te r fo r c o urs e s th ro u gh th e D BU . S ee s e ctio n 1 2c o n c o urs e r e gis tr a tio n. b . C ours e In fo rm atio n i . T it le i i. C ours e n um ber i ii. S ectio n n um ber i v . S em este r v . N um ber o f c o urs e c re dit s c . C ours e R egis tr a tio n In fo rm atio n i . C ours e – s e e s e ctio n 1 2b o n c o urs e in fo rm atio n i i. C ours e s e ctio n n um ber i ii. S em este r i v . S tu dent id entif ic a tio n v . I n str u cto r in fo rm atio n v i. G ra de 1 . G ra de c a n b e e it h er A ,B ,C o r F 1 3. G ra duatio n A pplic a tio n a . S tu dents m ust fu lf ill b elo w r e quir e m ents in o rd e r to g ra d uate i . H as ta ke n 1 0 c o urs e s ( 3 c re dit s e ach ) to ta llin g to 3 0 c re d it s h ours i i. H as ta ke n 3 o ut o f th e 4 c o re c o urs e s: C S51 0, C S511 , IM SE52 12, IM SE 5 13 i ii. H as a t m ost 2 g ra des b elo w B i v . H as a m in im um G PA o f 3 .0 b . G ra duatio n s ta tu se s a re lim it e d to : i . C le are d i i. N ot C le are d P ro cess W ork flo w 1 . A pplic a tio n P ro ce ss a . A n A pplic a nt fills o ut p ers o nal a nd a ca de m ic in fo rm atio n. b . A n A pplic a nt is n otif ie d if a ny r e quir e d fie ld s a re m is sin g. c . A n A pplic a nt s u bm it s a n a pplic a tio n o nce a ll r e q uir e d fie ld s a re fille d. d . A n A pplic a nt m ay c h eck o n th e s ta tu s o f th eir a pplic a tio n. e . A d ate th e a pplic a tio n w as r e ce iv e d b y th e d epartm en t is r e co rd e d. 2 . A dm is sio n P ro ce ss a . T he G S s co re s th e a pplic a tio n. b . T he fa cu lt y r e vie w s th e a pplic a tio n. c . T he C hair o f th e a dm is sio ns w it h th e h elp o f th e G S a dm it s , a dm it s w it h a id , o r r e je cts a n a pplic a nt. d . T he a dm is sio n o r r e je ctio n d ate is r e co rd ed. 3 . R egis tr a tio n a nd G enera l S tu dent P ro ce ss a . A S tu dent a cce pts th e a dm is sio n d ecis io n a nd th e G S a dds th e S tu dent in th e s yste m . b . A S tu dent w ho h as b een e nro lle d in th e U niv e rs it y r e g is te rs fo r a c la ss. c . A F acu lt y m em ber w ho in str u cts a c la ss m ay u pdate a s tu dent’s g ra d e d . A S tu dent o r F acu lt y m em ber m ay c h eck o n th eir g ra d es. 4 . G ra duatio n P ro ce ss a . S tu dent a pply fo r g ra duatio n b y fillin g o u t a n o nlin e fo rm w it h lis t o f c o urs e s th ey w ill ta ke to m eet g ra duatio n r e quir e m en ts b . S yste m a uto m atic a lly c h eck if g ra duatio n r e q uir e m en ts a re m et c . I f r e quir e m ents a re m et, s tu dent g ra duatio n a pplic a tio n s ta tu s c h anged to ‘ c le are d’. O th erw is e , s ta tu s is ‘‘ n ot c le are d’ d . G S g enera te s th e lis t o f g ra duatin g s tu den ts ( s tu dents w hose g ra d uatio n a pplic a tio n s ta tu s is ‘c le are d’) . G S o nly c h ecks th e “ c le are d ” s tu dents a nd a ppro ve s th eir g ra duatio n b y c h eckin g th eir fo ld er a nd tr a n scrip t. e . I f s tu dent g ra duatio n a pplic a tio n s ta tu s is ‘c le are d ’, G S th en r e m ove s th e s tu dent f r o m th e ‘g ra duate s tu dent’ lis t a nd a dds th em to a lu m ni lis t. E nro llm en t i n fo rm atio n m ust n ot b e r e m ove d f . A lu m ni a re th en a ble to e dit th eir p ers o na l in fo rm atio n u sin g th eir s tu dent n um be r t o a uth entic a te . A lu m ni a re a ble to v ie w a lis t o f th e c o urs e s th ey to ok a nd th eir g ra des
Determine technical capabilities – you may use any implementation technology as long as you will be able to do a demonstration of it. Create the build ERD based on business functionality required Det
Business Requirements Applicant Applicant Creation An applicant must be able to access a “website” to see all available actions that can be taken An applicant must provide personal information in the form (see section 9 for info details) Application Application Creation An applicant must provide academic information in the form (see section 10 for info details) An applicant must provide application specific information in the form (see section 11 for info details) Application Submission After an applicant submits their application, the “website” provides the applicant a student number After submission, the application is evaluated by the system (see section 2cii for application statuses) Application Status Below flow diagram describes the application status IF App is missing data THEN Application Incomplete ELSE “Application Complete and Under Review / No Decision Yet” Status’ include: Admit Admit with Aid Reject Application Queries An applicant can query the status of their application from the “website” using their student number Update personal or academic information Graduate Secretary GS Queries A Graduate Secretary may update [MODIFY] the application status Search for an applicant using their last name or Student Number Update an applicants’ personal or academic information Given a Semester or Year or Degree Program, generate the list of graduate applicants Given the Semester or Year or Degree Program, generate the list of admitted students Given the Semester or Year or Degree Program, generate total # of applicants, total # admitted, total # rejected, and avg GRE score for admitted students Given the Semester or Year or Degree Program generate a list of students cleared for graduation Given the Semester or Year or Degree Program generate a list of alumni and their email addresses Generate total list of current students (by degree or by admit year) Change Student’s Faculty Advisor, given a student number. Generate the list of courses and grades, given a student number. Generate list of all advisees, given a faculty advisor name Alumni Alumni Queries Request their transcript Update their personal information using their student ID to authenticate (see section 9) Current Graduate Student Student Enrollment A Student is enrolled once application has been completed and application decision is admitted or admitted with aid. See section 2d on application statuses. Student Course Registration A Student may enroll in a course. See section 12 on course information. Student Graduation Application A student may visit the “website” and apply for graduation System “audits” if student has satisfied program requirements (see section 14 on graduation requirements) If the student is not cleared for graduation they are informed what requirements they are missing Queries Generate the list of courses and grades, given a student number. View course list View grades Faculty Advisor Queries Generate the list of courses and grades, given a student number. View all data about an applicant but cannot enter a review View their advisees’ courses taken but cannot update the courses. Generate a list of all advisees Faculty Instructor Queries Generate the list of courses and grades, given a student number. Enter grades for the students in the courses they are teaching (i.e., courses for which they are the instructor). See section 12 on grades. Faculty Reviewers Queries Search for an applicant using their last name or Student Number Generate the list of courses and grades, given a student number. Review a student’s application Enter their review into a review form which is stored in the system. Personal Information All personal information must be protected from users who do not have access. For read/write allowances, see section 9c The following information must be provided by all applicants Name Address Street Number City State Zip Phone Numbers Work Mobile Home Email address Read/Write Allowances for Personal Information Read Only Faculty Advisor Graduate Secretary Read/Write Student Alumni Applicant Graduate Secretary Academic Information Prior Degrees (max 2) Degree years GPA per degree Univ/College of each degree GRE Score Verbal Analytical Quantitative Other Application Information Program Sought [MS or MSE] Applicant Date Received (MM/DD/YYY) Admission Date Request (W2023, S2022, or F2022) (optional) Area of Interest Prior Work Experience (1 or 2 sentences) Recommendation Letters (max 3) Authors Name Email address Title Affiliation Database University Students must be able to enroll and register for courses through the DBU. See section 12c on course registration. Course Information Title Course number Section number Semester Number of course credits Course Registration Information Course – see section 12b on course information Course section number Semester Student identification Instructor information Grade Grade can be either A,B,C or F Graduation Application Students must fulfill below requirements in order to graduate Has taken 10 courses (3 credits each) totalling to 30 credits hours Has taken 3 out of the 4 core courses: CS510, CS511, IMSE5212, IMSE 513 Has at most 2 grades below B Has a minimum GPA of 3.0 Graduation statuses are limited to: Cleared Not Cleared Process Workflow Application Process An Applicant fills out personal and academic information. An Applicant is notified if any required fields are missing. An Applicant submits an application once all required fields are filled. An Applicant may check on the status of their application. A date the application was received by the department is recorded. Admission Process The GS scores the application. The faculty reviews the application. The Chair of the admissions with the help of the GS admits, admits with aid, or rejects an applicant. The admission or rejection date is recorded. Registration and General Student Process A Student accepts the admission decision and the GS adds the Student in the system. A Student who has been enrolled in the University registers for a class. A Faculty member who instructs a class may update a student’s grade A Student or Faculty member may check on their grades. Graduation Process Student apply for graduation by filling out an online form with list of courses they will take to meet graduation requirements System automatically check if graduation requirements are met If requirements are met, student graduation application status changed to ‘cleared’. Otherwise, status is ‘‘not cleared’ GS generates the list of graduating students (students whose graduation application status is ‘cleared’). GS only checks the “cleared” students and approves their graduation by checking their folder and transcript. If student graduation application status is ‘cleared’, GS then removes the student from the ‘graduate student’ list and adds them to alumni list. Enrollment information must not be removed Alumni are then able to edit their personal information using their student number to authenticate. Alumni are able to view a list of the courses they took and their grades
Determine technical capabilities – you may use any implementation technology as long as you will be able to do a demonstration of it. Create the build ERD based on business functionality required Det
Project Presentation Project presentation will take 30-40 minutes. Points will be deducted for taking less time. Time may go over depending on questions asked during the presentation and demomstration of the application. Team will decide who will present and demo the project. Preparation and atual presentation count as part of “work performed” (equal work for all team members). Presentation: Introduce team members and roles performed Complete ERD – do not describe the ERD itself, descibe what changes took place between the initial and final version Business requirements – explain how your requirements change over time (i.e., what changed? There are always changes to interpretation of requirements, points of view, what to include/exclude …..) How did your Build ERD change over time? Describe the database system you built for the application – what DBMS did you use and why, what databases did you build (and how they changed), etc. How you built the application front end (web pages, forms, command line, etc.) ….. How you determined what and how to test – prepopulate database, extra frontend pages, etc. Show your test plan functionality list and for each test case if the test was a pass/partial/fail for that piece of functonality plus final overall status What went well and what what didn’t go well on the project If you started the project over again what would you do differently Overall lessons learned Demonstration of the application