Beruflich Dokumente
Kultur Dokumente
Credit Hours: 3
Prequisites:
Catalog Description:
Introduction to object-oriented software analysis, design, and development. Classes and objects. Object
composition and polymorphism. Sorting, searching, recursion. Strings using core classes. Inheritance and
interfaces. Graphic User Interfaces. Includes a comprehensive programming project.
Course Expectations:
After successful completion of this course, the student should be able to:
Textbook:
Introduction to JAVA Programming – Comprehensive Version, Eighth Edition, by Y. Daniel Liang, Prentice
Hall
Program #1
Purpose: Demonstrate the ability to create and execute a JAVA program using moderately complex control
structures.
Assignment: Write a program that creates a loan amortization table. The user of the program will supply
values for Initial Loan Principal, Annual Percentage Rate and Monthly Payment. The program should print
out the appropriate amortization table including the Number of Monthly Payments and the Total Interest
Paid for the life of the loan. The program should allow multiple runs of the table process and should allow
the user to compare runs in a tabular format (at least 4 different versions of the amortization table) at the
end of the program execution. Key data from each amortization table that should be displayed in the
comparison table are Initial Principle, Initial Payment, Annual Percentage Rate, Total Number of Payments
and Total Interest Paid.
Program #2
Purpose: Demonstrate the ability to create and execute a JAVA program that utilizes string manipulation to
solve a daily life problem.
Assignment: Write a program that will accept ten (or more) names (first and last names) and associated
birth-date. Your program should ask the user for how many people s/he wants to enter and then read the
names (first and last) and the corresponding birth-date. The birth-date must be entered in the following
format: MM/DD/YYYY. Your program should then use a menu that allows the user to display, search and
exit. Display should display the list of the entries, sorted by last name, first name, or birth-date as
requested by the user. Search should search for a specific entry by a specific field (last name, first name or
birth-date) as requested by the user. Exit should terminate the program when the user selects exit from the
menu.
Program #3
Purpose: Demonstrate the ability to create and execute a JAVA program that creates a multi-class
relationship among classes.
Player Class: The Player Class consists of at least two elements -- the player name and a collection of
scores for games. The score attribute is not used in Program #3 (and may be omitted in Program #3) but
will be needed in Program #4. Include in the class appropriate accessor and mutator methods for each
element in the class. You may have other attributes if needed.
Team Class: The Team class consists of at least 2 elements -- the name of the team and a collection of
players from the Player class. Include in the class appropriate accessor and mutator methods for each
element in the class. You may have other attributes if needed.
Input3 class: The Input3 class is provided for you. The Input3 class supplies data for your program. The
Input3 class has a public method, called getNextString, which returns a string with the input for your
program, one after the other. You must use this class to get the data for your program. See Input3.java on
eLearning to understand the class construction. Your program should be written in such a manner that the
grader could utilize an Input3 class with different numbers of teams and players and still give correct output
according to the data supplied.
Your program should display the roster of each team in alphabetical order by last name.
Program #4
Game Class: The Game Class consists of at least 3 elements – the names of two teams and an integer
number which identifies the game. Include in the class appropriate methods to show the output requested
below. You may have other attributes if needed.
Input4 class: The Input4 class is provided for you. The Input4 class supplies data for your program. The
Input4 class has a public method, called getNextString, which returns a string with the input for your
program, one after the other. You must use this class to get the data for your program. See Input4.java on
eLearning to understand the class construction. Your program should be written in such a manner that the
grader could utilize an Input4 class with different numbers of teams, players and games and still give
correct output according to the data supplied.
Display the roster of each team in alphabetical order by last name with the average score of each player for
the season.
Display the average score for the season against each of the two opponent teams.
Program #5
Assignment: Write a program that simulates a box fan. The box fan should have a speed control
mechanism for OFF, HIGH, MEDIUM, and LOW speeds. The fan blades should rotate at whatever speed
has been selected by the user. The fan should allow changing the fan state without terminating the
program. UML diagrams are not required for this assignment only.
Program #6
Purpose: Demonstrate the ability to write a complex Java application using Graphical User Interfaces.
Assignment: Form a three to four member programming team from students in your class. Write a
program to register students for a college. Students have names, addresses and courses. Implement the
interface class RegisterStudent. RegisterStudent has one method, public boolean register, which returns the
boolean value of true or false if the student is successfully registered for the course. Graduate students can
only register for graduate level courses, with a maximum course load of 6 credit hours, while undergraduate
students can only register for undergraduate level courses with a maximum course load of 12 credit hours.
Courses have a course number, credit hours and a minimum and maximum enrollment. The system should
graphically display a sorted list of registered courses for a student and/or a roster for each current course
with the names of the students enrolled in sorted order by last name. Demonstrate the correct operation of
your program by creating a driver program to load the student data base and the course data base from data
your group has created. The grader can then select students and register them for courses. Once the grader
has enrolled students into courses, the grader can request the report for a student or for a course.
Course Requirements:
There will be regularly assigned reading and homework problems. The homework problems will require
the student to spend time programming a computer.
Max Score
Partitioning 5%
Organization 5%
Program Design
Efficiency 5%
Coupling 5%
Source
Code Comments 10%
Formatting 5%
Coding Style Naming 5%
Capitalization 5%
Execution No crashes 5%
Program Execution Error Recovery 5%
Efficiency 5%
Nominal cases 25%
Specification
Special cases 5%
Documentation 10%
Total 100%
Keep in mind that you always want to write code that is easy to understand and is also easy to maintain.
Points Criteria
5 Partitioning: Is the required functionality spread logically across multiple methods (or classes)?
5 Organization: Is the overall program flow easy to follow? Is it easy for an outsider to figure out
how your software works?
5 Efficiency: Do the individual methods accomplish their given tasks as efficiently as possible? Are
unnecessary variables, loops, methods, and classes eliminated?
5 Coupling: Are methods (and classes) “loosely coupled”? Does each method only receive the data it
needs in order to accomplish its task? Are the “public” methods and variables appropriately so? Is
information as hidden as possible?
Comments: 10%
• Every file should have a header that includes your name, CS1337.nnn, & the homework number.
• Every class should have an extensive header comment explaining the purpose of the class.
• Every method should have comments explaining what it does, what its parameters are, and what
values it returns.
• Significant variables and sections of code should have comments explaining their purpose. Avoid
meaningless comments like “Declare the variables” or “This code adds one to the variable”.
Points Criteria
5 Formatting: Is code properly indented to indicate blocks?
5 Naming: Is everything (significant variables, classes, methods) named logically and descriptively?
(Not required for looping variables and throwaway variables.)
5 Capitalization:
• Package names are lowercase: java.io, java.net, etc.
• Class (and interface) names should be nouns, with the first letter of each internal word
capitalized: Loan, AmortizationTable, Person, HashMap
• Method names should be verbs, with the first letter lowercase & the first letter of each
internal word capitalized: run(), runFaster(), runForYourLife()
• Constants should be in all upper-case, with words separated by an underscore:
final int THIS_IS_A_CONSTANT = 1;
Execution: (45%)
This section has to do with how well your program runs. If your program does not compile, please be
aware that you may get no credit in this section.
Points Criteria
5 No crashes: Does the program actually run all the way through the simplest possible test case
without crashing?
5 Error Detection & Recovery: Does the program react well (does not crash) to unexpected or
inconsistent events or input? Are exceptions handled appropriately?
5 Efficiency: Does the program finish executing in a reasonable amount of time?
Points Criteria
25 Nominal case: Does the software correctly fulfill the requirements of the assignment for the
“expected” test cases?
5 Special cases: Does the software correctly handle unusual but legal test cases? Example: square
root of a negative number, interest payment higher than loan payment
For programming assignments that seem arbitrarily restricted (“your program must save 4 runs”, “your
program must accept up to 10 names”), points will be not taken off as long as your program meets at least
those requirements. You may exceed them without penalty.
Documentation (10%)
All assignments must be submitted with documentation. At a minimum, this should include an algorithm
report and a UML class diagram if you have more than a few classes.
You should describe the overall flow of your program at least at a high level. If there are any parts of the
program that are unusually complex, you should specify those parts in detail, using pseudocode or a
flowchart.
All make-up exams are scheduled during final week at the discretion of the instructor. Make-up exams are
only given to those students who coordinate the missing of an exam prior to the originally scheduled exam
date and time.
Course credit is only given for work assigned and scheduled in the course schedule. No extra work will be
assigned nor will extra credit be given for any extra work performed by a student.
Late assignments will not be accepted. Assignments are due at 10:00 P.M. on the day listed in the syllabus.
Class attendance is not recorded or required except for exam dates and times. There is a direct correlation
between class attendance and class performance. Those students who regularly attend class tend to make
significantly higher final grades than those who don’t.
Students are expected to be respectful to each other and to the course instructor. Disruptive behavior in the
class room is not tolerated.
Each student in the class is encouraged to join/form a study group. Members of each study group should
support one another in learning and understanding the course material.
All programming assignments and exams (other than the group project) are to be individual efforts. You
are not to collaborate with other students. Copying of programming assignments or exams, in whole or in
part, from other sources will be considered an act of scholastic dishonesty. This policy includes copying
from other students, from assignments from previous semesters or from the Internet.
Projects and exams determine grades. All exams are open book and open notes. The final grade will be
composed as follows:
Projects 25%
Exam 1 25%
Exam 2 25%
Exam 3 25%.
98-100 A+
92-97 A
90-91 A-
88-89 B+
82-87 B
80-81 B-
78-79 C+
72-77 C
70-71 C-
68-69 D+
62-67 D
60-61 D-
Below 60 F.
Off-campus, out-of-state, and foreign instruction and activities are subject to state law and
University policies and procedures regarding travel and risk-related activities. Information
regarding these rules and regulations may be found at the website address http://
www.utdallas.edu/BusinessAffairs/Travel_Risk_Activities.htm. Additional information is available
from the office of the school dean. Below is a description of any travel and/or risk-related activity
associated with this course.
The University of Texas System and The University of Texas at Dallas have rules and regulations
for the orderly and efficient conduct of their business. It is the responsibility of each student and
each student organization to be knowledgeable about the rules and regulations which govern
student conduct and activities. General information on student conduct and discipline is contained
in the UTD publication, A to Z Guide, which is provided to all registered students each academic
year.
The University of Texas at Dallas administers student discipline within the procedures of
recognized and established due process. Procedures are defined and described in the Rules and
Regulations, Board of Regents, The University of Texas System, Part 1, Chapter VI, Section 3, and
in Title V, Rules on Student Services and Activities of the university’s Handbook of Operating
Procedures. Copies of these rules and regulations are available to students in the Office of the
Dean of Students, where staff members are available to assist students in interpreting the rules and
regulations (SU 1.602, 972/883-6391).
A student at the university neither loses the rights nor escapes the responsibilities of citizenship.
He or she is expected to obey federal, state, and local laws as well as the Regents’ Rules,
university regulations, and administrative rules. Students are subject to discipline for violating the
standards of conduct whether such conduct takes place on or off campus, or whether civil or
criminal penalties are also imposed for such conduct.
Academic Integrity
The faculty expects from its students a high level of responsibility and academic honesty. Because
the value of an academic degree depends upon the absolute integrity of the work done by the
student for that degree, it is imperative that a student demonstrate a high standard of individual
honor in his or her scholastic work.
Scholastic dishonesty includes, but is not limited to, statements, acts or omissions related to
applications for enrollment or the award of a degree, and/or the submission as one’s own work or
material that is not one’s own. As a general rule, scholastic dishonesty involves one of the
following acts: cheating, plagiarism, collusion and/or falsifying academic records. Students
suspected of academic dishonesty are subject to disciplinary proceedings.
Plagiarism, especially from the web, from portions of papers for other classes, and from any other
source is unacceptable and will be dealt with under the university’s policy on plagiarism (see
general catalog for details). This course will use the resources of turnitin.com, which searches the
web for possible plagiarism and is over 90% effective.
Email Use
The University of Texas at Dallas recognizes the value and efficiency of communication between
faculty/staff and students through electronic mail. At the same time, email raises some issues
concerning security and the identity of each individual in an email exchange. The university
encourages all official student email correspondence be sent only to a student’s U.T. Dallas email
The administration of this institution has set deadlines for withdrawal of any college-level courses.
These dates and times are published in that semester's course catalog. Administration procedures
must be followed. It is the student's responsibility to handle withdrawal requirements from any
class. In other words, I cannot drop or withdraw any student. You must do the proper paperwork to
ensure that you will not receive a final grade of "F" in a course if you choose not to attend the
class once you are enrolled.
Procedures for student grievances are found in Title V, Rules on Student Services and Activities, of
the university’s Handbook of Operating Procedures.
In attempting to resolve any student grievance regarding grades, evaluations, or other fulfillments
of academic responsibility, it is the obligation of the student first to make a serious effort to
resolve the matter with the instructor, supervisor, administrator, or committee with whom the
grievance originates (hereafter called “the respondent”). Individual faculty members retain
primary responsibility for assigning grades and evaluations. If the matter cannot be resolved at
that level, the grievance must be submitted in writing to the respondent with a copy of the
respondent’s School Dean. If the matter is not resolved by the written response provided by the
respondent, the student may submit a written appeal to the School Dean. If the grievance is not
resolved by the School Dean’s decision, the student may make a written appeal to the Dean of
Graduate or Undergraduate Education, and the deal will appoint and convene an Academic
Appeals Panel. The decision of the Academic Appeals Panel is final. The results of the academic
appeals process will be distributed to all involved parties.
Copies of these rules and regulations are available to students in the Office of the Dean of
Students, where staff members are available to assist students in interpreting the rules and
regulations.
As per university policy, incomplete grades will be granted only for work unavoidably missed at
the semester’s end and only if 70% of the course work has been completed. An incomplete grade
must be resolved within eight (8) weeks from the first day of the subsequent long semester. If the
required work to complete the course and to remove the incomplete grade is not submitted by the
specified deadline, the incomplete grade is changed automatically to a grade of F.
Student AccessAbility
The goal of Student AcessAbility is to provide students with documented disabilities educational
opportunities equal to those of their peers. Student AccessAbility is located in room 3.200 in the
Student Services Building. Office hours are Monday through Thursday, 8:00 a.m. to 6:00 p.m. and
Friday, 8:00 a.m. to 5:00 p.m.
The college or university may need to provide special services such as registration, note-taking, or
mobility assistance.
It is the student’s responsibility to notify his or her professors of the need for such an
accommodation. Student AccessAbility provides students with letters to present to faculty
members to verify that the student has a disability and needs accommodations. Individuals
requiring special accommodation should contact the professor after class or during office hours.