Java object-oriented GUI programming features, computer science homework help

  

605.201 Mini-Project 3:
Please do the following to complete this assignment.
Purpose:
The purpose of this project is to provide non-trivial practice in the use of Java object-oriented GUI
programming features to implement an object-oriented GUI design and have a bit of fun doing it.
Resources Needed:
You will need a computer system with Java 7 or greater SE edition run-time and Java Development Kit
(JDK). You may optionally use a Java IDE for example NetBeans, Eclipse, etc. However application
builders are not allowed.
Submitted Files:
Design and Analysis:
This is an informal essay-style single-spaced word-processed document. The file formats accepted are
.odt, .doc, and .docx. The length of the document should be between 1 and 1.5 pages. The following
subjects should be discussed in this order:
1. General program design. How is the program organized? What major data structures were
used? How did you divide the functionality among your classes? How are commands
processed? Etc.
2. What alternative approaches were considered and why were they rejected?
3. What did you learn from doing this project and what would you do differently?
Source files:
Each public class must be contained in a separate Java source file. Only one source file will have a
main() method and this source will be named SongDatabase.java. Other source/class names are up to
you following the guidelines specified so far in the course.
The format of the Java source must meet the general Java coding style guidelines discussed so far
during the course. Pay special attention to naming guidelines, use of appropriate variable names and
types, variable scope (public, private, protected, etc.), indentation, and comments. Classes and
methods should be commented with JavaDoc-style comments (see below). Please use course office
hours or contact the instructor directly if there are any coding style questions.
JavaDocs:
Sources should be commented using JavaDoc-style comments for classes and methods. Each class
should have a short comment on what it represents and use the @author annotation. Methods should
have a short (usually 1 short sentence) description of what the results are of calling it. Parameters and
returns should be documented with the @param and @return annotations respectively with a short
comment on each.
JavaDocs must be generated against every project Java source file. They should be generated with a
-private option (to document all protection-level classes) and a –d [dir] option to place the resulting
files in a javadocs directory/folder at the same level as your source files. See the JavaDocs
demonstration for more details.
Submit file:
The submit file is to be a Zip file containing your design and analysis document, your Java sources, and
your javadocs directory/folder. Any appropriate file name for this Zip file is acceptable.
If you know how to create a standard Java JAR file, this is also acceptable for your source code.
However, make sure you include the source code in your JAR file.
Collaboration:
It is encouraged to discuss technical or small design parts of this project with your fellow students.
However the resulting design and implementation must be your own. For example, it is acceptable to
discuss different ways of maintaining the system state but not detailed design or implementation
information on processing the purchase command. When in doubt, ask during office hours or contact
your instructor.
Program Specification:
This project involves implementing a Java program that builds and manages a database of songs using
a GUI-based user interface.
The application will consist of a single frame that allows a user to add, edit, or delete songs from the
database. Here’s a rough prototype for what the frame might look like. Yours doesn’t have to look
exactly like this…the prototype is provided just to help you envision the ultimate application.
The application shall work as follows:
1. Upon start-up, the application will read the database file. The path of the database file will be
supplied by a run-time parameter. If the database file does not exist, the user will be told the
database does not exist and prompted (non-GUI text prompt) asking if they want to create a new
one. If the user answers positive, the application will continue with an initially empty song
database. If the user answers negatively, the application will exit. An example of an appropriate
start-up command is as follows:
java SongDB mySongDB.data
2. The original state of the frame shall display the combo box with the first song in the database
selected. The Item Code, Description, Artist, Album, and Price fields for this item shall be
displayed with the fields disabled (non-editable). The Add, Edit, Delete, and Exit buttons shall be
enabled, and the Accept and Cancel buttons shall be disabled.
3. To add a song, the user clicks on the Add button. This will cause the application to clear and enable
the Item Code, Description, Artist, Album, and Price fields so the user can enter information for the
new song. The Edit and Delete buttons are also disabled, and the Accept and Cancel buttons are
enabled. When the user presses the Accept button, the new song will be added to the database and
combo box. If the user presses the Cancel button, the entry transaction is canceled and the frame
reverts to its original state.
4. To edit an existing song, the user shall select the song from the combo box. The information for the
selected song shall then be displayed in the disabled fields. The user then presses the Edit button,
which enables the Description, Artist, and Price fields. The user may not change the Item Code.
Select Song: Yellow Submarine
Item Code: BT012
Description: Yellow Submarine
Artist: The Beatles
Album: Beatles Greatest Hits 1
Price: 1.99
Add Edit Delete Accept Cancel
Exit
The Add, Edit, and Delete buttons are disabled, and the Accept and Cancel buttons are enabled. If
the user presses the Accept button, the changes are saved and the combo box is updated. If the user
presses the Cancel button, the edit transaction is canceled and the frame reverts to its original state.
5. To delete an existing song, the user shall select the song from the combo box. The information for
the song shall then be displayed in the disabled fields. If the user presses the Delete button, the song
is deleted from the database and the combo box.
6. When the user presses the Exit button the application shall terminate. The current state of the
database shall be saved in a file using the pathname supplied at program start-up (see above).
7. Data fields shall be validated to ensure they are not blank with appropriate error messages
displayed. If the song is a single, the text “None” will be used for the album name. The price field
shall be validated to ensure only numeric data is entered.
Other Activates:
1. Create a compressed zipped folder containing your Design and Analysis document, your Java
source code files, and your javadocs folder.
2. Submit your compressed zipped folder as directed by your instructor.
Assignment Rubric:
Part 70% 80% 90% 100% % of
Grade
Design and
Analysis
Document
All but one subject
addressed with
relevant,
information. Few
minor
typographical
issues. Document
is close to assigned
length
All assigned
subjects address
with mostly
relevant
information.
Nicely formatted
document.
Document is
close to assigned
length
All assigned subjects
address with
accurate and
relevant. Nicely
formatted document.
Document is within
assigned length
All assigned
subjects address
with accurate,
relevant, and
insightful
information.
Very nicely
formatted.
Document is
within assigned
length
15%
Functionality Majority of
required function
parts work as
indicted in the
assignment text.
One major or 3
minor defects. All
major functionality
at least partially
working (example
change provided
but not correct).
Most required
function parts
work as indicted
in the
assignment text
above and
submitted
documentation.
One major or 3
minor defects.
All major
functionality at
Nearly all required
function parts work
as indicted in the
assignment text
above and submitted
documentation. One
to two minor
defects.
All required
function parts
work as indicted
in the assignment
text above and
submitted
documentation.
50%
Design document
does not fully
reflect
functionality.
least partially
working
((example
change provided
but not correct).
Code Majority of the
code conforms to
coding standards as
explained and
demonstrated so far
in the course (ex.
method design,
naming,
formatting, etc.).
Five to six minor
coding standard
violations. Some
useful comments.
Some JavaDocs
commenting.
Code compiles
with multiple
warnings or fails to
compile with
difficult to
diagnose error.
Most of the code
conforms to
coding standards
as explained and
demonstrated so
far in the course
(ex. method
design, naming,
formatting, etc.).
Three to four
minor coding
standard
violations.
Mostly useful
comments.
Public class
JavaDocs
complete. Code
compiles with
one to two
warnings.
Almost all code
conforms to coding
standards as
explained and
demonstrated so far
in the course (ex.
method design,
naming, formatting,
etc.). One to two
minor coding
standard violations.
Appropriate level of
useful comments.
Public class
JavaDocs complete.
Code compiles.
Code compiles with
no errors or
warnings.
All code
conforms to
coding standards
as explained and
demonstrated so
far in the course
(ex. method
design, naming,
formatting, etc.).
Appropriate level
of useful
comments.
Complete
JavaDocs as
specified. Code
compiles with no
errors or
warnings.
25%
Submit
package
More than one file
submitted in
incorrect format.
Files not enclosed
in the specified
compressed file.
All but one file
submitted in
correct format.
Files not
enclosed in the
specified
compressed file.
All file submitted in
correct format but
not in the specified
compressed file.
All file submitted
in correct file
formats and
compressed as
specified.
10%
mini_project_3.pdf

Unformatted Attachment Preview

Don't use plagiarized sources. Get Your Custom Essay on
Java object-oriented GUI programming features, computer science homework help
Just from $10/Page
Order Essay

605.201 Mini-Project 3:
Please do the following to complete this assignment.
Purpose:
The purpose of this project is to provide non-trivial practice in the use of Java object-oriented GUI
programming features to implement an object-oriented GUI design and have a bit of fun doing it.
Resources Needed:
You will need a computer system with Java 7 or greater SE edition run-time and Java Development Kit
(JDK). You may optionally use a Java IDE for example NetBeans, Eclipse, etc. However application
builders are not allowed.
Submitted Files:
Design and Analysis:
This is an informal essay-style single-spaced word-processed document. The file formats accepted are
.odt, .doc, and .docx. The length of the document should be between 1 and 1.5 pages. The following
subjects should be discussed in this order:
1. General program design. How is the program organized? What major data structures were
used? How did you divide the functionality among your classes? How are commands
processed? Etc.
2. What alternative approaches were considered and why were they rejected?
3. What did you learn from doing this project and what would you do differently?
Source files:
Each public class must be contained in a separate Java source file. Only one source file will have a
main() method and this source will be named SongDatabase.java. Other source/class names are up to
you following the guidelines specified so far in the course.
The format of the Java source must meet the general Java coding style guidelines discussed so far
during the course. Pay special attention to naming guidelines, use of appropriate variable names and
types, variable scope (public, private, protected, etc.), indentation, and comments. Classes and
methods should be commented with JavaDoc-style comments (see below). Please use course office
hours or contact the instructor directly if there are any coding style questions.
JavaDocs:
Sources should be commented using JavaDoc-style comments for classes and methods. Each class
should have a short comment on what it represents and use the @author annotation. Methods should
have a short (usually 1 short sentence) description of what the results are of calling it. Parameters and
returns should be documented with the @param and @return annotations respectively with a short
comment on each.
JavaDocs must be generated against every project Java source file. They should be generated with a
-private option (to document all protection-level classes) and a –d [dir] option to place the resulting
files in a javadocs directory/folder at the same level as your source files. See the JavaDocs
demonstration for more details.
Submit file:
The submit file is to be a Zip file containing your design and analysis document, your Java sources, and
your javadocs directory/folder. Any appropriate file name for this Zip file is acceptable.
If you know how to create a standard Java JAR file, this is also acceptable for your source code.
However, make sure you include the source code in your JAR file.
Collaboration:
It is encouraged to discuss technical or small design parts of this project with your fellow students.
However the resulting design and implementation must be your own. For example, it is acceptable to
discuss different ways of maintaining the system state but not detailed design or implementation
information on processing the purchase command. When in doubt, ask during office hours or contact
your instructor.
Program Specification:
This project involves implementing a Java program that builds and manages a database of songs using
a GUI-based user interface.
The application will consist of a single frame that allows a user to add, edit, or delete songs from the
database. Here’s a rough prototype for what the frame might look like. Yours doesn’t have to look
exactly like this…the prototype is provided just to help you envision the ultimate application.
Select Song:
Yellow Submarine
Item Code:
BT012
Description:
Yellow Submarine
Artist:
Album:
Price:
Add
The Beatles
Beatles Greatest Hits 1
1.99
Edit
Delete
Accept
Cancel
Exit
The application shall work as follows:
1. Upon start-up, the application will read the database file. The path of the database file will be
supplied by a run-time parameter. If the database file does not exist, the user will be told the
database does not exist and prompted (non-GUI text prompt) asking if they want to create a new
one. If the user answers positive, the application will continue with an initially empty song
database. If the user answers negatively, the application will exit. An example of an appropriate
start-up command is as follows:
java SongDB mySongDB.data
2. The original state of the frame shall display the combo box with the first song in the database
selected. The Item Code, Description, Artist, Album, and Price fields for this item shall be
displayed with the fields disabled (non-editable). The Add, Edit, Delete, and Exit buttons shall be
enabled, and the Accept and Cancel buttons shall be disabled.
3. To add a song, the user clicks on the Add button. This will cause the application to clear and enable
the Item Code, Description, Artist, Album, and Price fields so the user can enter information for the
new song. The Edit and Delete buttons are also disabled, and the Accept and Cancel buttons are
enabled. When the user presses the Accept button, the new song will be added to the database and
combo box. If the user presses the Cancel button, the entry transaction is canceled and the frame
reverts to its original state.
4. To edit an existing song, the user shall select the song from the combo box. The information for the
selected song shall then be displayed in the disabled fields. The user then presses the Edit button,
which enables the Description, Artist, and Price fields. The user may not change the Item Code.
The Add, Edit, and Delete buttons are disabled, and the Accept and Cancel buttons are enabled. If
the user presses the Accept button, the changes are saved and the combo box is updated. If the user
presses the Cancel button, the edit transaction is canceled and the frame reverts to its original state.
5. To delete an existing song, the user shall select the song from the combo box. The information for
the song shall then be displayed in the disabled fields. If the user presses the Delete button, the song
is deleted from the database and the combo box.
6. When the user presses the Exit button the application shall terminate. The current state of the
database shall be saved in a file using the pathname supplied at program start-up (see above).
7. Data fields shall be validated to ensure they are not blank with appropriate error messages
displayed. If the song is a single, the text “None” will be used for the album name. The price field
shall be validated to ensure only numeric data is entered.
Other Activates:
1. Create a compressed zipped folder containing your Design and Analysis document, your Java
source code files, and your javadocs folder.
2. Submit your compressed zipped folder as directed by your instructor.
Assignment Rubric:
Part
70%
80%
90%
100%
Design and
Analysis
Document
All but one subject
addressed with
relevant,
information. Few
minor
typographical
issues. Document
is close to assigned
length
All assigned
subjects address
with mostly
relevant
information.
Nicely formatted
document.
Document is
close to assigned
length
All assigned subjects
address with
accurate and
relevant. Nicely
formatted document.
Document is within
assigned length
Functionality
Majority of
required function
parts work as
indicted in the
assignment text.
One major or 3
minor defects. All
major functionality
at least partially
working (example
change provided
but not correct).
Most required
function parts
work as indicted
in the
assignment text
above and
submitted
documentation.
One major or 3
minor defects.
All major
functionality at
Nearly all required
function parts work
as indicted in the
assignment text
above and submitted
documentation. One
to two minor
defects.
All assigned
subjects address
with accurate,
relevant, and
insightful
information.
Very nicely
formatted.
Document is
within assigned
length
All required
function parts
work as indicted
in the assignment
text above and
submitted
documentation.
% of
Grade
15%
50%
Design document
does not fully
reflect
functionality.
Code
Submit
package
least partially
working
((example
change provided
but not correct).
Majority of the
Most of the code
code conforms to
conforms to
coding standards as coding standards
explained and
as explained and
demonstrated so far demonstrated so
in the course (ex.
far in the course
method design,
(ex. method
naming,
design, naming,
formatting, etc.).
formatting, etc.).
Five to six minor
Three to four
coding standard
minor coding
violations. Some
standard
useful comments.
violations.
Some JavaDocs
Mostly useful
commenting.
comments.
Code compiles
Public class
with multiple
JavaDocs
warnings or fails to complete. Code
compile with
compiles with
difficult to
one to two
diagnose error.
warnings.
More than one file All but one file
submitted in
submitted in
incorrect format.
correct format.
Files not enclosed
Files not
in the specified
enclosed in the
compressed file.
specified
compressed file.
Almost all code
conforms to coding
standards as
explained and
demonstrated so far
in the course (ex.
method design,
naming, formatting,
etc.). One to two
minor coding
standard violations.
Appropriate level of
useful comments.
Public class
JavaDocs complete.
Code compiles.
Code compiles with
no errors or
warnings.
All code
conforms to
coding standards
as explained and
demonstrated so
far in the course
(ex. method
design, naming,
formatting, etc.).
Appropriate level
of useful
comments.
Complete
JavaDocs as
specified. Code
compiles with no
errors or
warnings.
25%
All file submitted in
correct format but
not in the specified
compressed file.
All file submitted
in correct file
formats and
compressed as
specified.
10%

Purchase answer to see full
attachment

Place your order
(550 words)

Approximate price: $22

Calculate the price of your order

550 words
We'll send you the first draft for approval by September 11, 2018 at 10:52 AM
Total price:
$26
The price is based on these factors:
Academic level
Number of pages
Urgency
Basic features
  • Free title page and bibliography
  • Unlimited revisions
  • Plagiarism-free guarantee
  • Money-back guarantee
  • 24/7 support
On-demand options
  • Writer’s samples
  • Part-by-part delivery
  • Overnight delivery
  • Copies of used sources
  • Expert Proofreading
Paper format
  • 275 words per page
  • 12 pt Arial/Times New Roman
  • Double line spacing
  • Any citation style (APA, MLA, Chicago/Turabian, Harvard)

Our guarantees

Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.

Money-back guarantee

You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.

Read more

Zero-plagiarism guarantee

Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.

Read more

Free-revision policy

Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.

Read more

Privacy policy

Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.

Read more

Fair-cooperation guarantee

By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.

Read more

Order your essay today and save 30% with the discount code ESSAYSHELP