payroll system development duration

[ad_dur]

---

depende na na sa inyo .. daghan man mo sa inyo team if everyone cooperates & do their share dali ra ang trabaho ..

[kuelcoder88]

OK ra if you already have procedures and processes that you require. But if you need to come up with your own algorithm for computation dili jud feasible ang 22 days. Take for example DTR, if you don't have an algorithm nga naka ready mahurot siguro nimo ang majority sa imong time just trying to come up with an algorithm nga maka solve most of the problem sa DTR (that includes Absents, Undertime, Late, Overtime, Leaves, Change Schedules, Broken Schedules, Night Premiums, etc). Coming up with a formula is very tedious, so if apil na sa imong 22 days, dili jud ka mahuman on time.

"with your own algorithm for computation" as long naa formula ug data, making plan? i gues for me it takes 2 days..

[moodsey211]

"with your own algorithm for computation" as long naa formula ug data, making plan? i gues for me it takes 2 days..

Easier said than done.

[fixyourself]

VB.net with MySQL? hmm, semms good but for me Web Application Payroll System is better. 22days? for me is enough.. if u have 4 to 5 members in a group and then with focus. coz if u have the exact data or procedure what system can do that is no problem. the big scope in this system is the user ryts and the payroll computation only. after that this system is running..

biometrics? use C for it. use linux for easy access mysql libraries.

using web application is you have no problem if what OS will use. either linux or windows. and system can be access easy online, with no installation of the said system.

this is just my point of view... thanks and God Bless!

There is more to software engineering than focus. Provide a project plan / road map within a range of 22 days, with 6 team members, then we'll decide if its feasible.

I have a few questions about your suggestions above.

* What makes a web based payroll system better than a desktop based payroll app?

* Biometrics, won't this add another scope if you are to implement a web based payroll system? (unless if you are hosting your own application)

* Biometrics, why C? there are lots of MySQL connector distributions.

[salbahis]

one question, how would you link biometrics to php?, are you using XML-RPC?

web application why not XUL?

[niehrx]

if you guys keep on saying 22 days isn't enough... well wala gyud mo mabuhat ana... payroll computation isn't that difficult... even with tax. start something and start right away. im not saying bug free na na. there will be always a bug no matter how perfect your system. at least by the end of 22 days... well, you come up with something. rather than keep on whinning 22 days would be impossible. im not trying to be a smart ass im just saying based on my experience. i did a payroll before. i also got about the same deadline. so what i did, i simplified the design as easier as i could. though honestly it was buggy, and they can't blame me for that. thing is dili man sad na ma go into production without parallel running either manual or legacy payroll system after several payroll period...

[salbahis]

if you guys keep on saying 22 days isn't enough... well wala gyud mo mabuhat ana... payroll computation isn't that difficult... even with tax. start something and start right away. im not saying bug free na na. there will be always a bug no matter how perfect your system. at least by the end of 22 days... well, you come up with something. rather than keep on whinning 22 days would be impossible. im not trying to be a smart ass im just saying based on my experience. i did a payroll before. i also got about the same deadline. so what i did, i simplified the design as easier as i could. though honestly it was buggy, and they can't blame me for that. thing is dili man sad na ma go into production without parallel running either manual or legacy payroll system after several payroll period...

rolling it after 22 days and still buggy?, thats not the way to go.... we are whining about 22 days is because it is impossible to roll it out without any bugs with in 22 days, debugging takes time also...

[moodsey211]

if you guys keep on saying 22 days isn't enough... well wala gyud mo mabuhat ana... payroll computation isn't that difficult... even with tax. start something and start right away. im not saying bug free na na. there will be always a bug no matter how perfect your system. at least by the end of 22 days... well, you come up with something. rather than keep on whinning 22 days would be impossible. im not trying to be a smart ass im just saying based on my experience. i did a payroll before. i also got about the same deadline. so what i did, i simplified the design as easier as i could. though honestly it was buggy, and they can't blame me for that. thing is dili man sad na ma go into production without parallel running either manual or legacy payroll system after several payroll period...

A system that is not stable is not a system at all. I mean kinsa gud mugamit ug system if kahibaw ka nga daghang problema ana. If a system would not be used in production duha ra padulngan ana, trash can or re-development. Dili lalim magbuhat ug program and if you could already see unsay outcome why waste your effort? Pila ka adlaw gud ka mag pulaw para himo ana then kas.ahan ra ka ug ingon nga dili namo ni gamiton kay 'bati', for me dili worth it.

[niehrx]

hehe. cge oi, bahala na mo dha. hehehe. mag porn nalang ko.

[fixyourself]

hehe. cge oi, bahala na mo dha. hehehe. mag porn nalang ko.

haha... we are just being realistic here.. in systems development, there are lots of things to consider than just having a running system.

running_system != working_system