lab assigment 111
Ukoirala
javaproject.zipAssign 10.docx
Assignment 10: Chapter 10
Complete Programming Challenges - Problems 7 ( File Encryption Filter ) and 8 ( File Decryption Filter ).
In both cases, make sure you create a custom Exception to let the user know, when decrypting if the input file was not encrypted ( read a random character, apply your decryption algorithm and see if the result is in the ASCII range ) or if the input file is not clear text, when encrypting ( read a random character and see if it is in the ASCII range, if not do not encrypt )
The solution class should have both encyption and decryption methods, thus a single class for both problems and two classes for the two custom exceptions.
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
assign 5.docx
Assignment 5: Chapter 5
Chapter 5 - Programming Challenge 24: A Game of Twenty One
Additional requirements:
· Solution, must be object oriented design remonstrated with a driver.
· Welcome the user with a message that you read from a file called "input.txt".
· Write the results of the game to the terminal and also to the output file called, "output.txt" and remind the user to look at that file if he/she wants to.
You only need to submit the designs, input/output files ( if applicable ) source code ( .java and not the project or the .class ) files of all the classes you'll implement and the driver program for the problem. ( Do not submit the whole project folder and irrelevant files. )
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Assign 6.docx
Assignment 6: Chapter 6
Attached Files:
·
FuelGauge Class UML.tif
(95.717 KB)
·
Odometer Class UML.tif
(222.93 KB)
Chapter 6 - Programming Challenge 12: Car-Instrument Simulator
You only need to submit the source code ( .java and not the project or the .class ) files of all the classes you'll implement and the driver program for the problem.
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Assign 7.docx
Assignment 7: Chapter 7
Chapter 7 - Programming Challenge 2: Payroll Class
You only need to submit the source code ( .java and not the project or the .class ) files of all the classes you'll implement and the driver program for the problem. Of course, code does not mean anything without design, so you still have to submit that as well. Make sure your implementation is using ArrayList not just primitive array.
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Assign 8.docx
Assignment 8: Chapter 8
Attached Files:
·
Morse Class UML.tif
(43.492 KB)
Programming challenge 16. ( Note: use a parallel array of char[] and String[] to keep the mapping between ASCII and Morse codes )
You only need to submit the source code ( .java and not the project or the .class ) files of all the classes you'll implement and the driver program for the problem. Submit your flowchart or pseudo code. Add all your files in an archive file, name the archive file as specified at the beginning of the semester, and submit the single archive file on eCampus before the due date. No assignments will be accepted as an email submission or as a hard copy after the due date.
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Morse Class UML.tif
Assign 9.docx
Assignment 9: Chapter 9
Attached Files:
·
CompleteObjectList.png
(66.489 KB)
·
CourseGrades Class UML.tif
(234.535 KB)
Programming challenge 5.
You only need to submit the source code ( .java and not the project or .class ) files of all the classes you'll implement and the driver program for the problem. Submit your flowchart or pseudo code. Add all your files in an archive file, name the archive file as specified at the beginning of the semester, and submit the single archive file on eCampus before the due date. No assignments will be accepted as an email submission or as a hard copy after the due date.
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
CompleteObjectList.png
CourseGrades Class UML.tif
Assignment 2.docx
Assignment 2: Chapter 2
Complete Programming Challenges 17, 18 and submit your source codes and designs ( .java and not project or .class ). Submit it using the naming standard discussed on the first day in this course.
Note: You are not allowed to use import statement(s). You have to use absolute path for all classes used in your code(s).
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Assignment 3.docx
Assignment 3: Chapter 3
Your assignment in this chapter is to solve the programming challenges 2,4, and 9. You need to submit the designs, source codes ( .java not the project or the .class ) files of all the classes you'll implement and the driver program for each problem.
Focus on chapter coverage:
- Object oriented programming solution ( object + driver )
- Proper UML + flowcharts
- proper constructor
- avoid stale data and shadowing
- demonstrate object's methods
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Assignment4.docx
Assignment 4: Chapter 4
Your assignment in this chapter is to solve the programming challenge 14. You only need to submit the source code ( .java not the project or the .class ) files of all the classes you'll implement and the driver program for the problem. You still need to submit your designs, remember code without design is not a code - syllabus requirement still applies for all assignments.
What you need to think about:
· - You can use relative path and/or import statements and/or packages for classes
· - Decimal formatting
· - Switch receiving string data type
· - Conditional operator
· - String formatting with decimal value
· - Object oriented solution ( ch 3 )
/**
*Description: <Meaningful description>
*Class: <Semester> - <COSC 1437.xxxxx>
*Assignment1: <yyyyyyyyyyy>
*Date: <##.##.##>
*@author <your name>
*@version <#.#.#>
*/
For each method, you will also be required to create docstring as follows:
/**
* @param args <Meaningful description>
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
Final Project.docx
Final Project
Attached Files:
·
FinalProject.zip
(73.691 KB)
See attachment for details.
Due on the final day by the end of the day. No late submission will be accepted even if it is due to technical problems. )
What to use in your completed code
Get input from file. Ask user at least a single question and read at least one answer. Use at least a single method from Math class. Use at least one overloaded constructor. Use at least one if-else-if, while, for, and enhanced for loops. Use methods to pass and return identifiers and objects. Pass arrays to/from methods. Use at least a method to sort the array in the project. Use inheritance and polymorphism. Use exception handling. Use input validation. Pass the input and output files as commandline arguments.
/**
*Description: This program will displays a string without any user interaction
*Class: Fall - COSC 1437.81002
*Assignment1: Hello World
*Date: 08/15/2011
*@author Zoltan Szabo
*@version 0.0.0
*/
For each method, you will also be required to create docstring as follows:
/**
* @param String as args
* @return Termination code as int, 0 for normal, anything else is error condition
* @throws Nothing is implemented
*/
All assignments must be submitted on eCampus under Assignments attached as a single compressed file ( no hard copy needed )
Assignment#Lastname####.zip
Where Assignment# is the applicable assignment number listed in the syllabus and Lastname### is the submitting student’s last name and last four digits of the student’s studentID.
You can submit your assignments early using the applicable assignment link if it is active on eCampus, but no assignments will be accepted after the due date/time. No assignments will be accepted that are sent to the instructor over email. Only eCampus submissions will be counted toward assignment grade.
i.e Assignment1Szabo1234.zip
Flowcharts/UML and Pseudo code
All assignment questions must show design flowchart/UML and/or pseudo code unless otherwise stated for the assignment by your instructor. Flowcharts/UMLs can be created via an application (DIA) or drawn by hand and photographed for submission.
FinalProject.pdf
Final Project - Credit card numbers and the case of Mobius Duck
In this project, you are assisting an investigation. The investigator asked you to help him determine the validity of credit card numbers located in a case of Mobius Duck, case number 20150510-001.
Your task is to:
– Read the data listed below “Data to Evaluate” from a file.
– Evaluate each number to see if they are representing a possible credit card number.
– Validate each credit card number to see if they are a valid number.
– Store the valid numbers and invalid numbers in a separate array.
– Write the contents of validated credit card number array into a file called “valid_cards.txt”.
– Write the invalid credit card number array to a file called “invalid_numbers.txt”.
– Make sure to include the issuer for each group of credit card numbers identified.
– Your application should work with any number of credit card entries.
Turn in:
– Source code ( .java ) files of all classes and driver class.
– Completed UML for application classes.
– Flow chart for every method that contains beyond sequential logic flow.
– Generated javadocs structure.
– Input and output files
Grading:
– Naming standard followed for project files – 2%
– Input and output files – 2%
– Javadoc structure – 5%
– Project compiled without error – 91%
– Proper use of internal comments, docstrings, and tags – 5%
– Self documenting field, identifier, method, static, final, and class identifiers - 5%
– Properly validated input and output files - 5%
– Properly used arrays to store data - 5%
– Correct output calculated by the Luhn algorithm and card number issuer identified – 71%
Extra Credit:
- Implement the full Issuer IIN Range instead of the simplified list.
How to validate Credit Card Numbers? Most credit card number can be validated using the Luhn algorithm, which is more or a less a glorified Modulo 10 formula!
The Luhn Formula:
• Drop the last digit from the number. The last digit is what we want to check against • Reverse the numbers • Multiply the digits in odd positions (1, 3, 5, etc.) by 2 and subtract 9 to all any result higher than 9 • Add all the numbers together • The check digit (the last number of the card) is the amount that you would need to add to get a multiple
of 10 (Modulo 10)
Luhn Example:
Steps Total Original Number: 4 5 5 6 7 3 7 5 8 6 8 9 9 8 5 5 Drop the last digit: 4 5 5 6 7 3 7 5 8 6 8 9 9 8 5 Reverse the digits: 5 8 9 9 8 6 8 5 7 3 7 6 5 5 4 Multiple odd digits by 2: 10 8 18 9 16 6 16 5 14 3 14 6 10 5 8 Add digits from line above 1 8 9 9 7 6 7 5 5 3 5 6 1 5 8 Add all numbers: 1 8 9 9 7 6 7 5 5 3 5 6 1 5 8 85 Mod 10: (85 + X) modulo 10 = 0 , thus X=5 (last digit of card)
List of credit card number formats Credit Card Issuer Starts With ( IIN Range ) Length ( Number of digits )
American Express 34, 37 15 Diners Club - Carte Blanche 300, 301, 302, 303, 304, 305 14 Diners Club - International 36 14 Diners Club - USA & Canada 54 16
Discover 6011, 622126 to 622925, 644, 645, 646, 647, 648, 649, 65
16
InstaPayment 637, 638, 639 16 JCB 3528 to 3589 16 Laser 6304, 6706, 6771, 6709 16-19
Maestro 5018, 5020, 5038, 5893, 6304, 6759, 6761, 6762, 6763
16-19
MasterCard 51, 52, 53, 54, 55 16-19 Visa 4 13-16 Visa Electron 4026, 417500, 4508, 4844, 4913, 4917 16
Data to Evaluate 3158539628375348 3337465828248404 3112804683572030 3112804683572033 5435528978467581 6706465468107999 6304362971054667 6706169762827894 6706169762827892 4844104341377697 4913405490886727 4844885754351829 4844885754351822 6371473570875275 6381475006869978 6389057917814806 347100734345549 347100734345543 6011162533805000 6011621663574413 6011824617460743 6011824617460745 6389057917814802 4539318768050385 36880982786892 36845793345501 36661154562232 36661154562234 5893329089846994 6761680165952016 6763100400984029 6763100400984022 5127043299122389 5330838017737340 5429168755154025 5429168755154023 375354034606481 379570632133224 4485521241443135 4532916206508075 4532916206508076 5590976687287124 5540641137519895 5540641137519892 30522070708059 30066552673241 30365487186802 30365487186801
Simplified Issuer Codes for Final Project:
VISA: 45 44 MasterCard: 51 53 American Express (AMEX): 37 34 Discover: 60 JCB: 31 33 Diners Club - North America: 54 55 Diners Club - Carte Blanche: 30 Diners Club - International: 36 Maestro: 58 LASER: 67 Visa Electron: 48 49 InstaPayment: 63
- Final Project - Credit card numbers and the case of Mobius Duck
- How to validate Credit Card Numbers?
- The Luhn Formula:
- Luhn Example:
- List of credit card number formats
- Simplified Issuer Codes for Final Project:
