Date format converter Program plan: “DateFormatConverter.java”: Import required packages. Define the class “DateFormatConverter”. Declare required variables. Define an array and assign it with the months. Define the “main()” method. Do until the user enters other than “Y” or “y”. Inside the “try” block, Get the date from the user. Trim the input. Store the month value in a variable. Check if that value is less than 0. Assign “false” to “validInput”. Throw an exception. Check if month value is less than 1 or greater than 12. Assign “false” to “validInput”. Throw an exception. Otherwise, Get the date value and store it in a variable. Call the function “dayCheck()”. Catch “MonthException”. Print the error message. Check if the function “validInput()” returns true. Print the month name and its date. Get the response from the user whether the user wants to do it again or not. Give function to convert string to integer for month. Get the position of “/”. Check if that position is equal to 2. Return the value. Check if that position is equal to 1. Return the integer value. Otherwise, Return -1. Give function to convert string to integer for day. Get the number of characters. Check if that number is equal to 2. Return the value. Check if that number is equal to 1. Return the integer value. Otherwise, Return -1. Function definition to convert ASCII value to integer. Switch to the digit. Assign the value according to the character digit. Give function definition to check the day. Inside the “try” block, Switch to the month number. If the month number is 1, 3, 5, 7, 8, 10 and 12, Check if the day is less than 1 or greater than 31. Assign “false” to “validInput”. Print the error message. Otherwise, Assign “true” to “validInput”. Break the case. If the month number is 4, 6, 9 and 11, Check if the day is less than 1 or greater than 30. Assign “false” to “validInput”. Print the error message. Otherwise, Assign “true” to “validInput”. Break the case. If the month number is 2, Check if the day is less than 1 or greater than 29. Assign “false” to “validInput”. Print the error message. Otherwise, Assign “true” to “validInput”. Break the case. Inside the “catch” block for “DayException”, print the error message. “DayException.java”: Define the exception class “DayException”. Define a default constructor. Call the parent class’s method. Define two parameterized constructors. Call the parent class’s method by passing a message. “MonthException.java”: Define the exception class “MonthException”. Define a default constructor. Call the parent class’s method. Define two parameterized constructors. Call the parent class’s method by passing a message.

Question

Want to see the full answer?

Answer 1

Question

Chapter 9, Problem 3PP

Program Plan Intro

Date format converter

Program plan:

“DateFormatConverter.java”:

Import required packages.

Define the class “DateFormatConverter”.

Declare required variables.

Define an array and assign it with the months.

Define the “main()” method.

Do until the user enters other than “Y” or “y”.

Inside the “try” block,

Get the date from the user.

Trim the input.

Store the month value in a variable.

Check if that value is less than 0.

Assign “false” to “validInput”.

Throw an exception.

Check if month value is less than 1 or greater than 12.

Assign “false” to “validInput”.

Throw an exception.

Otherwise,

Get the date value and store it in a variable.

Call the function “dayCheck()”.

Catch “MonthException”.

Print the error message.

Check if the function “validInput()” returns true.

Print the month name and its date.

Get the response from the user whether the user wants to do it again or not.

Give function to convert string to integer for month.

Get the position of “/”.

Check if that position is equal to 2.

Return the value.

Check if that position is equal to 1.

Return the integer value.

Otherwise,

Return -1.

Give function to convert string to integer for day.

Get the number of characters.

Check if that number is equal to 2.

Return the value.

Check if that number is equal to 1.

Return the integer value.

Otherwise,

Return -1.

Function definition to convert ASCII value to integer.

Switch to the digit.

Assign the value according to the character digit.

Give function definition to check the day.

Inside the “try” block,

Switch to the month number.

If the month number is 1, 3, 5, 7, 8, 10 and 12,

Check if the day is less than 1 or greater than 31.

Assign “false” to “validInput”.

Print the error message.

Otherwise,

Assign “true” to “validInput”.

Break the case.

If the month number is 4, 6, 9 and 11,

Check if the day is less than 1 or greater than 30.

Assign “false” to “validInput”.

Print the error message.

Otherwise,

Assign “true” to “validInput”.

Break the case.

If the month number is 2,

Check if the day is less than 1 or greater than 29.

Assign “false” to “validInput”.

Print the error message.

Otherwise,

Assign “true” to “validInput”.

Break the case.

Inside the “catch” block for “DayException”, print the error message.

“DayException.java”:

Define the exception class “DayException”.

Define a default constructor.

Call the parent class’s method.

Define two parameterized constructors.

Call the parent class’s method by passing a message.

“MonthException.java”:

Define the exception class “MonthException”.

Define a default constructor.

Call the parent class’s method.

Define two parameterized constructors.

Call the parent class’s method by passing a message.

Expert Solution & Answer

Want to see the full answer?

Check out a sample textbook solution

See solution

Students have asked these similar questions

This is a question that I have and would like someone who has experiences with scene graphs and entity component systems to answer.For context, I am currently implementing a game engine and currently I am debating on our current design.Our current design is we have a singular game component class that every component inherits from. Where we have components like SpriteRendererComponent, Mehs Component, etc. They inherit from this GameComponent class. The point of this is being able to have O(1) access to the scene to being able to modify components to attach more components with the idea of accessing those components to specific scene objects in a scene.Now, my question is what kinds of caveauts can this cause in terms of cache coherence? I am well aware that yes its O(1) and that is great but cache coherence is going to be really bad, but would like to know more explicit details and real-life examples such as write in RAM examples on how this is bad. A follow-up question that is part…

Q4: Consider the following MAILORDER relational schema describing the data for a mail order company. (Choose five only). PARTS(Pno, Pname, Qoh, Price, Olevel) CUSTOMERS(Cno, Cname, Street, Zip, Phone) EMPLOYEES(Eno, Ename, Zip, Hdate) ZIP CODES(Zip, City) ORDERS(Ono, Cno, Eno, Received, Shipped) ODETAILS(Ono, Pno, Qty) (10 Marks) I want a detailed explanation to understand the mechanism how it is Qoh stands for quantity on hand: the other attribute names are self-explanatory. Specify and execute the following queries using the RA interpreter on the MAILORDER database schema. a. Retrieve the names of parts that cost less than $20.00. b. Retrieve the names and cities of employees who have taken orders for parts costing more than $50.00. c. Retrieve the pairs of customer number values of customers who live in the same ZIP Code. d. Retrieve the names of customers who have ordered parts from employees living in Wichita. e. Retrieve the names of customers who have ordered parts costing less…

Q4: Consider the following MAILORDER relational schema describing the data for a mail order company. (Choose five only). (10 Marks) PARTS(Pno, Pname, Qoh, Price, Olevel) CUSTOMERS(Cno, Cname, Street, Zip, Phone) EMPLOYEES(Eno, Ename, Zip, Hdate) ZIP CODES(Zip, City) ORDERS(Ono, Cno, Eno, Received, Shipped) ODETAILS(Ono, Pno, Qty) Qoh stands for quantity on hand: the other attribute names are self-explanatory. Specify and execute the following queries using the RA interpreter on the MAILORDER database schema. a. Retrieve the names of parts that cost less than $20.00. b. Retrieve the names and cities of employees who have taken orders for parts costing more than $50.00. c. Retrieve the pairs of customer number values of customers who live in the same ZIP Code. d. Retrieve the names of customers who have ordered parts from employees living in Wichita. e. Retrieve the names of customers who have ordered parts costing less than$20.00. f. Retrieve the names of customers who have not placed…