I would say you're far, far too ambitious. Software like this is massive.
Teams of programmers work for years to produce it and still get it wrong.
You wouldn't have a prayer at producing anything significant. The UK
National Health Service is currently in a shouting match with its software
suppliers over a mult-million pound project to do just what you describe.
I can't suggest what you *should* consider because I don't know what your
institution expects, but I can say that whatever interests you, you should
spend some time writing up scenarios and use cases in order to get an idea
of what you might achieve. Even writing the appointments schedule for what
you talk about below would be too much for an undergraduate project, IMHO.
You would need to hold details of patients, their clinical details and their
allocation details (allocation to a doctor). Then you would need
practitioner details and you would need to check that patients are only
allocated to practitioners with the relevant skills/knowledge for the
patient illnesses. Then you would need practitioner schedules (when they
will be available) and you will have to provide routines for allocating
appointments, changing them and deleting them, creating follow-ups,
reallocating an appointment to another practitioner if an allocated
practioner becomes unavailable (holidays/sickness...) etc etc. You would
need pages/screens to add/update/delete all these details, as well as code
to apply business rules and to talk to your database.
Has your institution provided you with example projects from previous years?
Is so, you should study those very carefully to get some idea of the scope
and depth required.
My experience says that you are better off choosing a discreet project that
you can pursue in depth. For example, I have an interest in Library
software. Projects I would consider would be things like software to read
MARC records into a bibliographic database, or a set of C# classes for a
Z39.50 client (and perhaps a server) derived from the ASN.1 specification.
But YMMV.
You don't need to worry about databases, BTW. There are plenty of industry
grade databases you can use with .NET (e.g. MySQL).
HTH
Peter
<an**********@rediffmail.comwrote in message
news:11**********************@q69g2000hsb.googlegr oups.com...
Hi Nicholas,
Thanks for your reply,
I was planning to create a complete software for Hospital. Which
includes many modules like registeration, appointment schedullng,
blood bank, patients record etc etc. For this application i would be
needing heave database. To keep the record of all the patients and etc
etc.
But i am now confused like some one said for this type of application
it is better to use ASP.net with C#.Net and SQL server 2005. As it
could be used via internet(if wanna use gloabally) or just intranet(if
want to use it locally within hospital premises.)
And then some one said you could do this application without ASP.net
by simply creating tables in SQL and connecting it with your C# code.
So what do you suggest, what should i do in this case. Should i pick
up ASP book and get myself through it or should i first just stick to
C#.NET.....
Thanks