Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

B&S assigning contractors

 
Davinder Kohli
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am little confused about if I should assign a subcontractor to an owner or should I assign certain amount of workers from a subcontractor to an owner? In the latter situation I can create records within the db to maintain which customer has how many workers from a subcontractor...a little more involved approach than assigning the entire subcontractor(with all its workers) to an owner.

Should I also implement "Cancel Order", "Modify Order" in addition to "Place Order"?

Thanks,
Dave
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 11854
185
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dave,

I am little confused about if I should assign a subcontractor to an owner or should I assign certain amount of workers from a subcontractor to an owner? In the latter situation I can create records within the db to maintain which customer has how many workers from a subcontractor...a little more involved approach than assigning the entire subcontractor(with all its workers) to an owner.


My advice would be not to over complicate this assignment. Your instructions probably do not mention anything about booking partial records, or subtracting desired numbers of contractors from available contractors (and handling negative numbers).

The consensus in this forum seems to be that the entire record should be booked for one owner. Most candidates seem to get very good scores with this aproach.

Should I also implement "Cancel Order", "Modify Order" in addition to "Place Order"?


Again - this is not listed in the instructions, so I would not add it in.

You may have a line in your instructions telling you that you will not get extra marks for going beyond the requirements. So adding these features won't help your score, but could potentially damage it (if you make a mistake).

Regards, Andrew
 
Davinder Kohli
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Andrew for your kind response.

If this is the case, then the GUI (rather the entire application) seems to be simple, not trying to trivialize it though.

I referred to this SCJD book which explicitly talks about listing out the use cases, kind of enacting the real world application.

Also, quoting the assigment, "This document deliberately leaves some issues unspecified, and some problems unraised."

I am going with your advice, and sticking with the MUST requirements listed in the assignment.

Do you think it is a good idea to document the use cases, and other enchancements that could be made to this appliciation?
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 11854
185
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dave,

If this is the case, then the GUI (rather the entire application) seems to be simple, not trying to trivialize it though.


Agreed. But at the same time, the assignment does cover a lot of different topics and techniques. Anyone who completes the assignment can be proud of the number of APIs and tools they learned and used for this assignment.

The additional functionalities are not required to prove that you have mastered any particular technique. If you already have the update functionality working correctly then adding an unbook function will be 5 minutes work - you will not be using any new J2SE APIs to add this function. So why have them?

I think one of the reasons the SCJD exam is so good is because it does cover a large number of APIs, tools, and techniques. When you complete the SCJD you will have worked on front end GUIs, back end systems, raw file I/O, threading issues, networking issues, documentation, designing ... An extra function or two will not change that.

Also, quoting the assigment, "This document deliberately leaves some issues unspecified, and some problems unraised."


I think you will find that this is more to do with dealing with issues such as how you handle InteruptedException, or how you deal with the instructions telling you that fields should be null terminated when they are clearly filled with blanks. That is - these are issues and problems related to complying with the "real-world type of specifications" (in other words - inacurate/incomplete specifications ).

I am going with your advice, and sticking with the MUST requirements listed in the assignment.




I referred to this SCJD book which explicitly talks about listing out the use cases, kind of enacting the real world application.

Do you think it is a good idea to document the use cases, and other enchancements that could be made to this appliciation?


I think that is a very good idea.

When it comes to submitting your assignment, you may wish to reduce the unimplemented use cases to bullet points in your design decisions document - just a brief note to say that you considered the use case for 'xxx' but decided it was out of scope / undesirable / ... That way the assessor knows that you did consider these issues.

Regards, Andrew
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic