You are on page 1of 2

Abstract

When a Computer Software succeeds-when it meets the needs of the people who use it, when it performs flawlessly over along period of time, when it is easy to modify and even easier to use-it can and does change things for the better. But when software fails-when its users are dissatisfied, when it is error prone, when it is difficult to change and even harder to use-bad things can and do happen. We all want to build software that makes things better, avoiding the bad things that lurk in the shadow of failed efforts. To succeed we need discipline when software is designed and built. Many individuals and companies still develop software haphazardly, even as they build systems to service the most advanced technologies of the day. As a result, the quality of the software that we produce suffers and bad things happen. This project report is intended to serve as a guide to the software developed on HEALTHCARE. I have tried to follow the principles and rules as suggested by the software engineers as far as possible, in order to make this software a successful one. The report starts with a comprehensive introduction to the project undertaken as its very First Section. It includes objectives and scope of the project; about the front-end tool used i.e. ASP.Net with C# and the back-end tool i.e. SQL Server. The second part presents and discusses the theoretical background of the project. The third section encompasses all the problems of the software that includes what is expected from the software, the demands and the requirements of the end-users. The fourth part is the System analysis and design section. This part focuses on requirements analysis and specification, analysis issues, detailed procedures and the database designs. In The fifth section, different approaches to formal evaluation and review techniques are explored. The sixth section highlights the methodology adopted for this project. The seventh part suggests the steps required to implement the software on the user machine. The eighth part discusses the hardware and software requirements of the user machines. The ninth part deals with the cost benefit analysis. The tenth section contains the data flow diagrams. The next section is the flowchart part. The next section is for the entity relationship diagram of the project. The thirteenth part explains the methodology used for testing. The fourteenth section is the test report. The fifteenth part is the most important part of the project i.e. the code for the software. ix

The sixteenth part is the user manual section. The seventeenth part is the annexure for the topic that includes some details about the organization, the data dictionary, definitions, acronyms and abbreviations used in the report. The final section is the reference part that contains a list of the books and reports that were referred during the development of the project and the report as well. The emphasis in this report is to document the important concepts and techniques used for the successful development of this project. I do hope fervently that, through this report, the readers will get a real picture of what the project is all about. I also wish that may this software satisfies all the needs and requirements of the organization, for which it is meant.