• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Discrepancies in Sun's Specifications

 
Kevin Thompson
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sun's specifications say one thing, and their code says something completely different. How did other people here handle this issue?
WHAT THE SPECIFICATIONS SAY:
Here is what Sun's written specifications say about the user's ability to modify data:
"The user should be able to select the origin and destination of flights...." "The user must be able to book one or more seats on a chosen flight..."
ERGO: The user can query data using the origin and destination fields, and the user can change the "available seats" field. That is it.

HOWEVER, HERE IS WHAT THE PROVIDED JAVA CODE SAYS:
(Sun describes this provided code as "complete and functional")

The user can query existing records.
The user can add totally new records. <-------- not in specs
The user can delete existing records. <------- not in specs
The user can modify ANY field on ANY existing record. <--- not in specs

I think based on the limited information, I am going to have to assume that people at Sun don't know how to write specifications, and assume that I have to finish off 100% of all the code provided, even if the specs say something different.
Is this how other people handle this issue???
This is bad because a Java program that can query data and update only one field on already existing records, is much easier and simpler than a Java program that can add, browse, delete, and modify anything.
 
Lora Louise
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kevin, follow your first line of thinking unless you want to do the rest as an academic exercise. The rest of the Data class's functionality does not need to be used in this assignment in order to pass, or even get a perfect score. That is a fact!
Think of the rest of Data's methods as possiblities for extending the application. Perhaps adding an "adminstrator" mode which would give commands to delete records or modify more flight attributes.
In fact, I would strongly suggest you NOT turn in an assignment which allows any user to delete/add records or modify any field. The grader might fail you for giving the user too much control.
[This message has been edited by Lora Louise (edited October 05, 2001).]
 
Kevin Thompson
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks lora.
OK, so just to recap - these are the specs that people are using - right?
QUESTION: What can the user do?
ANSWER:
1. User can query records on the "origin" field. (For a specific origin or any origin(using wildcard).
2. User can query records on the "destination" field.(for a specific destination or any destination(using wildcard).
3. User can decrease the "available seats" field on any record by booking a flight.
Note, it is implied that the user can not increase the number of available seats by removing a booking, they can only decrease the number of available seats.
This is good, if this is all there is to it. I already had a functioning program that added records, deleted records, and modified any field, I just hadn't figured out how to do it all with a JTable. I guess I will take all that code out of my program.
 
Lora Louise
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kevin,
You probably meant this, but just to clarify I think a user should be able to query on a destination and origin at the same time. Sort of a boolean AND for both combo boxes.
Most people seem to lose points, or even fail, because they don't implement the remote and local access possibilities. Or, their locking mechanism isn't good enough.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic