Category: Software Engineering

Due: 3/9/2020 11:59 PM 3/11/2020 11:59 PM

Write a Java program that does the following jobs.
Step1. Creates a House table with property id (PID), neighborhood, year built, sqft, number of bedrooms, number of bathrooms, and price.
Step2. Reads data from the CSV file and insert the houses into the table created in Step 1.
Step3. Interact with the user, where the user can select one of the following actions.
        – (Q) Quit: quit the program
      – (A) Add a house
      – (C) Calculate average house price
      – (P) Print a subset of the houses based on SQFT
      – (B) Print a subset of the houses based on numBeds and numBaths

The user can choose one of these actions by typing Q, A, C, P, or R in the console. When adding a house, the user must provide property id (PID), neighborhood, year built, sqft, number of bedrooms, number of bathrooms, and price through the console. When selecting a subset of the houses based on SQFT, a lower bound SQFT value must be provided. When selecting a subset of the houses based on numbed and numBaths, lower bounds must be provided. 

Four files are provided with the assignment.
1. AmesHousingDB.java: the main class of this assignment.
2. Database.properties: file for Apache Derby
3. SimpleDataSource.java: file for Apache Derby
4. Ameshousing.csv: sample CSV file for Step 2.

Submit one source file (AmesHousingDB.java). In other words, Database.properties, SimpleDataSource.java, or Ameshousing.csv should not be submitted. In modifying the source file,

1. Do not change the file (class) names. Three Points will be deducted if you have different names. Class name changed due to Canvas (e.g., Classname(1).java, Classname(2).java) is ignored.
2. Fill in your name in the @author section of the comment in each of the files. If you do not, two points will be deducted.

I need help coming up with a  Pseudocode for my assignment. I’m trying to design a game of amazons type of game. It doesn’t have to be to difficult. Should be in C#. I just need help coming up with a good pseudocode. I’ve attached some more information on the assignment if you need it. Not a difficult assignment at all I’m just not very good at this yet. This is my own individual assignment

I need help coming up with a  Pseudocode for my assignment. I’m trying to design a game of amazons type of game. It doesn’t have to be to difficult. Should be in C#. I just need help coming up with a good pseudocode. I’ve attached some more information on the assignment if you need it. Not a difficult assignment at all I’m just not very good at this yet.

I can extend deadline till tomorrow night if needed. The assignment is simple. I am trying to make a game> I came up with an idea and concept but haven’t gotten it all the way figured out. I need you to write down in Microsoft word or whatever you feel more comfortable with, a requirements page that you think would be good for this project. Write it like it’s my assignment because I’m going to send it to my teacher. I am having trouble coming up with ideas and things, that’s why I’m coming here. Whatever creative ideas you think would be good for this project and that I should use put it in this requirement page. I’m attaching all the information you need to help decide.

This is what I’m essentially wanting you to write:

Requirements Documentation
Detailed requirements are essential for building valid software (i.e., the software the
customer wants). Your requirements should be as complete and as detailed as possible.
You should organize your requirements in a sensible, hierarchical manner. Each requirement
should be given a unique identifier that can be used to trace that requirement through the
subsequent phases of the software life cycle. Your requirements document should follow the
standard below, which is based on the IEEE/ANSI 830-1998 standard. For your require-
ments document, you do not need to include appendices (unless you have need to) or an
index (an index would be nice, but unless you have a tool to generate an index automati-
cally, this is too time-consuming)

Specific requirements
Section 3(you don’t need to see this), which deals with the specific requirements, will vary depending on the
software being built. I suggest using a simple numbering scheme. Below I show a
partial set of requirements for a poker game, using a similar system. These require-
ments are far from complete – they are simply provided as an example.
Playing Cards
1.0.0 The game should use a standard deck of 52 playing cards, with no
jokers.
1.1.0 User should be allowed to choose the design used for the card
backs from 2 provided designs.
1.1.1 Solid blue design should be provided.
1.1.2 Red thatched design should be provided.
1.2.0 Each non-face card should display the appropriate numerical
value.
1.3.0 Each non-face card should display the appropriate number of suit
symbols.
Game types
2.0.0 User should be allowed to choose the type of poker game they wish to
play.
2.1.0 The game should allow the user to play 5-card draw, according
to standard rules.
2.2.0 The game should allow the user to play 7-card stud, according to
standard rules.
2.3.0 The game should allow the user to play Texas Holdem, according
to standard rules.

Read the attached pdf and follow all of the instructions so the assignment can be turned in properly. Provide solutions to the conceptual problem and the reasoning behind it. Put all files including solutions and code into one tar zip file.

PLEASE USE sample code provided in the PDF and fill out missing code to make the program work.

Im attaching different separate sheets of info that should be all you need. For an assignment I need you to come up with a good introduction that will have “Definitions, acronyms, and abbreviations – list and define all of these that appear
in documentation, References – include references for anything that is trademarked or copyrighted here (e.g., game instructions, algorithms such as the LZW compression algorithm for images, etc.)”.

I need a general description section which would include” Product perspective – give a little background about why the software is being built and why it will be useful; one good paragraph will do, Product functions – describe fundamentally what the software will do; again, one good paragraph will suffice, and you do not need to go in depth (the specific requirements section will cover the in-depth functions, User characteristics – describe who the end users will be,  General constraints – describe the general limitations of your software (e.g., system limitations, does not work over a network, etc.), and  Assumptions and dependencies – examples of these would be: assumes end user
has QuickTime installed; requires Visual Basic runtime to be installed on end users
computer

I basically came up with an idea for a game to create because that’s the assignment but I need help deciding on all what should be done and how it should be made. You don’t have to actually create it but come up with some good stuff for the sections mentioned above and write it out neatly and in a presentiful way that would be acceptable for a teacher.

While I don’t expect you to have to get very detailed, you can see what the requirements involve right here in the deliverables file. It’s the first thing listed under the Programmer’s Manual.

But to give it short requirements have the following sections:
1. Introduction – This contains the scope statement that we made, definitions/acronyms/abbreviations of terms we use, references to copyrighted material we used.
2. General Description – A paragraph describing why we’re making the game and why it is useful (like, a paragraph that rattles on it being fun and such), product functions, user characteristics (essentially who will be using the game), limitations of our software (we aren’t making an online game, so no network compatibility for example), dependencies that a user needs in order to play (.NET framework and windows probably, for a C# game)
3. Specific Requirements – Pretty much what the requirements are for the game. Think a list of rules in how the game operates. In terms of our game that pretty much means the rules and how the game is expected to function. (4 queens to each player, and each must move and fire an arrow to pass their turn, as a example)
4. Appendices – We probably won’t need any of these, unless we feel it’s necessary. You can ignore this one.
5. Index – We also probably won’t use this one since indexes aren’t very necessary and time consuming.

I attached the scope statement that I updated for C# and the dependencies document. Don’t sweat it too hard, we can refine the document together as time goes on together. The biggest thing will probably be Specific Requirements since that’ll involve how we want the menus to work and how the game operates, but since the game has a relatively simple premise it should be fine- though there are a lot of conditions to check for once we get into programming-
Like, for example, when someone’s turn starts, we need to check if any of their queens can move. If not, they loose. If they can, let them move a queen, and fire an arrow (they should be able to fire an arrow if they were able to move, so we may not have to check for that) Another thing might be checking if they’re allowed to move into a selected space (can’t move into or past other queens/arrows)
It’s a bunch of jargon but the specific requirements will help us figure out how we want to structure our game. Again you probably won’t have to be too detailed, it’s mostly the rules of the game and what a player can do, it’s not pseudocode.

Programming Assignment 1: Theater Reservation System
General Requirements
Java 8 introduced new APIs for Date and Time to address the shortcomings of the older java.util.Date and java.util.Calendar. You have to use these new features of Java 8 to manipulate time information in your program.
In your implementation, ignore cases to recognize a user request. Whenever your program asks for a user input, it prompts the expected format of the user input. The system should be user-friendly. That is, a user including me should be able to easily use the system without any manual.

Overview
This assignment is to design and implement a simple theater reservation system. The design goals include identifying classes, their responsibilities, and their relationships. These goals can be achieved by by conducting use case analysis, noun-verb analysis, producing CRC cards, and producing UML class and sequence diagrams.
Reservation System Description
During the season between December 23, 2020 and January 2, 2021, the theater presents “Miracle on 34th Street”. The show is scheduled at 6:30 pm and 8:30 pm on a given date.
System Functions
When the system starts, it loads “reservations.txt” containing reservations made earlier. If the file does not exist or empty because it is the very first run of the program, the system doesn’t load anything.
Then, the program prompts the following initial menu:

Sign [U]p  Sign [I]n  E[X]it
A new user first signs up for the system, and then sign in the system using the user id and password. An existing user can directly sign in.
Sign [U]p: The system asks for a user id and a password. The user id must be unique in the system, and a simple password is acceptable.
Sign [I]n: The system checks the validity of the user id and password entered by the user. The system presents an error message for any non-existing user id or an invalid password. With a valid credential, a transaction starts for the user.
E[X]it: This option terminates the system, meaning you will get an operating system prompt back to you. This is not a user option in the real world but is used as a way to persist the in-memory data in a file for this assignment. With this option, the system copies the valid reservations of all registered users from the in-memory data structure to a file called ‘reservations.txt’.
When a user signs in, a transaction mode starts. That is, a transaction mode starts with sign-in and ends with sign-out. In the transaction mode, the user can choose options from the following transaction menu. This menu will be displayed after each selected option is done until the user enters O the sign-out to finish the transaction mode.
[R]eserve    [V]iew    [C]ancel    [O]ut   
[R]eserve: During a reservation session, that starts with R and ends with a user’s confirmation, the following interactions are done between the user and the system. The system prompts the user to enter the date and time of the desired show. Then, it displays the list of all available seats for the requested show. The user can reserve multiple seats across different sections for the given show by entering the corresponding seat numbers. If the user attempts to reserve an unavailable seat, the system prompts an error message asking for another seat. Once the user is done with the reservation for a particular show, the system asks if the user wants to make another reservation or to confirm the reservation session, which will end the reservation session. The system saves all the reservations made in that session, technically saving them in an in-memory data structure of your choice such as arrays or array lists.
[V]iew: The user should be able to view the entire reservations of the user or the user’s reservations by date. Reservations are diplayed in the order of date and then time.
[C]ancel Reservation: The system asks for the date and time of the show and displays all the seat numbers of the show reserved for the user. The user selects seat numbers and the system cancels them, technically removing them from the in-memory.
[O]ut: The system displays a receipt for the transaction. The receipt begins with a confirmation number and is organized by shows with reserved seats in the order of date and time of the shows. For each show, include the date, time, seat numbers, and the total price charged for the show. (See the price and discount information below.) At the end of the receipt, include the total price charged for this transaction.
When the user signs out, the system prompts the initial menu again asking for another user to sign up or sign in or to terminate the program.

Sign [U]p  Sign [I]n  E[X]it
Seat and Price Information
In the theater, there is 1 auditorium with four different types of sections (Main Floor and South, East and West Balconies) with different ticket prices as shown below. (The seat numbers are listed inside of the parentheses.)

Regular single ticket prices
Main Floor: $35 (left side: m1-m50, right side:m51-m100), $45 (m101-m150)
South Balcony: $50 (sb1-sb25), $55(sb26-sb50)
West Balconies: $40 (wb1-wb100)
East Balconies: $40 (eb1-wb100)
Discount Nights (December 26-27): $20 for any seat
Group Discount:
5-10 persons: $2 discount per ticket
11-20 persons: $5 discount per ticket
Does not apply during Discount Nights
Combined transactions do not qualify for discounts. (i.e. if a user purchased three tickets during one transaction then purchased two more tickets during another transaction, then no group discount is applied for any of the transactions and the combined.)
Group discount will be applied for the tickets purchased for a single show.
Group discount will be applied for the tickets purchased for several sections in a show. For example, a user reserve seats for a particular show through multiple reservation sessions (remember a reservation session begins with [R] and ends with a user confirmation), the latest reservation should apply a discount considering previous reservations made for the show. For example, if a user reserved 2 seats in one reservation session and reserve 3 more seats in another reservation session for the same show, the system consider the user served 5 seats for the show and applies the group dicount.
Cancellation in part or whole may cause recalculation of ticket price if number of tickets fall below lower limit of people. (i.e. 11 tickets reserved, 2 cancel, ticket prices recalculated for 5-10 bracket)
Submission Due Dates
Softcopy of your implementation by 11:30 pm Tuesday, February 11.