I’m not sure if “What language/tools should I be using?” is a good place to start because you could potentially use almost any language for this, which would have its own tools of which would help assist you. It mostly boils down to what you’re comfortable with using. Even still, you’ll probably end up using no less than three; one for front end, one for back end and then SQL or some framework If your not going to do the development yourself and are just trying to get a general idea, then nevermind.

Here’s how I would go about setting this up:

  1. I would make it a web app first, then a desktop application. The desktop app would be more for managmentadmin purposes, and I’d have the Web app be employeed-focused.

  2. I’m a professional with C# so I’d use ASP.Net Core 2.0 as my foundation for the web app. WIth that I could use EntityFrameworkCore as well as Identity Framework for ORM purposes. You’ll need to know HTML and CSS of course ofr the front end but you could probably get plenty of templates for all of this.

  3. For the scheduling aspect you could go with either a simple table which I think would be very easy to implement, or try to utilize a calendar plugin/library which may be a bit more difficult but could potentially be easier to read/use. You’d also probably want to know Javascript/Jquery. I’ve used a calendar plugin in JS before so I know there’s plenty out there. I’d use all these things for the first three, maybe four features. For the fifth, I haven’t done much analytical work before but I’ve heard that F# is useful for that. But I’m not sure.

  4. As far as free domain, that only ones I can think of for sure are any places that give out subdomains for free. Other than that you’d have to pay. As far as hosting, it’s the same boat, you’ll have to pay. If you wanted it all in house, it may be cheaper but way more difficult. You’d need a static IP, some machine to be a dedicated server, possibly a seperate DB server depending on your size. You’d need IIS to be set up and you’d need to have your network configued properly. It’s all doable but it depends on what you need and how soon you’d need it.

  5. You could definitely host a DB server like you would a web server but it’s similar to the web server in that one way or another you’ll be paying for it.

If there’s anything I’ve missed, any thing that needs clarification, or anybody that has better ideas feel free to let me know.



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here