URLyBird [...] take bookings only within 48 hours of the start of room occupancy.
Did your instructions have anything extra?
Did you put anything in your design decisions about the 48 hours?
What did the examiner say in their comments?
Anyway, we'll be graded by human beings. With a "MUST-BE-ONLY" development, it's possible that your grader thinks "Great ! The shortest assignment I ever saw, I'll save time with that guy !" and that you get a high score thanks to that. The same grader on another mood (or another grader), could "Mmh... This guy really did the minimum in all areas" and ... (I let you guess ).
I documented all my reasoning regarding this very well in both the choices document and the user guide.
"This application fails because it does not meet the application specifications. The sepcification states that "URLyBird" is a broker of discount hotel rooms. They take bookings only within 48 hours of the start of room occupancy. The submission does not meet this requirement. The application allows bookings for any rom an any time with no date checking. It even allows users to book rooms for dates in the past."
This application fails because it does not meet the application specifications. The sepcification states that "URLyBird" is a broker of discount hotel rooms. They take bookings only within 48 hours of the start of room occupancy. The submission does not meet this requirement. The application allows bookings for any rom an any time with no date checking. It even allows users to book rooms for dates in the past."
Bookings should only be taken within 48 hours of the start of room
occupancy. You should consider this rule before booking a room.
The current release of this application will not prevent you from
booking a room outside of this 48-hour window. However, you need to
take this into account before choosing to book a room.
A 48-hour business rule was mentioned in the specs. I decided not to
implement this in the application. Instead, I include this business
rule in the User Guide and expect the CSRs to handle this rule
manually. My application allows the booking of any room
that has not already been booked for the following reasons:
1. Many rooms in my database file are either for rooms way in the
future or way in the past. Implementing this business rule would
allow for not very many rooms in my database to be booked.
2. There is currently no GUI administration type of function in this
application that would allow updating the available date of rooms.
Also, there is no GUI functionality for adding new records. The scope
of the assignment deals strictly with searching and booking, so once a
room is booked, it stays booked with no updates to either the owner
or date available fields.
3. The instructions say the "marking process will expect the exact
same data without any changes". I wanted to make sure that there will
be records out there in my database that the user/grader can successfully
4. There also could be many issues dealing with different time zones
that would need to be researched before implementing date functionality.
I would need to talk to the users more to gain a better understanding
of their requirements before coding this rule.
This 48 hour booking restriction could certainly be a future enhancement
that is implemented at the same time as enhancements for administrative
I posted a separate posting regarding my appeal frustrations. (separate appeal posting) Does anyone have any ideas on how I can get them to respond to me? I have no idea if they are actually considering my appeal or not. I have heard nothing back, despite multiple emails requesting a status.
I have sent an appeal to Sun regarding my 48 hour autofailure. However, I am very frustrated because I have heard nothing back from them. This whole thing started back in February. I'll put the timeline of what has happened below.
2/20 - received initial auto-fail in database
2/20 - emailed high level appeal to the who2contact email
2/23 - a Sun rep sent a question to my grader and he responded
2/23 - Sun rep sent response back to me (I disagree with his response)
2/23 - I sent a detail appeal request back to this Sun rep
3/8 - sent email requesting status to same Sun rep
3/14 - sent email requesting status to who2contact address (w/email trail)
3/18 - talked with a new Sun person in Educational Services (Colorado) and sent him the email trail - he was going to chase it down
3/25 - talked with a different Sun person in Educational Services. Found out that the original Educational Services guy was now on vacation for a week. She asked me to send her the email trail
Ughhhhhh!!! Will this ever end? Is this typical? I would expect that they would tell me if they were not considering my appeal, but I don't know.
Does anyone have any other ideas on how I can get them to respond to me? I really don't want to dump the $$$$ for resubmission if I don't have to. I just want to find out if they are still considering my appeal or not.
I think that Phil has gotten slightly ahead of himself on this. Terry, I am sorry to know that you have to go through all this. Both myself and Vlad have implemented the 48 Hours rule in our submitted assignment. If you do a search on my name or the memeber id, you will find the thread where Vlad actually suggested an alternate strategy for me to parse the date field. I actually have implmented the check for both 48 Hours range as well as to disallow the booking if the date is in the past.
Phil, the thread that you have mentioned above, I was trying to caution Linda not to go overboard in terms of implementing an administrative GUI front-end to manage the date data.
Just focus on all the MUSTS in the problem statement. What I did is that I extracted out all those MUST statements and made a separate document. I kept referring to this document throughout my SCJD effort to keep myselft focused. These are the things that you MUST absolutely do. Don't worry about "nice to haves."
I am pretty sure that Vlad did not implement the 48H rule as I have sent him a private message on Dec 17, 2003 regarding this issue after he received his result.
URLyBird takes booking only within 48 hours of the start of room occupancy. However, based on the data given in the database file, we think that this requirement should be a business background process, rather than implementation requirement.
Thus, we decide not to add this constraint to the system, and we assume that there is another program which caters for updating the database file, such that the data inside the file fits the 48-hour booking requirement.
The system relies on this program to display data and book the rooms without further checking.
In our assumption, we have not added the 48 hours booking constraint into the system although it is easy to be implemented by the following ways:
The system displays only records with data available that within 48 hours. Users can only book those displayed records.
The system displays all available records in the database file. However, when the user clicks the book button to book a particular record, the system checks whether the record fits the 48 hours requirement. The booking will be succeed if the requirement is fit. The booking will be fail otherwise.
However, since the CSRs are not allow to create new records or update existing records (except the owner field), we consider that the 48 hours booking constraint as a business process background information, which is ensure by another program that generates the records in the database file, rather than the implementation enforced in the system.
However, I would not use arguments, that others have done the same and passed:
- it is not a good argument
- Sun can always say: "So what, we didn't see it. If have seen it the others would also fail".
If I do get to a point where they are not listening to my arguments, I may push them to find out if the criteria which cause auto-failure is objective or subjective (i.e. the whim of the grader).
This would indirectly deal with the fact that others have passed, but yet not use an argument that really wouldn't get me anywhere.
What's really frustrating me now though is that I can't get anyone at Sun to give me a status on what's going on. I don't know if they are still considering my appeal or not, and it's been since 2/23.
Five weeks ago I disagreed with my Sun Certified Java Developer certification Exam result and sent a full description of my reasoning and a request for review.
I have heard nothing back despite repeated attempts to get a basic status.
Can someone please respond to these questions:
1. Is my request in the process of being reviewed?
2. Will I hear back via email when a decision has been made?
Last night I sent another email to the general who2contact email:
"Your assignment is being reviewed again. I will contact you with the assessor's response within 5 business days."
I am confused. If a room's available date is last year(say 2003/04/25), and now(2004/04/17) the room is empty(No owner), a customer can NOT book this room right now?
The application allows bookings for any room an any time with no date checking. It even allows users to book rooms for dates in the past."