Write out Deliverables: use-case diagram, domain model & class diagram

Project Description (The 'LU Student Degree Audit'): This project (The LU Student Degree Audit') requires you to adopt a use-case driven object-oriented approach to develop a system to support the simulation of the LU Student Degree Audit of a particular student based on courses she/he took and what courses are still due upon students graduation, etc. Motivation: We live in a society guided by computers. For example, when we try to find out what courses you still need to take (and pass) in order to graduate, we would like to check that list immediately. This particular software deals with listing the courses passed by a particular student and what other courses are needed to graduate according a database of courses that are part of the student's major degree plan. The purpose of the LU Student Degree Audit is to dynamically display the passed courses for the given student and to accurately list the courses need for student's graduation. In this way, students and adviscrs would be able to use the LU Student Degree Audit effectively. The second purpose of the software is to publish the relevant and non-sensitive data into a website for the LU community to see the graduation rates of our students. Of course, this data should not identify any student's sensitive information - it should follow the F.E.R.P.A. law Difficulties: The LU Student Degree Audit is quite a complex task because of its dynamic behavior, that is, you need to display all the possibilities of courses remaining to be taken upon student's graduation. The software should have as input structure the degree plan of cach major of Computer Science. The LU Student Degree Audit should calculate the percentage of the degree progress (for example, 55% means that the student passed more than half of the degree requirements and he/she still has to take 45% more courses in order to graduate). The second input structure is the prerequisite chart of cach degree plan that should be encoded as a directed acyclic graph modeling the prerequisite chart we have displayed outside our office (for example, a student cannot take COSC 1337 Programming Fundamentals II if she/he did not passed COSC 1336 Programming Fundamentals I with a grade of 'B' or above). Structure: The software should include two data structures: 1. One database containing the list of all courses from the student's degree plan. 2. One directed acyclic graph representing the prerequisite chart of all courses involved in the degrcc plan. Most of the software methods wl be support methods. For example, there should be a method called calculateNumbertCmditHours String courscNamc) which will return the number of credit hours of cach course. There should a method called degrecPogress String Lnumber) for calculating the degree progress. For cxample, the number of undergraduate credit hours for B.Sc. in C.S. is 120 and the number of graduate credit hours for M.Sc. in C.S. is 34 (Thesis option) and 37 (Graduate Project option). All these degrees may involve some p 4302 Operating Systems and COSC 4304 Foundations of Programming for M.Sc. in C.S.). courses (Pre-Calculus for B.Sc. in C.S. and COSC Project Description (The 'LU Student Degree Audit'): This project (The LU Student Degree Audit') requires you to adopt a use-case driven object-oriented approach to develop a system to support the simulation of the LU Student Degree Audit of a particular student based on courses she/he took and what courses are still due upon students graduation, etc. Motivation: We live in a society guided by computers. For example, when we try to find out what courses you still need to take (and pass) in order to graduate, we would like to check that list immediately. This particular software deals with listing the courses passed by a particular student and what other courses are needed to graduate according a database of courses that are part of the student's major degree plan. The purpose of the LU Student Degree Audit is to dynamically display the passed courses for the given student and to accurately list the courses need for student's graduation. In this way, students and adviscrs would be able to use the LU Student Degree Audit effectively. The second purpose of the software is to publish the relevant and non-sensitive data into a website for the LU community to see the graduation rates of our students. Of course, this data should not identify any student's sensitive information - it should follow the F.E.R.P.A. law Difficulties: The LU Student Degree Audit is quite a complex task because of its dynamic behavior, that is, you need to display all the possibilities of courses remaining to be taken upon student's graduation. The software should have as input structure the degree plan of cach major of Computer Science. The LU Student Degree Audit should calculate the percentage of the degree progress (for example, 55% means that the student passed more than half of the degree requirements and he/she still has to take 45% more courses in order to graduate). The second input structure is the prerequisite chart of cach degree plan that should be encoded as a directed acyclic graph modeling the prerequisite chart we have displayed outside our office (for example, a student cannot take COSC 1337 Programming Fundamentals II if she/he did not passed COSC 1336 Programming Fundamentals I with a grade of 'B' or above). Structure: The software should include two data structures: 1. One database containing the list of all courses from the student's degree plan. 2. One directed acyclic graph representing the prerequisite chart of all courses involved in the degrcc plan. Most of the software methods wl be support methods. For example, there should be a method called calculateNumbertCmditHours String courscNamc) which will return the number of credit hours of cach course. There should a method called degrecPogress String Lnumber) for calculating the degree progress. For cxample, the number of undergraduate credit hours for B.Sc. in C.S. is 120 and the number of graduate credit hours for M.Sc. in C.S. is 34 (Thesis option) and 37 (Graduate Project option). All these degrees may involve some p 4302 Operating Systems and COSC 4304 Foundations of Programming for M.Sc. in C.S.). courses (Pre-Calculus for B.Sc. in C.S. and COSC