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

Adding future expansion points

 
Richard Levy
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

While developing my SCJD I've come up with all sorts of crazy ideas for extending it into the most amazing application ever! However, I realise that this turns the assignment into a never-ending development and the documentation for the assignment says that you don't get extra credit for functionality that is not requested.

With this in mind, I'm creating start points for this functionality, but no implementation. In the JavaDoc for these classes I'm describing what could be done here "in the future" but not actually adding any implementation.

Shutdown hooks are a prime example. Its not been asked for but its useful, so I've got a shutdown factory, which at launch returns me an empty shutdown implementation that is mode specific which subsequently gets added as a shutdown hook into the Runtime object. Like I said, the actual class contains an empty implementation and some JavaDoc about what could go here in the future.

I shall also be detailing this in my choices.txt file under a "future expansion" section.

Does this sound like a sensible approach? I don't want to toil over the app forever, but I want to indicate to the examiners that I've thought about it.

Thanks
Rich
 
Luiz Reginaldo Curado
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Richard.

I began my assignment like you, implementing much more than the required. But I saw in this forum some guy that had your score reduced because of this... I think the revisor do not liked to analyse a lot of code... :roll:

In my case, I left only the required... And also an option to delete a database record. No more than this. The delete option, in my case, is used to show that my gui can be improved - and I say this in my choices.txt.

Well... It's what I think. The important is: write in your document files all your decisions.
 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Richard,

You can build an easy to extend architecture and you can document this in your documentation. I do the same (by example I have a points like : "how to extend the main window", "Future extensions").

Regards M.
 
Lucy Hummel
Ranch Hand
Posts: 232
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Richard,

At the moment I do the userguide.html stuff. To stress out I write the user documentation.

And I found extra checking, extra windows that I have to document. Since their are not required by SUN, I deleted some of them.
 
Jonathan Cole
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In the real world when you implement more than what the customer requested (even for free) you introduce more risk. You also introduce more code that would need to be maintained and at a minimum more for a reviewer to read.

If I were grading your submission I would knock you for anything that I had to review that was not in the assignment.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic