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

Some questions B&S...

 
A. Gazola
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ranchers,

I�m starting the development of my project and I have a few questions:


1) The requirements for the GUI functionality in the B&S state that it must allow CSRs to search contractors and book a specific record. Now, is it necessary (for the purpose of the exam) to offer the CSRs a "Remove book" functionality as well?

2) In the Search part of my GUI, the user can search for all records or for records that exactly match values specified by the user regarding the name and/or location fields. Then, I�m thinking of putting two comboboxes, one containing the names of all contractors and one containing all the locations, and the user simply selects one or both of the comboboxes e clicks a search button. Consequently, the search operation is less error-prone, as opposed to simply offering a textfield input control. Any shortcoming with this solution?

3) The DB file description says: "(...) you should assume that customers and CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them." I don�t know if I understood this specification..., In my GUI, a CSR selects a register in the table, clicks a "Book" button and the application shows a dialog asking for the "customer id number", which will be used to book the selected register in the database file. Is this solution OK with the above specification?

Thank you all for any help,

Alex
 
Jens Voss
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

1) The requirements for the GUI functionality in the B&S state that it must allow CSRs to search contractors and book a specific record. Now, is it necessary (for the purpose of the exam) to offer the CSRs a "Remove book" functionality as well?

Since a system without an "unbook" functionality would be close to unusable, I would definitely recommend to implement it, too.


2) In the Search part of my GUI, the user can search for all records or for records that exactly match values specified by the user regarding the name and/or location fields. Then, I�m thinking of putting two comboboxes, one containing the names of all contractors and one containing all the locations, and the user simply selects one or both of the comboboxes e clicks a search button. Consequently, the search operation is less error-prone, as opposed to simply offering a textfield input control. Any shortcoming with this solution?

Yes, it it very impractical when dealing with thousands of contractors in hundreds of locations (which we should suppose B&S is aiming at )
So I think it is wiser to stick with simple text fields.

3) The DB file description says: "(...) you should assume that customers and CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them." I don�t know if I understood this specification..., In my GUI, a CSR selects a register in the table, clicks a "Book" button and the application shows a dialog asking for the "customer id number", which will be used to book the selected register in the database file. Is this solution OK with the above specification?


Sounds okay with me.

Best regards and lots of fun with the assignment,
Jens
[ April 22, 2008: Message edited by: Jens Voss ]
 
A. Gazola
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Jens, thank you very much for your insights!

Just a silly question: The DBAccess interface that I received to implement has implementation comments rather than javadoc-style comments. Can I change the interface provided, converting the implementation comments to javadoc comments?

Kind regards,

Alex
 
Mary John
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
quote:
--------------------------------------------------------------------------------

1) The requirements for the GUI functionality in the B&S state that it must allow CSRs to search contractors and book a specific record. Now, is it necessary (for the purpose of the exam) to offer the CSRs a "Remove book" functionality as well?

--------------------------------------------------------------------------------


Since a system without an "unbook" functionality would be close to unusable, I would definitely recommend to implement it, too.



Hi all,

I was under the impression that many people chose not implement the unbook functionality as it is not required by the assignment. Anything that is not required will not fetch any extra marks, although in reality it may be necessary function. But sometime can lead to loss of marks, for any mistakes made in implementing it and increasing complexity of code. ?? am
I right? or wrong?
 
Roberto Perillo
Bartender
Posts: 2271
3
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mary John:
Hi all,

I was under the impression that many people chose not implement the unbook functionality as it is not required by the assignment. Anything that is not required will not fetch any extra marks, although in reality it may be necessary function. But sometime can lead to loss of marks, for any mistakes made in implementing it and increasing complexity of code. ?? am
I right? or wrong?


Totally right.
 
c tt
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any comments on the question below ?

Originally posted by A. Gazola:
Hi Jens, thank you very much for your insights!

Just a silly question: The DBAccess interface that I received to implement has implementation comments rather than javadoc-style comments. Can I change the interface provided, converting the implementation comments to javadoc comments?

Kind regards,

Alex
 
Roberto Perillo
Bartender
Posts: 2271
3
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You cannot change the signature of the methods. The Java code must remain as is. What I did, I kept the description of the method and put it in a JavaDoc above each method, along with each return, exception and parameter's description.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic