What is a good pattern I can use for designing an HR system

Question

0.00/5 (No votes)

See more: (untagged)

I am trying to design a small module of an HR system. It deals with applying for leave. The organization I am designing for has branches in various countries. Each branch has their own norms when it comes to applying for leave.

Each branch manages their own database of employees. Moreover you'd find that the structure/attributes differ from branch to branch for an employee. Do I have to model an employee for each branch?

Now each employee has associated forms (UI) with it depending on the branch that employee is from. Basically this form (usually a web interface or page) has to have input fields corresponding to the underlying employee object's properties (or fields).

When I googled up for patterns for an HR system the visitor pattern showed up. Not sure if this can do well. In the future we may have different centers, different rules, etc.

Posted 2-Feb-10 0:55am

deostroll

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Answer 1 · 2010-02-02T03:33:00

Solution 1

deostroll wrote:
Do I have to model an employee for each branch?

You could put your common attribute inside an employee class and then inherit that class.

deostroll wrote:
Now each employee has associated forms (UI) with it depending on the branch that employee is from.

How about MVC?

Posted 2-Feb-10 3:33am

Abhinav S

Abhinav S · Answer 2 · 2010-05-03T19:29:00

Solution 3

Have a look at the MVP / MVC pattern to build your UI / view.

Posted 3-May-10 19:29pm

Abhinav S

Christian Graus · Answer 3 · 2010-05-03T19:30:00

Perhaps people like yourself need to stop worrying about patterns and learn how to program instead. Using patterns will NOT cause your project to be any better, if you don't have the skills to write good code in the first place. The right question to ask is, do any patterns seem like they apply here, not, what patterns can I use here, if they fit or not ?

As far as I am concerned, the MVC pattern works best if the underlying architecture allows for it ( you don't say at all what sort of app this will be ), AND then it is best used where the view or controller are likely to change. Beyond that, it's a bit convoluted in a world where the controller and view are intimately tied to each other, and is way overused today as some sort of magic bullet.

What is a good pattern I can use for designing an HR system

3 solutions

Solution 1

Solution 3

Solution 4

Add your solution here

Preview 0

Existing Members

...or Join us