Java

Need Help in Java Assignment?
We can help you if you are having difficulty with your Java Assignment. Just email your Java Assignment at admin@assignmentcache.com.
We provide help for students all over the world in Java Assignment.

Items 1 to 10 of 12 total

per page
Page:
  1. 1
  2. 2

Grid  List 

Set Ascending Direction
  1. Employee Online Time Clock Project

    Employee Online Time Clock Project

    Regular Price: $25.00

    Special Price: $20.00

    Employee Online Time Clock Project


    Overview
    The final project for this course is the creation of an Online Time Clock. The final project is designed to allow you to put together the concepts learned in the course and to demonstrate your ability to write a useful Java program. The final project is given early in the course so that you will have plenty of time to design the program before it is due.
    Early in the course, you will not have the knowledge to implement many of the required elements, but you will still be able to move your project forward by designing it at the conceptual level. Diagramming and pseudo coding before coding a project allows you to think through what needs to be done in detail, thus allowing you to see design flaws before they have been coded. The extra effort to design the program before coding will make the coding process much easier and will result in fewer bugs. The project specifications include a list of requirements that demonstrate different areas of Java development that must be included in your final project to demonstrate your skill in that area. The project shall demonstrate the following skills:
    • Use of a static member
    • Use of extended class
    • Code Commenting
    • GUI or Console based interface
    • Use of public and private methods
    • Use at least one overloaded constructor
    • Create instances of class(es)
    • Use the 'this' reference
    • Optional: Exception handling using try/throw/catch/finally


    The project is divided in to Six Milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final submissions. These milestones will be submitted in Modules Four, Six, Seven, Eight, Nine, and Ten.


    Main Elements


    Approach Blueprint
    Coding a project of this size requires some planning and time. Work on building a blueprint for the program throughout the term. Having a blueprint will make the coding simpler and keep you from going down dead ends. Some important things to work on early:
    • If the application is using more than one screen (console applications have no choice.), what is the flow between screens? A flow chart that covers all of the possible screen access possibilities will avoid logic problems in the application.
    • Break the program down into a set of classes that will work together to execute the program. Object oriented programs are easier to write than structured programs because each class has one set of functionality that it does well and working on one piece at a time makes the programming easier. List out the properties and methods that each class will use so that the relationship between the classes can be established. (Software Engineers create formal class diagrams that show the class hierarchy of a program and how they interrelate. A formal class diagram is not required for this project, but sketching a rough diagram will make things easier.)
    • Optional: Error handling can have unexpected results if not done correctly. Diagram how your exception handling will work by sketching a flow chart.
    • Validation can be as tricky as error handling, so sketching a diagram is also useful.
    • Devise a strategy for handling data. The data may be held in objects in memory, or, optionally, in text files. If you decide to use memory objects, then there should be separate objects for Employee information and their time clock records. The employee memory object (or employee.txt flat file) will be relatively simple since there are no deletes or modifications to an input value. Employees will be employee ID order. The time clock memory object (or timeclock.txt file) is a different story because the records will not be in employee ID order; they will be in the order that an employee punched in or out. When generating a report it will be necessary to find all of the data for each employee and output it in chronological order. The chronological order is already in the memory object (or file) because we are not deleting or modifying any data. The program will only need to group all of the data for an employee together. This can be done in several ways (You may choose which is best, or come up with another solution):
    o When an employee punches in or out the program can search the data file and insert the value after the last entry for that employee.
    o The system can sort the values in the file in memory as part of the reporting functionality, leaving the data in the file in its original order.


    Caution is in order because the records should have the punch in time and punch out time for a single day in order. (They will be in that order in the file, because someone has to punch in before they punch out. The program specifications require checking for a 'punched in' record before saving a 'punched out' record.)
    NOTE: The separate screen descriptions are for console applications. The GUI application may use one or more screens, as appropriate, but the functionality shall remain the same).
    NOTE: Functionality labeled as Optional does not have to be implemented. It is for students who would like to write a more challenging program.
    NOTE: Those developing a GUI application will replace the 'input values' with appropriate GUI objects such as buttons. For example, instead of inputting 'A' for Add New Employee, create a button for adding a new employee.


    Scenario
    A company hires you to write a program to track hourly employee arrival and departure times from work. In essence, you are tasked to make an online time clock. The time clock shall keep a history of an employee’s hours for a two-week pay period. The application shall have the following functionality:


    Main Screen
    The main screen shall act as a menu to access program functionality and to exit the program.
    The main screen shall:
    • Display 4 options
    A) Add New Employee – Displays new employee screen
    B) Punch In/Out – Displays punch in/out screen
    C) Report – Displays report screen
    D) Exit – Exits the program
    • Display an input field called "Choice" to input one of the four options.
    • Inputting an incorrect option shall display a prompt indicating that the input was invalid and to try again.
    • Optional functionality: If the user enters an incorrect value more than 3 times, display a prompt that the program is exiting and close the program.


    Add New Employee Screen
    The 'add new employee screen' shall:
    • Add a new employee (we will not worry about modifying or deleting.), saving the data to a memory object or file.
    o The program shall allow the user to enter the Employee’s First and Last Name
    o The program shall validate the first and last name entered to ensure they are not blank. (We will assume that everyone has a first and last name.)
    o The program shall assign a new employee ID to the employee and display it on the screen.
    o The employee ID shall be generated by adding 1 to the largest employee ID already in the employee memory object (or employee.txt data file).
    o The program shall allow the user to enter an unlimited number of employees. In console based applications, the system shall prompt “Do you want to enter another? (y/n). Entering 'y' shall clear the screen and prompt for another employee. If 'n', the program shall return to the main screen.
    o The employee data shall be saved to a memory object called employee (or file called employee.txt)
    o Optional functionality: Check the first and last name to ensure that there are only valid characters. For examples, filter out numbers, punctuation, etc. Commas can cause problems because the data is being saved to comma-delimited files and that can be a headache!


    Punch in/out Screen
    The 'punch in/out screen' shall:
    • Save the punch in or punch out date and time of the employee to a memory object (or file).
    o The date and time, 'I' for Punched In or 'O' for punched out along with the Employee ID shall be saved to a memory object called timeclock (or file called timeclock.txt).
    o The recorded date for 'punched in' and 'punched out' shall be the method for matching corresponding records.
    o The program shall test to ensure that there is a 'Punched in' record for the corresponding day before a 'punched out' record is saved. If none is found, prompt the user to enter a 'punched in' time.
    o Then the user has punched in or out, the program shall display a message indicating that the employee has punched in or out, the employee ID, date and time.
    o In console based applications the screen shall display "Press any key to continue"
    o In console based applications the program shall return to the main menu after a key is pressed when the “Press any key to continue” prompt is displayed.
    o Optional functionality: Add the day of the week to the data saved.


    Report Screen (Hint: If you are writing a console application, java.io.PrintWriter may be useful.)
    The 'report screen' shall:
    • Allow the user to display a work history report for an individual or for all employees for the two weeks prior to the report request.
    o The screen shall display a prompt to enter 'I' for individual employee report, 'A' for all employees report.
    o If the selected value is 'I', prompt the user to enter the employee's ID number.
     If 'I' is selected the display shall show the employee's name and ID, list out each day worked in chronological order, the number of hours worked that day and a total number of hours worked in the two week period.
     The report shall prompt the user to re-enter an employee ID of it does not exist in the employee file.
     Optional Functionality: If the user inputs a nonexistent employee ID more than 3 times, prompt the user and then return to the main screen.
    o If the selected value is 'A', output the information to the console for the past two weeks.
    o The end of the report shall display "Press any key to continue" to return to the main menu.
    o Optional Functionality: Allow the user to print the report to a printer.


    Example Screen Shots
    The following screen shots are suggestions for setting up your application. You are not required to make your screens look like these, they are only provided to help you think about the program’s interface. Items that are inside a red box are some example prompts that may not be displayed unless a particular action takes place. You may have more or different prompts depending on how you decide to create your program.
    Console Based Application


    GUI Base Application Using One Screen (You are free to use multiple screens, if desired.)

    Learn More
  2. CIS355A Week 5 iLab 5 Step 1 Write Clients to File

    CIS355A Week 5 iLab GUI Graphics and File I/O

    Regular Price: $25.00

    Special Price: $20.00

    CIS355A Week 5 iLab GUI Graphics and File I/O


    Scenario/Summary
    In this lab, you will create one project that reads from a file, one project that writes to a file, and one project drawing a snowman.


    iLAB STEPS
    STEP 1: Writing out Client Information
    1) Create the following GUI, so that when your program is running, your user can input information regarding a client and hit the save button to save the information out to a file.
    2) Every time the user hits the save button, that information should be saved out to a file called client.txt; each new client's information should append to the information already saved onto the file client.txt.
    3) The data in the client.txt file should be formatted like the following.
    Client Activity Report
    Client Name Client ID Starting Balance Closing Balance
    XXXXXXXXX 9999999 99999.99 99999.99
    XXXXXXXXX 9999999 99999.99 99999.99
    XXXXXXXXX 9999999 99999.99 99999.99

    STEP 2: Reading in Client Information
    1) Create a class called Client, the Client class must contain attributes for Client name, Client ID, starting balance, and closing balance, and all other accessor/mutator/constructor functions as necessary.
    2) Assume you have a client.txt file with the following sample information.
    Charles Smith|100235|5700.75|1200.00
    James Peterson|320056|349.56|4005.56
    Francis Lewis|400556|7500.00|456.23
    William Burgess|45399|5000.00|1245.56
    Philip Wilson|10090|10000.00|2300.75
    James Brown|34291|25000.45|31454.86
    3) Create a Client ArrayList to process input records in main().
    4) Use a for loop to read in the information from client.txt.
    5) The GUI to this program should look similar to this:
    6) Once the user hits the display button, everything read in from the file should display in the Console window in this format.
    Client Activity Report
    Client Name Client ID Starting Balance Closing Balance
    XXXXXXXXX 9999999 99999.99 99999.99
    XXXXXXXXX 9999999 99999.99 99999.99
    XXXXXXXXX 9999999 99999.99 99999.99


    STEP 3: Snowman!
    Use the many draw methods provided to you by Java and draw a Snowman—be as creative or as basic as you would like, as long as the final result resembles a snowman. It doesn't have to necessarily look exactly like this, but this is the minimum you should achieve with your drawing.
    1) You must have at least three circles in your project.
    2) You must have at least a line, a polygon, an oval, or a rectangle.
    3) In addition to your snowman, you should also use drawString to draw some text.
    4) Use draw or fill and the color class as you see fit.
    Hint: frame.getContentPane().setBackground(Color.blue); //This is the code you need to set the frame's background color. Have Fun!

    Learn More
  3. Travel Agents System Java Program

    Travel Agents System Java Program

    Regular Price: $30.00

    Special Price: $25.00

    Travel Agents System Java Program


    You are to develop program in Java for a small travel agents. The company arranges holidays from four UK airports to five international destinations. Users need to find flight times and costs for journeys between these destinations. The system also provides information on hotels at the destinations (name of hotel and cost per person per night). Information on hotels can only be added, or loaded from file, when the program is running. The following table (Table 1) provides the airport names, destinations, costs and flight times for the journeys Table 1 Information for the travel agents program – the two values represent cost (£) and flight time (hours) respectively – you can make up your own (realistic values) if you wish


    Airport/Destination | New York |Dahab | Rome |Sydney |Tokyo
    East Midlands |200/5.0 |150/4.0 |100/1.0 |500/22.0 |400/12.0
    Birmingham |190/4.8 |140/3.5 |95/1.1 |480/22.5 |380/12.5
    Heathrow |195/4.9 |140/3.6 |95/1.1 |490/23.0 |390/12.5
    Manchester |210/5.5 |145/3.7 |110/1.2 |470/22.7 |370/12.6


    (the above is a data table, where there is a line, represents the cell)


    Your program should have a main menu with four options – Time, Price, Hotels and End (which terminates the program). The Hotels option takes the user to another (Hotel) menu with the following six options – View Hotels; Add Hotel; Delete Hotel; Save Hotels; Retrieve Hotels; Exit (back to the previous menu). Note that your program should include appropriate error trapping – for example, entering an invalid date (eg 30 February).
    Functionality for each of these menu options is explained below:
    Time – Provides the flight time presented in hours.
    Price – The cost of travelling from an airport to a given destination (both selected by the user). Note, if the customer is travelling on the last day of the month the fare should be increased by 5% (and display a message to say that this has been done). The system will therefore need to ask the user the date of travel. It should not simply ask the user if it is the end of the month – but work this out from a date provided by the user.
    Hotels – Takes the user to a Hotels Information Menu.
    Hotels menu
    View Hotels – The user selects a destination and the system displays all available hotels at that destination including the overnight cost per person. If there are no hotels for a destination it should display a message to say so.
    Add Hotel – Allows the user to add a hotel for a given destination. This should add to the list of existing hotels for that destination (if there are any). For example, I might add 'Belle Vue' as a hotel in Sydney at a cost of £50 per person per night.
    Delete Hotel – Allows the user to delete a hotel from a list of hotels at a destination.
    Save Hotels – save all the information on all hotels to a single file in a format of your choosing.
    Retrieve Hotels – read in all the information on hotels from a user selected file (a file saved using the previous option). This should overwrite any existing hotel data in the program when it is running.


    Marking
    The more functionality you add to the program the higher your mark. Begin by getting the menu options in place then add functionality to your program in the following order (make sure that earlier parts of the system are working properly before moving on). Your program should also be structured in an object oriented way. You should try to identify and implement a number of classes for this program.


    Minimum pass (40%)
    The flight time between any airport and destination;
    The cost of travel between any airport and destination;
    Increased cost of travel on the last day of the month and a message to say this has been applied;


    40%-70%
    View hotels – users can view information on all hotels at a chosen destination; Add hotel – the ability for users to add hotels for a destination;
    Sort hotels – users can sort all hotels alphabetically;


    Documentation
    Your coursework should be submitted with appropriate documentation. You should include class diagrams, designs, functionality not completed, functionality working, test plans, evaluation, and program listings. Make sure you include an explanation of how your code should be run (eg. which file should be compiled and run and anything I need to know about using the program – a user guide).

    Learn More
  4. CIS355A Week 3 iLab InheritanceTest Java Program

    CIS355A Week 3 iLab InheritanceTest and Greeting Java Program

    Regular Price: $25.00

    Special Price: $20.00

    CIS355A Week 3 iLab InheritanceTest and Greeting Java Program


    Scenario/Summary
    In this lab, you will create one project that uses inheritance and one simple Applet.


    Deliverables
    Program files for each of the following programs
    1. InheritanceTest; and
    2. Greeting.


    iLAB STEPS
    Step 1: InheritanceTest
    Implement an inheritance hierarchy based on the following specifications for Account class, Checking Account class, and Savings Account class:
    Account class
    • Methods:
    o processDeposit ( ) - accepts a single double parameter containing the deposit amount. Updates the balance by adding the deposit amount to the balance.
    o processWithdrawal ( ) - accepts a single double parameter containing the withdrawal amount. Updates the balance by subtracting the withdrawal amount for the balance. Note: For now do not worry about negative balances.
    o calcInterest ( ) - Coded as a double method with an empty body.
    • Attributes:
    o String Account Name
    o Integer Account ID
    o Double balance
    • Constructor
    o Prompt the user and accept input for the Account Name, Account ID and the initial balance.
    The CheckingAcct class which is a derived class of the Account class.
    • Attributes:
    o Inherits all the attributes of the Account class.
    o The overDraftFee is double and is populated in the constructor of the CheckingAcct class.
    • Methods:
    o calcInterest () - If the account balance is greater than or equal to 3000.00 an interest rate of 1% or .01 is applied to increase the balance.
    • Constructor:
    o Prompt the user for the OverDraftFee.
    The SavingsAcct class which is a derived class of the Account class.
    • Attributes:
    o Inherits all the attributes of the Account class.
    o There are no other attributes.
    • Methods:
    o calcInterest ( ) - If the account balance is greater than or equal to 5000.00 an interest rate of 4% or .04 is applied to increase the balance. If the balance is greater than or equal to 3000.00 an interest rate of 3% or .03 is applied to increase the balance. Otherwise use an interest rate of 2%. The new balance is returned to the calling program.
    • Constructor:
    o Inherited from the Account class. (no code needed)
    Main:
    Prompt the user for the bank name and routing number. Create at least two account objects (each of a different type). Process a deposit then withdraw then calculate the interest for each account. Generate the following report:
    Bank Name: XXXXXXXX Routing Number: XXXXXX
    Account Name: XXXXXX Account ID: XXXXXXXXX Balance: 9999.99
    Account Name: XXXXXX Account ID: XXXXXXXXX Balance: 9999.99


    Step 2: Greeting
    Create an applet of size 500 by 500. The background color of the applet should be yellow. The four components to be included are
    1. a Label object that has the text "Please enter your name;"
    2. a Textfield object of size 20;
    3. a Button object with the text "GREET;" and
    4. a Label object with the text "Result goes here." This label will change to "Hello," followed by the entered name.
    For this lab, you will need the actionPerformed method to provide event handling for the button.
    The getText() method will be needed to get the string from the TextField.
    The setText() method will be needed to change the text of the second Label.
    Test your applet by entering your full name and confirming that the result label has changed.

    Learn More
  5. CIS355A Week 6 iLab 6 Java Pizza Swing

    CIS355A Week 6 iLab Swing and Database Connection

    Regular Price: $25.00

    Special Price: $20.00

    CIS355A Week 6 iLab Swing and Database Connection

    iLAB OVERVIEW
    Scenario/Summary
    Develop one application using JTabbedPanes and JFrames and another application that connects to a MySQL database.
    Deliverables
    1. JavaPizza
    2. ContactList

    iLAB STEPS
    Step 1: JavaPizza
    Develop an application using a JTabbedPane to order a pizza. You will need to ask the customer for their name and phone number. You will ask for the size (choose one) and toppings (choose many) and compute the total. After computing the total, provide a button to display the order summary, which includes the name, phone number, size, toppings, and total. The prices are listed below. Screenshots of a possible solution are included. Your application must include four tabs and open a new window when the button is clicked.
    • Small:  8.00
    • Medium: 10.00
    • Large: 12.00
    Each topping is 2.00 extra.
     
    JavaPizza    Points    Description
    Standard header included    1    Must contain program's name, student name, and description of the program
    Program compiles    1    Program does not have any error
    Program executes    1    Program runs without any error
    Created the JTabbedPane with four tabs    4    The JTabbedPane is displayed with the four required tabs and components on each tab
    Total is calculated correctly    5    The total on the last tab is calculated correctly based on information supplied.
    Order summary window displayed correctly    8    The order summary window is displayed with a JTextArea, including all information from the four tabs.
    Subtotal    20      
     
    Step 2: Contact List
    Develop a Java application to add a contact into the contact table, and display all contacts in the contact table. The contact table contains two columns, FullName, and PhoneNumber. Both values are text data. Use JOptionPanes to ask for the contact data, and display a confirmation message when the contact is added. Display the list of contacts in the console. Screenshots of a possible solution are included.
     
    ContactList    Points    Description
    Standard header included    1    Must contain program's name, student name, and description of the program
    Program compiles    1    Program does not have any error
    Program executes    1    Program runs without any error
    Created the JOptionPanes for input    6    Two JOptionPanes are displayed to retrieve input
    JOptionPane displayed upon insert    4    A JOptionPane is display to confirm the contact was added
    ContactList shown in console    7    The list of contacts is displayed in the console under a heading contact list .
    Subtotal    20

    Learn More
  6. CMIS 242 Project 4 Color Menu

    CMIS 242 Project 4 Color Menu

    Regular Price: $25.00

    Special Price: $20.00

    CMIS 242 Project 4 Color Menu


    This project focuses on demonstrating your understanding of Java Collections. Before attempting this project, be sure you have completed all of the reading assignments listed in the syllabus to date, participated in the weekly conferences, and thoroughly understand the examples throughout the chapters.
    Write a Java application that effectively uses Collections to store custom color definitions (between 5 and 20, inclusive).
    The user should assign a unique name to each color, and a unique hexadecimal value (e.g., red is #FF0000).
    User input can be done in a GUI or on the command-line.
    Your program should enforce uniqueness. In other words, if the user enters a name for a color that already has that name, then the user should be reprompted. (Same behavior for the hexadecimal value.)
    Additionally, a GUI should be included that displays the color names and hexadecimal values.
    Each name/value pair should be selectable via a radio button or other mechanism.
    When a color is selected, an area of the GUI should change to that color (the area is up to you, as long as it's visible).

    Learn More
  7. Introduction To Java 9th Edition Chapter 22 Exercise 13 The 24-point game Success

    Introduction To Java 9th Edition Chapter 22 Exercise 13 The 24-point game

    Regular Price: $25.00

    Special Price: $20.00

    Introduction To Java 9th Edition Chapter 22 Exercise 13 The 24-point game


    (Game: the 24-point card game) The 24-point game is to pick any 4 cards from 52 cards, as shown in Figure 22.19. Note that the Jokers are excluded. Each card represents a number. An Ace, King, Queen, and Jack represent 1, 13, 12, and 11, respectively. You can click the Refresh button to get four cards. Enter an expression that uses the four numbers from the four selected cards. Each number must be used once and only once. You can use the operators (addition, subtraction, multiplication, and division) and parentheses in the expression. The expression must evaluate to 24. After entering the expression, click the Verify button to check whether the numbers in the expression are currently selected and whether the result of the expression is correct. Display the verification in a dialog box. Assume that images are stored in files named 1.png, 2.png, . . . , 52.png, in the order of spades, hearts, diamonds, and clubs. So, the first 13 images are for spades 1, 2, 3, . . . , and 13.

    Learn More
  8. CMIS 141 Project 3 Stringed Musical Instrument Java Class

    CMIS 141 Project 3 Stringed Musical Instrument Java Class and UML class diagram

    Regular Price: $25.00

    Special Price: $20.00

    CMIS 141 Project 3 Stringed Musical Instrument Java Class and UML class diagram


    This project focuses on demonstrating your understanding of classes and objects. Before attempting this project, be sure you have completed all of the reading assignments listed in the syllabus to date, participated in the weekly conferences, and thoroughly understand the examples throughout the chapters. The project requirements include:


    1. Design and implement a stringed musical instrument class using the following guidelines:
    a. Data fields for your instrument should include number of strings, an array of string names representing string names (e.g. E,A,D,G), and boolean fields to determine if the instrument is tuned, and if the instrument is currently playing. You are welcome to add additional data fields if you like.
    b. A constructor method that set the tuned and currently playing fields to false.
    c. Other methods 1) to tune the instrument, 2) to start the instrument playing, and 3) to stop the instrument from playing.
    d. Other methods as you see fit (Add at least one unique method).


    2. Create a UML class diagram using a diagram tool (e.g. PPT, Visio) of your choice. Prepare the diagrams and place them in a word document along with a brief description of each of your classes.


    3. Create Java classes for your instruments. Be sure that your code matches your design specifications and some minimal functionality is included. For example, if you called the violin.play() method, you should at least print that the violin is playing. Similar functionality should be supplied when you stop playing, tune or call any of your methods. For example:


    public void playviolin() {
    System.out.println("The violin is now playing.");
    }


    4. Write the output from your Instrument class methods to a text file that a user entered from the command line arguments (e.g. java Mynamep3tst myfilename.txt). This allows your program to accept filenames from the user via a command line argument.


    5. Finally, create a Java test class that simulates using your instrument class. In your test class be you should at a minimum: a) Construct 10 instances of your instrument, b) tune your instruments, c) Start playing your instrument, d) Call your unique method, and e) Stop playing your instruments. (Hint: Arrays and Loops will make your job easier and result in more efficient code!)


    6. Your programs should compile and run without errors.


    7. Be sure to test your program carefully. Provide a list of comprehensive test cases used to validate your application and include these test cases in your word document containing your UML diagrams and descriptions. Similar to Project 1, your test data can be shown in a table that includes input data, expected output, actual output and pass/fail results from the test.

    Learn More
  9. CIS355A Week 4 iLab Quick Fast Car Care Application

    CIS355A Week 4 iLab Quick Fast Car Care Application

    Regular Price: $25.00

    Special Price: $20.00

    CIS355A Week 4 iLab Quick Fast Car Care Application


    iLAB STEPS
    Step 1: Quick Fast Car Care Application
    Quick Fast Car Care is a small business that specializes in oil changes and car washes. Their strategic advantage is providing quick service. To provide quick service, this owner wants a new application that will calculate services provided to customers. The table below has the services and the cost of these services.


    Oil Change Cost
    Bronze $20
    Silver $25
    Gold $30

    Car Wash Cost
    Basic $5
    Better $10
    Best $15


    Your manager wants you to create a prototype Java application using menus that will calculate the cost of a customer getting an oil change, car wash, or both. This application should add the appropriate amount to the total cost when services are provided. When the total menu item is selected, a message box should display the services purchased and the total amount. Allow the client to use the clear menu item to wipe out the memory and start fresh for a new customer. The exit menu item should close the application. Use the screen designs below to model your application.

    Learn More
  10. CIS355A Week 7 Course Project Flooring Application User Manual and Application Code

    CIS355A Week 7 Course Project Flooring Application User Manual and Application Code

    Regular Price: $25.00

    Special Price: $20.00

    CIS355A Week 7 Course Project Flooring Application User Manual and Application Code


    Your application must include at least three tabs. The user will choose wood flooring or carpet, enter the length and width of the floor, as well as the customer name and address. The application will compute the area of the floor and the cost of the flooring considering that wood floor is $20 per square foot and carpet is $10 per square foot. A summary should be displayed, either in a tab or another window, listing the customer name and address, floor selection, area, and cost. This information should also be stored in the MySQL database table. The program should validate that all information is entered and that the length and width are numeric values. Any numeric or currency values must be formatted appropriately when output. Recommendations for the components used for input are
    • radio buttons—flooring type (wood or carpet);
    • text fields—customer name, customer address, floor length, and floor width; and
    • buttons—calculate area, calculate cost, submit order, display order summary, display order list.
    The MySQL database table is called flooring and has the following description.
    Field Type
    CustomerName varchar(30)
    CustomerAddress varchar(50)
    FlooringType varchar(10)
    FloorArea Double
    FloorCost Double
    In addition to entering new customer orders, your application should list all customer orders stored in the database. These will be viewed as a list, in a text area, and will not be updated by the user.


    User Manual (Due Week 7)
    Your actual Course Project and user manual are due at the end of Week 7. However, it is strongly recommended that you start your project in Week 5 to avoid many last minute issues.
    In Week 7, you will be required to submit a user manual, as well as your Java code. The user manual can be a simple Word document with screenshots that explains how to run your application. Your mark will depend both on the program quality and the quality of the user manual.
    Here are some more detailed guidelines about the user manual.
    It does not need to be long, probably not more than 5 pages, including screenshots.
    Write at the expected user's level, not too technical.
    Detail all the functionality that the application provides.
    For each function, show what is its purpose and sample execution, with a screenshot.


    User Manual Points Description
    Sufficient length to describe the application 5 Manual contains explanation in detail of all relevant areas of the application
    Contains screenshots of the key interface components 5 Images of each section of the application
    Operations are explained 5 Detailed operation of each section of the application
    Written to the user's level and is not technical 5 Must not contain code or any other technical items irrelevant to the users
    Subtotal 20


    Application Code (Due Week 7)
    The following grading rubric will be used for the code portion of the project.
    Flooring Application Points Description
    Standard header included 2 Must contain program name, student name, and description of the program
    Program compiles 2 Program does not have any error
    Program executes 2 Program runs without any error
    Includes at least 3 tabs 10 Three or more tabs are used
    Includes components for all required inputs 35 Components for customer name, address, floor type, length, width, area and cost with buttons to calculate area, calculate cost, display order summary, and display order list are included
    Area calculation 4 Area is calculated correctly
    Cost calculation 5 Cost is calculated correctly
    Included data validation 10 If no values or non-numeric values are entered, the proper error message should display.
    Correct data is stored in the database table 10 When values are entered, the data is stored correctly in the database table.
    Customer orders are displayed in a list 10 All records saved to the database are displayed in a list with appropriate formatting.
    Correct output is displayed 10 When values are entered, the order summary is shown with appropriate formatting.
    Total 100

    Learn More

Items 1 to 10 of 12 total

per page
Page:
  1. 1
  2. 2

Grid  List 

Set Ascending Direction