Create a courseexception class that extends exception and whose constructor receives a string that holds a college course’s department (for example, cis), a course number (for example, 101), and a number of credits (for example, 3). save the file as courseexception. java. create a course class with the same fields and whose constructor requires values for each field. upon construction, throw a courseexception if the department does not consist of three letters, if the course number does not consist of three digits between 100 and 499 inclusive, or if the credits are less than 0.5 or more than 6. save the class as course. java. write an application that establishes an array of at least six course objects with valid and invalid values. display an appropriate message when a course object is created successfully and when one is not. save the file as throwcourseexception. java

When making changes to optimize part of a processor, it is often the case that speeding up one type of instruction comes at the cost of slowing down something else. for example, if we put in a complicated fast floating-point unit, that takes space, and something might have to be moved farther away from the middle to accommodate it, adding an extra cycle in delay to reach that unit. the basic amdahl's law equation does not take into account this trade-off. a. if the new fast floating-point unit speeds up floating-point operations by, on average, 2ă—, and floating-point operations take 20% of the original program's execution time, what is the overall speedup (ignoring the penalty to any other instructions)? b. now assume that speeding up the floating-point unit slowed down data cache accesses, resulting in a 1.5ă— slowdown (or 2/3 speedup). data cache accesses consume 10% of the execution time. what is the overall speedup now? c. after implementing the new floating-point operations, what percentage of execution time is spent on floating-point operations? what percentage is spent on data cache accesses?