knobloch
asked on
C# project advice needed !!!
Hi
I need an advice and might be couple pointers regarding to C# .NET project.
I have to design insurance management system for small insurance agency.
Since I have never done financial application I need some advice how to approach this project.
Here is very broad project description
The agency has 3 branches and they want to be able access customer data from all locations. Currently they have about 10 workstation and 12 users more or less, and over 100 clients. However, they are growing and it going to be more clients at least this is what they are saying. They have 3 branches, but at this point of time project it going to be implemented only for one office. After that they want connect another two offices.
Wish list :
- user authorization : two main type of user : super user with rights to modify data and regular user only with rights to prepare reports without rights to save, or update customer data or policy data.
- preparing payment schedule for their customers
- reporting system (
- keep tracking policy expiration date
- keep tracking customer payments
- quote policy
There is one more important thing for them, when they take down payment from customer they are obligated to return money to insurance company in 25 days for individual customers and 14 for business customers.
They want to be able keep down payment money as long it is possible so they have to keep tracing these dates too. Otherwise they will be in trouble and pay some fine.
My Questions:
Should I do this as Desktop application or ASP.NET.
I’m worried about performance of ASP, the system will have to generate a lot of reports so wouldn’t be better to generate these reports on client side instead of IIS side. I could grab some data from database and process it with the client. What do you think?
I might be mistaken but in my opinion Windows Forms have more flexibility over ASP,
What about hardware for desktop application:
I have following options:
- Linux plus MySql
- Linux plus Oracle 10g
- Windows plus Oracle 10g
- Windows plus SQL2000 (it is possible but it might be too expensive configuration for this project, budget is very tight)
Thanks
I need an advice and might be couple pointers regarding to C# .NET project.
I have to design insurance management system for small insurance agency.
Since I have never done financial application I need some advice how to approach this project.
Here is very broad project description
The agency has 3 branches and they want to be able access customer data from all locations. Currently they have about 10 workstation and 12 users more or less, and over 100 clients. However, they are growing and it going to be more clients at least this is what they are saying. They have 3 branches, but at this point of time project it going to be implemented only for one office. After that they want connect another two offices.
Wish list :
- user authorization : two main type of user : super user with rights to modify data and regular user only with rights to prepare reports without rights to save, or update customer data or policy data.
- preparing payment schedule for their customers
- reporting system (
- keep tracking policy expiration date
- keep tracking customer payments
- quote policy
There is one more important thing for them, when they take down payment from customer they are obligated to return money to insurance company in 25 days for individual customers and 14 for business customers.
They want to be able keep down payment money as long it is possible so they have to keep tracing these dates too. Otherwise they will be in trouble and pay some fine.
My Questions:
Should I do this as Desktop application or ASP.NET.
I’m worried about performance of ASP, the system will have to generate a lot of reports so wouldn’t be better to generate these reports on client side instead of IIS side. I could grab some data from database and process it with the client. What do you think?
I might be mistaken but in my opinion Windows Forms have more flexibility over ASP,
What about hardware for desktop application:
I have following options:
- Linux plus MySql
- Linux plus Oracle 10g
- Windows plus Oracle 10g
- Windows plus SQL2000 (it is possible but it might be too expensive configuration for this project, budget is very tight)
Thanks
ASP and ASP.net are completely different, for the most part windows forms and ASP.net web forms use most of the same objects and most of the same code. It also depends on what reporting tool your using as well. .NET has great support for crystal reports. For example I built a asp.net application using a windows IIS server and a sql server 2000 database, I have about 30 people using it from all over the country accessing about 5000 different customers. I debated to on whether to build a windows based or a web based, and it didnt make sence for me not to build a web based. As for a database, you could go with mysql its just .net has great tools for connecting to SQL server and even oracle. I would say the best combo is asp.net, windows, and sql server. As far as performance it has been great, I have about 10 users that are using laptops with wireless cards running at 56K and the web application is very fast. Look into the web based crystal reports, its great. We put this application on our intranet and is not available to the outside. I really think intranet applications are the way to go.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm not really ASP.NET person I know how to do it in Windows Forms.
Could I run into some problem because of it?
I'm especially worried about security issue and data manipulation.
What do you think?
Could I run into some problem because of it?
I'm especially worried about security issue and data manipulation.
What do you think?
No, that is not a issue as far as ASP.NET is concerned. Even you can use AD Security, or Forms Authentication (means normal db check for the user) or Passport Authentication. ASP.NET is good in security. Try to atleast have a lookup in ASP.NET concepts so that you will get good idea before starting the project.
As far as the data manipulation is concerned, ASP cacheing will help you in reducing the db lookups unlike other languages you have to fetch anything or store anything (even the cached objects) in db. But, for example you have to display some set of rows depends on userid, what ASP.NET will do is it will cleverly show the cached page from the server. It will throw the query to DB server and it reduces the certain amout of db payload.
I believe as far as your application is concerned ASP.NET is right choice.
Cheers!!
As far as the data manipulation is concerned, ASP cacheing will help you in reducing the db lookups unlike other languages you have to fetch anything or store anything (even the cached objects) in db. But, for example you have to display some set of rows depends on userid, what ASP.NET will do is it will cleverly show the cached page from the server. It will throw the query to DB server and it reduces the certain amout of db payload.
I believe as far as your application is concerned ASP.NET is right choice.
Cheers!!
ASKER
Thanks