a Java Bean to represent a diary page in a pocket diary

This assignment is designed to test you ability to develop one or more Java Beans and deploy the developed beans in an application development environment called NetBeans. You are required to develop a Java Bean to represent a diary page in a pocket diary. A pocket diary is longer than it is wide. You can assume that the diary will be laid out as pairs of pages. If you are unsure about what this application should do look at a pocket diary. At the top of each diary page the month of the year and the year are displayed. Each page in the diary is divided up into rows with each row representing an entry for a day of the week. Each entry for a day of the week has the date and the name of that particular day. The bean is customisable at design time via the selection of the year and the month. The diary page must be localised in some way by including the To calculate the day of the week for a particular month and year you are required to implement Zeller’s algorithm. No other means of calculating the day of the week is acceptable. This algorithm is detailed in Appendix 1(attached file). You are also required to produce 4 customised buttons as Java Beans. One pair of buttons will display the previous page or the next page of the current month while the other pair will display the current week in the previous month or the next month depending on which button is pressed. You will have to take into account that different months have a different number of days. Once you have developed the diary page bean(s) and the buttons you are required to put them into appropriate jar file(s) and make them available to the NetBeans environment on the graphical components tool bar. You are now required to develop an application which makes use of the components that you have developed. You should therefore use the components to implement an electronic “pocket diary?? application. You must use NetBeans to develop this application. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform it will be run throug the command line on xp