1. I have to simulate a business that allows two main types of users which are:
The directions of my project do not specify how many employees or how many managers but I feel that I should design this program with one manager and many employees.
2. Without giving to many details about my project, this project is a ticketing type of project where the employee can submit a ticket and the manager can review it and choose to approve it or deny it. Both the manager and employee have separate home pages and employee can view his tickets pending tickets and tickets resolved, and of course the manager can view both pending tickets and resolved tickets from employees but also can view all employees as well as choose only one employee out of the list to look at ticket submits.
• Hopefully the help I'm looking for here is for someone to possibly give me a good blue print on how I should design the above user stories from number 2, for example should I start with coding it out first or create database with users first?.
3. Documentation 5% - (javadocs) ----> I understand this to be a way to create comments in my code which will help me and whoever needs to read my code in the future my question is what is the best practice for achieving good documentation? Should I create documentation on every page of code just detailing what is being done? Is there an art to documentation?
4. User Interaction 10% ----> I understand this part which is basically just the user experience / interaction with my app
5. Unit Testing (20% coverage) 40% -------> I understand this however Im unsure as to how to run my code in Eclipse to see coverage, I was able to see coverage on a project I worked on in intelliJ but I cant figure it out for eclipse
6. Presentation 5% ----> I understand this part
7. Data Persistence 5% -------> Does this mean I need to create my program in very specific OOP way so I will be able to perform crud from editor directly to database?
8. Logging 5% ----> I think this means to print out a log of text information to show what state/states my program is in when it is running, is this accurate? Can I achieve this with log4J? If so can someone tell me how?
TECHNOLOGIES I need to use are:
With the technologies mentioned above and with the project requirments also listed above, can someone possibly give me a good starting point to start this project? Any suggestions or any help is appreciated.
5. Unit Testing
20% is not much so you could just test the business logic.
7. Data Persistence
This just means the data can be retrieved even if the program is turned off. The technologies list has jdbc and postgres listed so they want you to use postgres db to persist the data.
log4j has a learning curve. I suggest thoroughly reading the docs if you can't get it working from a sample.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop