Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: URLyBird 1.2.1 Functional Requirements - Create and Delete Records

 
Xie Ruchang
Ranch Hand
Posts: 160
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the Use Case analysis point of view, these are what the CSRs do
  • Take bookings on the phone.
  • Generate a list of accomodation that meets the need of the customers.


  • For take bookings, we need to book and unbook an accomodation (in case book wrongly), this translates to update a record in database.
    For generate a list of accomodation, this is basically search, this translates to read record(s) from the database.
    There is no use-case to create and delete accomodation. But somewhere in the company, someone must be doing that. Probably out of the scope of the assignment. Just like the reports are being printed from the database as mentioned in the specification.
    Question A
    Am I justified in omitting the creating and deleting of records in the implementation based on my use case analysis?
    Question B
    The DBAccess interface did have create and delete records? Should I just implement them and leave them unused?
    You may not need to answer the questions but I would like to know what are the approach you take.
    I am sorry if these questions have been already discussed in other threads, and I would greatly appreciate it if you could refer me to those threads.
    Many thanks.
     
    Don Resnik
    Greenhorn
    Posts: 18
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Frankie,
    I had these exact same questions not too long ago. I decided to write code for both create and delete record methods that match the functionality of their respective comments in the interface. The methods cannont be accessed via the GUI, becuase I agree that these functions are beyond the scope of a customer service rep (CSR) (and they are not requirements either). But the code is there and it works if Sun wants to take the time to test it.
    On the topic of actual requirements, it does not say that CSRs should be able to un-reserve a record (as you mentioned in your use case). As a matter of fact, if they could, how could you ensure that any reservation was safe if the next CSR could just un-reserve a reservation and give it to someone else.
    I am trying to not go outside the requirements which say the CRS should be able to search for records and reserve records. Once one of my records is reserved, it is no longer available to be updated. I realize this is not a good real-world solution, but these are not good real-world requirements.
    Hope that helps,
    Don
     
    Xie Ruchang
    Ranch Hand
    Posts: 160
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Thank you Don for your reply,
    I decided to put in the unreserve function because the CSR could make a mistake or the customer requested to cancel it, which is very common. I agree with you on the security aspect that any CSR to cancel other CSR's booking. Since, two security measures are required, I assume it is based on trust. Like what you said, the specification is not good for the real world.
    Best Regards!
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic