Medi Tracker (1)

ACKNOWLEDGMENT

My express thanks and gratitude and thanks to Almighty God, my parents and other family members and friends without whose uncontained support, I could not have made this career in MASTER OF COMPUTER

APPLICATIONS.

I wish to place on my record my deep sense of gratitude to my project guide, Mr. SRINIVASA REDDY, SANDSYS TECHNOLOGIES, Hyderabad for his constant motivation and valuable help through the project work.Express my gratitude to Mrs. K.RAJINIDEVI, HEAD

OF THE DEPARTMENT, SIDDHARTH INSTITUTE OF P.G. STUDIES for his valuable suggestions and advices throughout the M.C.A. course. I also extend my thanks to other Faculties for their Cooperation during my Course.

Finally, I would like to thank one and all for their cooperation to complete this project.

SOPRALA SWAPNA

MEDITRACKING Y8MC93051

DECLARATION

I, the student of Siddharth Institute of P.G. Studies

hereby declare that this work entitled MEDITRACKER

being submitted to the Department of MCA,SIPS affiliated

to Acharya Nagarjuna University for the award of

MASTER OF COMPUTER APPLICATIONS, is a record of

bonafied work done by me.

SOPRALA SWAPNA

SIDDHARTH INSTITUTE OF P.G. STUDIES 2


CONTENTS

1. INTRODUCTION• INTRODUCTION TO PROJECT• ORGANIZATION PROFILE• PURPOSE OF THE PROJECT• PROBLEM IN EXISTNG SYSTEM• SOLUTION FOR THESE PROBLEMS

2. SYSTEM ANALYSIS• INTRODUCTION• PROPOSED SYSTEM• HARDWARE & SOFTWARE REQUIREMENT

3. FEASIBILITY REPORT• TECHNICAL FEASIBILITY• OPERATIONAL FEASIBILITY• ECONOMIC FEASIBILITY

4. MODULES

5. SOFTWARE REQUIREMENT SPECIFICATION• FUNCTIONAL REQUIREMENTS• PERFORMANCE REQUIREMENTS

6. SYSTEM DESIGN• INTRODUCTION• SYSTEM WORKFLOW• NORMALIZATION• E-R DIAGRAM• DATA FLOW DIAGRAMS • DATA DICTIONARY



• UML DIAGRAMS

7. OUTPUT SCREENS

8. SYSTEM TESTING AND IMPLEMENTATION

• INTRODUCTION• STRATEGIC APPROACH OF SOFTWARE TESTING• UNIT TESTING• TEST

9. SYSTEM SECURITY

• INTRODUCTION• SECURITY IN SOFTWARE

10. CONCLUSION

11. BIBLIOGRAPHY



CHAPTER 1



INTRODUCTION TO PROJECT:

Every hospital needs an online system where by it can accommodate the patients comfortably and avoid any confusion to the doctors regarding their work. There should be a system where the patients are categorized under insurance policy and non policy holders and the system helps the hospital management to claim the bills from concerned insurance companies. All these needs and much more are fulfilled in MediTracker.

MediTracker is useful to record patient’s details along with the compliant. It also records the inpatient details and outpatient details and arranges the appointment of doctors. MediTracker also provides the management reports like schedules, appointments of doctors, inpatients, insurances and discharges. And also used to generate bills dynamically for the discharged patients etc.

The administrative user can create new users and change their passwords. He can add the doctor’s information as well as new doctor’s details. He can add information related to inpatients, outpatients, rooms availability, billing and insurance information. The administrator can view the management reports.The doctors can change their own passwords. He can view his own appointments and information of inpatients and outpatients for any day. Manager is another person who manages the activities in the hospital. He can add a new doctor to the list. He can also add new room information. He



can view the information of doctors, rooms and patients.An accountant can add the information related to patient insurances and view all the reports. He can view the details of inpatients, outpatients and discharged patient’s information. He also collects the bill amount from the patient and enters it into the

system. MediTracker thus ensures smooth operation of the hospital management tasks as well as offering facility to the patients.

Technologies Used :

J2SE SETVLETS JSP JDBC JAVASCRIPT



ORGANIZATION PROFILE

About Us

SANDSYS TECHNOLOGIESis a technology based company that operates to explore different technologies and services which help people and companies by addressing their problems and challenges by realizing their possibilities, aspirations to accomplish their dreams. We apply new thinking and ideas to create simple, valuable methodologies by finding simpler ways that endeavor high potential and innovative works.

Accessible Technology:

A valuable resource for students:

A greater number of students are now learning with the help of computers. Considering these trends, it is of the utmost importance that all students have equal access to the educational opportunities that computer technology provides and we concentrate to give Real time projects to students to know subject at professional level.

Methodology:

For any organization a transition to new technology or new processes can be ineffective if it lacks one key element: education. Education ensures that the people involved understand their new role and leads them successfully to the adoption of the new tools and procedures. Our institute uses a learner-centric,



competency-based teaching methodology, or teaching focuses on learning tasks which an individual can handle complex issues. Our workshops are designed for talents transformation and individual personality development.

SANDSYS TECHNOLOGIES IT Training

Certified instructors utilize their own development, deployment, and support experience to teach students in both onsite and offsite environments.

SANDSYS TECHNOLOGIES prides itself on our flexibility; we will gladly customize our IT training solutions to meet your needs. Our instructors provide public classes taught at our state-of-the-art training as well as private classes taught at the corporate location or third-party facility of your choice.

SANDSYS TECHNOLOGIES has tailored the training solutions for Small and medium sized Software Development companies and as well as clients who has their own IT Staff. Vision:

Our vision is to foster prosperity through technology by means of education, innovation and emerges a world class professional development and placement centre.

Mission

Our mission is to impart high quality training to students and promote comprehensive professional development program through cutting edge topics.

Corporate Training



Our training offers the most comprehensive session catering to the industry’s calendar and adhoc requirements. Our training faculty is lead by senior members from the IT industry we provide quality training through presentation slides and interactive sessions.

Integrated Learning

SANDSYS TECHNOLOGIES Education Services offers a variety of high-quality courses to choose from. Choose your interest and view the curriculum path that is right for you. When you start browsing our technical training you will find that we provide a variety of training options.

Training Courses:

.NET Java Software Testing PHP

Timings of Classes

All classes at SANDSYS TECHNOLOGIES facility begin at 7:00 AM and typically conclude around 8:30 PM depending on the course and class size.

Any other queries feel free to call us or go through our website:Address:

SANDSYS TECHNOLOGIES, GREEN HOUSE, 3rd floor,NEAR ADITYA TRADE CENTER,AMEERPET,Hyderabad.India.Email: [email protected]

PROBLEM STATEMENT SIDDHARTH INSTITUTE OF P.G. STUDIES 10

mailto:[email protected]


Problem statement is one of the basic and important phases of project phase. When the basic problem is determined, it is documented and the symptomatic problem is analyzed, then the current list of basic problem is completed. A system is simply a set of components that interact to accomplish some purpose.

MediTracker is an online software application which fulfills the requirement of a typical management of details of doctors, inpatients, outpatients and rooms in a Hospital. It provides the interface to users in a graphical way to manage the daily transactions as well as historical data. Also provides the management reports like schedules, appointments of doctors and inpatients, insurances and discharges etc.

The aim of this application is to reduce the manual effort needed to manage transactions and historical data used in a hospital. Also this application provides an interface to users to view the details like the schedules, appointments of doctors and discharge of inpatients etc.

Current system is a manual one in which users are maintaining ledgers, books etc to store the information like Inpatient’s details, outpatient’s details, appointments of doctors etc.. It is very difficult to maintain historical data.

This project is developed using Java Programming Language under Windows.



CHAPTER 2



INTRODUCTION:

System Analysis is first stage according to System Development Life Cycle model. This System Analysis is a process that starts with the analyst.

Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. One aspect of analysis is defining the boundaries of the system and determining whether or not a candidate system should consider other related systems. During analysis, data are collected on the available files, decision points, and transactions handled by the present system.

Logical system models and tool are used in analysis. Training, experience, and common sense are required for collection of the information needed to do the analysis.

CURRENT SYSTEM:

Current system is a manual one in which users are maintaining books to store the information like Patients details, Doctors details, Available rooms and insurance facilities, as well as employee details. It is very difficult to maintain historical data. Also regular investments need to purchase stationary every year.

Disadvantages:

The following are the disadvantages of current system1. It is difficult to maintain important information in books2. More manual hours need to generate required reports



3. It is tedious to manage historical data which needs much space to keep all the previous year’s ledgers, books etc

4. Daily admissions of patients are to be entering into different books immediately to avoid conflicts which are very difficult.

PROPOSED SYSTEM:

Proposed system is a software application which avoids more manual hours that need to spend in record keeping and generating reports. This application keeps the data in a centralized way which is available to all the users simultaneously. It is very easy to manage historical data in database. No specific training is required for the employees to use this application. They can easily use the tool that decreases manual hours spending for normal things and hence increases the performance. As the data is centralized it is very easy to fix an appointment of doctor with a patient immediately.

Advantages:

The following are the advantages of proposed system

1. Easy to manage all the daily admissions of patients and appointments of doctors.

2. Can generate required reports easily3. Easy to manage historical data in a secure manner4. Centralized database helps in avoiding conflicts5. Easy to use GUI that does not requires specific training.



REQURIEMENTS ANALYSIS

The requirement phase basically consists of three activities: Requirement Analysis Requirement Specification Requirement Validation

Requirement Analysis:

Requirement Analysis is a software engineering task that bridges the gap between system level software allocation and software design. It provides the system engineer to specify software function and performance, indicate software’s interface with the other system elements and establish constraints that software must meet.

The basic aim of this stage is to obtain a clear picture of the needs and requirements of the end-user and also the organization. Analysis involves interaction between the clients and the analysis. Usually analysts research a problem by asking questions and reading existing documents. The analysts have to uncover the real needs of the user even if they don’t know them clearly. During analysis it is essential that a complete and consistent set of specifications emerge for the system. Here it is essential to resolve the contradictions that could emerge from information got from various parties. This is essential to ensure that the final specifications are consistent.



It may be divided into 5 areas of effort. Problem recognition Evaluation and synthesis Modeling Specification Review

Each Requirement analysis method has a unique point of view. However all analysis methods are related by a set of operational principles.

They are

The information domain of the problem must be represented and understood.

The functions that the software is to perform must be defined.

The behavior of the software as a consequence of external events must be defined.

The models that depict information, function and behavior must be partitioned in a hierarchical or layered fashion.

The analysis process must move from essential information to Implementation detail

Requirement Analysis in this Project SIDDHARTH INSTITUTE OF P.G. STUDIES 16


The main aim in this stage is to assess what kind of a system would be suitable for a problem and how to build it. The requirements of this system can be defined by going through the existing system and its problems. They discussing (speak) about the new system to be built and their expectations from it. The steps involved would be

Problem Recognition:

The main problem is here while taking the appointments for the Doctors. If we want to verify the old data or historical data it is very difficult to findout. Maintain the data related to all departments is very difficult.

Evaluation and Synthesis:

In the proposed system this application saves the lot of time, and it is time saving process when we use this application. Using this application we can easy to manage daily treatments and easy to maintain the historical data. No specific training is required for the employees to use this application. They can easily use the tool that decreases manual hours spending for normal things and hence increases the performance.

REQUIREMENTS SPECIFICATION



Specification Principles:

Software Requirements Specification plays an important role in creating quality software solutions. Specification is basically a representation process. Requirements are represented in a manner that ultimately leads to successful software implementation.

Requirements may be specified in a variety of ways. However there are some guidelines worth following: -

Representation format and content should be relevant to the problem

Information contained within the specification should be nested

Diagrams and other notational forms should be restricted in number and consistent in use.

Representations should be revisable.

Software Requirements Specifications:

The software requirements specification is produced at the culmination of the analysis task. The function and performance allocated to the software as a part of system engineering are refined by establishing a complete information description, a detailed functional and behavioral description, and indication of performance requirements and design constraints, appropriate validation criteria and other data pertinent to requirements.

HARDWARE AND SOFTWAREREQUIREMENTS



Hard ware Specification:

Processor : Intel P-IV based system

Processor Speed : 2.0. GHz

RAM : 256 MB to 512 MB

Hard Disk : 40GB to 80GB

Key Board : 104 keys

Software Specification:

Database : MySQL 5.0, MySQL 3.5 JDBC driver

Server : Apache Tomcat 4.1

Front end : JSP / Servlets, J2SDK 1.4, HTML,DHTML,

Java Script

Editor : Edit plus



CHAPTER 3



FEASIBILITY STUDY

All projects are feasible given unlimited resources and infinite time. But the development of software is plagued by the scarcity of resources and difficult delivery rates. It is both necessary and prudent to evaluate the feasibility of a project at the earliest possible time.

Three key considerations are involved in the feasibility analysis.

Economic Feasibility:

This procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. Otherwise, further justification or alterations in proposed system will have to be made if it is to have a chance of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle.

Technical Feasibility:

Technical feasibility centers on the existing computer system (hardware, software, etc.,) and to what extent it can support the proposed addition. If the budget is a serious constraint, then the project is judged not feasible.



Operational Feasibility:

People are inherently resistant to change, and computers have been known to facilitate change. It is understandable that the introduction of a candidate system requires special effort to educate, sell, and train the staff on new ways of conducting business.

FEASIBILITY STUDY IN THIS PROJECT

1. Technical feasibility:

The system is self-explanatory and does not need any extra sophisticated training. As the system has been built by concentrating on the Graphical User Interface Concepts, the application can also be handled very easily with a novice User. The overall time that is required to train the users upon the system is less than half an hour.

The System has been added with features of menu-driven and button interaction methods, which makes the user the master as he starts working through the environment. The net time the customer should concentrate is on the installation time.

2. Financial Feasibility:

i) Time Based:

Contrast to the manual system management can generate any report just by single click. In manual system



it is too difficult to maintain historical data which become easier in this system. Time consumed to add new records or to view the reports is very less compared to manual system. So this project is feasible in this point of view

ii)Cost Based:

No special investment need to manage the tool. No specific training is required for employees to use the tool. Investment requires only once at the time of installation. The software used in this project is freeware so the cost of developing the tool is minimal and hence the overall cost.



CHAPTER 4



The most creative and challenging phase of the life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to the technical specifications that will be applied in implementations the candidate system. The design may be defined as “the process of applying various techniques and principles for the purpose of defining a device, a process or a system in sufficient details to permit its physical realization”.

The designer’s goal is how the output is to be produced and in what format samples of the output and input are also presented. Second input data and database files have to be designed to meet the requirements of the proposed output. The processing phases are handled through the program Construction and Testing. Finally, details related to justification of the system and an estimate of the impact of the candidate system on the user and the organization are documented and evaluated by management as a step toward implementation.

The importance of software design can be stated in a single word “Quality”. Design provides us with representations of software that can be assessed for quality. Design is the only way that we can accurately translate a customer’s requirements into a finished software product or system without design we risk building an unstable system, that might fail it small changes are made or may be difficult to test, or one who’s quality can’t be tested. So it is an essential phase in the development of a software product.



APPLICATION DESIGN

USERS:

The major functionality of this product is divided into four categories.

1. Administrative User Functions. 2. Doctors Functions. 3. Mangers Functions. 4. Accountants Functions.

In this application each and every user must having their own User ID and Password, using these User ID and Password only they can directly enter into their corresponding Login forms.

After enter into their Login forms each user will interact with the following functionalities.But according to their responsibilities only they will use the above functionalities.1) Administrative User Functions:

In this functionality the administrator will do his own responsibilities. Whenever he needs to change the Password, then he can directly change it. If any reason he needs to add a new user he can directly add. He can view how many doctors has already existed in hospital, their details means how much money they have to charge per hour, the doctor’s designation, Working hours, and their experience all these details he can view. If the admin user can add a new doctor in hospital, The admin user can view the details of all the patients already existed, their nature of illness, guardian’s



details, either he has admitted as an inpatient or outpatient all these details he can view and he can directly add a patient. The admin user can provide the appointments for the patients or charities. For patients, which doctor they have to prefer, his charges, working hours, all these details he can provide to patients. He can view the appointment details of all the doctors. He can view the details of all types of rooms and he can allot the new rooms for the Inpatients. The admin user can view the details of all the patient’s discharges and he can make the discharges. He can view the details of all the insurance claims and he can add a new insurance claim. The admin user can view the details of all the users and he can add a new user. He can view or generate all the management reports.

2) Doctors Functions:

In this function, the Doctor can enter into his functionality using his own User ID and Password. After entering into his functionality, whenever he needs to change his password then he can directly change it. The Doctor can view the details of all the doctors available in hospital, but he can’t add the doctors. In the same way he can view the details of all the patients but he can’t add the patients details in the register. The Doctor user can allot the appointments for his own and he can view the details of all the doctor’s appointments and his personal appointments. He can view the details of all types of rooms available in the hospital. He can view the details of discharges. He can view the details of insurance claims.



3) Managers Functions:

In this function, the Manager can enter into his functionality using his own User ID and Password. After entering into his functionality, whenever he needs to change his password then he can directly change it. The Manager can view the details of all the users, means how much money they have to charge per hour, their experience, working hours all these details he can view and if any reason he needs another doctor to work in the hospital he can add the new doctor. He can view the details of all the patients. He can monitor the appointment details of all the doctors. He can allot the rooms for the patients and he can view the details of all types of rooms. The Manager can view the details of patient discharges. He can view the details of all insurance claims. He can view or generate all types of reports.

4) Accountants Functions:In this function, the Accountants can enter into his

functionality using his own User ID and Password. After entering into his functionality, whenever he needs to change his password then he can directly change it. He can view the details of all the patients. He can view the details of patient discharges. He can view the details of all the insurance claims and he can make the insurance claims for the patients. He can view all types of management reports.

MODULES: The System after careful analysis has been identified to present with the following modules.

1. EMPLOYEE INFORMATION & DOCTORS MODULE: SIDDHARTH INSTITUTE OF P.G. STUDIES 28


This module maintains all the information, which belongs to the employees who are working with the Hospital. This module maintains the details all the four types of users. This module separately maintains the information of different departments. This can be maintaining Admin, Manager, Doctors, and Accountants. All the employees’ details are recorded to database and can be viewed as a report.

This module maintains all the information of doctors in the hospital. All the doctors’ details are recorded to database and can be viewed as a report that displays the schedules of doctors. The admin user, manager, and doctor can view the details of all the doctors. Each and every doctor can have their own personal identification numbers. Any one of the above mentioned users can view the doctors details like, Identification number of the doctor, name, date of joining in that hospital, personal contact number, doctor’s designation or specialization, experience as a doctor, working days, holiday in that week, how much money the doctor has been charging per hour or per day, these details are placed inside the doctors list. This list is available only for the above mentioned doctors. The user wants the details in sequencing order, he can just click on any of the field that is showing in the doctor’s list then it will be automatically displayed in sorting order. If the user wants print out of the doctor’s list then he can collect the print out just clicking on the print option that is showing on the screen.

2. PATIENTS & APPOINTMENTS MODULE: SIDDHARTH INSTITUTE OF P.G. STUDIES 29


This module deals with major and crucial part which includes information of patients admitted either as inpatient or as outpatient This module provides interface to add the Patients details and can be viewed as a report that displays all the information about the inpatients and outpatients in the hospital. If the patient needs to join in the hospital as inpatient, then the user just go through the option “Admission as” which is available in the new patient’s admission form. If the user selects the patient as an inpatient then he should give the details of insurance. If he is working in any organization then he can directly claim the insurance, otherwise he should give the details of any of his relatives details as a guardian. Then the insurance claiming will be processed with the name of his guardian. All the users means Admin, Manager, Doctor and Accountant can view the full details of all the users, which are joined in the hospital, but only Admin User can add the patient’s details. The Patients module displays all the details of the patient including Patient ID, Patient Name, contact no, Occupation, Nature of Illness, admission date and discharge date all these details will be displayed. This module deals with major and crucial part that includes Appointments of doctors that are either given to patients or to any charity etc. This module provides interface to add the appointments of doctors and can be viewed as a report that displays all the appointments given to patients and charities etc. Admin user, Doctor user and Manager user can view the details of all the users. Only Admin and Manager can allot the new appointments for the patients.



Whenever the user click on the field “view appointments”, it will display the doctor’s details, either the doctor given the appointment to patient or charity these details it will be displayed. The total appointments information will be placed inside the database.

2. ROOMS MODULE: This module deals with major and crucial part that includes the details of available rooms in the hospital for inpatients. This module provides interface to add the rooms and can be viewed as a report that displays all the empty rooms and reserved rooms and it can also shows the different types of rooms available in the hospital. Basically some categories of rooms are available in the hospital. Whenever the patient admits in the hospital, the admin user or the manager will fill the admission form of the patient. If the patient wants to join as an inpatient then it will display availability of the rooms in some categories. According to the availability, the patient can chose the room. Rooms description, Visiting hours for the patient’s relatives this type of information will be displayed in the rooms list. Only admin user and the manager can view details of all rooms, rooms availability information, and they can allot the new rooms for the patients.

3. DISCHARGES & INSURANCE MODULE: This module deals with major and crucial part that includes discharges of inpatients and updates the rooms’ status as empty after discharge of the patient. This module provides interface to discharge a patient and can be viewed as a report that displays all the discharges of patients done in the



hospital. Every patients information will be placed inside the database. When the time of discharge the concern user will check out the details of corresponding patient. Whenever the user wants to check the patient’s details, the discharges module will display the details like, date of joining, date of discharge, consultant doctor, referred by doctor, and insurance claiming all these details will be displayed. All the four types of users can view the details of the discharges in any time, but only admin user can make the discharges. Any of the users can collect the information about the discharges. This module deals with major part which includes Insurances of patients which are admitted as inpatients. This module provides interface to add the details of insured patients and can be viewed as a report that displays all the details of inpatients who are insured. First of all this module will checks whether the patient wants the insurance claiming or not. If the patient wants the insurance claiming, then it will check the patient is working in any organization or not. If the patient is working in any organization only the insurance claiming will processed on the name of the patient, if at all he is not working in any organization, then he should provide the details of any other working person in his family. Then that time only the insurance processings will be transferred into his guardian’s account. The processing will be be processed based on the patient’s bill details. 4. ADMINISTRATOR MODULE:

This module is used to maintain the details of users of the project



Users are divided into four categories.

A. Admin B. Doctors C. ManagersD. Accountants

All the four types of users details will be displayed in this module. Only the administrator can have wrights to add or delete the users from the users list. If at all the administrator wants to add one more user, then he can add. Remaining users can’t do this type works. All the admin user works, features all these information will be provided in this module. The works and features of the doctors, managers and accountants will be displayed in this module. All the four user’s can view the total reports in this application.

5. REPORTING MODULE:

This module used to provide reports required by the higher management. To generate dynamic reports like Schedules of Doctors, information about the inpatients and outpatients, Appointments of the doctors given to charities and patients, details of insured inpatients and discharges of inpatients done in the hospital.The Reports module having the following information.

Doctors Appointments Discharges Inpatients



Generate Bill Insurance

If at all the patient or other user’s wants to check the doctors list, then they can check out the details of the doctors, his designation, experience using the Reporting module.All information about the doctors appointments, patient discharges, Inpatients details, generating bills and insurance claiming, all these information will be displayed with the help of Reports module.



CHAPTER 5



The software, Site Explorer is designed for management of web sites from a remote location.

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

Developing the system, which meets the SRS and solving all the requirements of the system?

Demonstrating the system and installing the system at client's location after the acceptance testing is successful.

Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.

Conducting any user training that might be needed for using the system.

Maintaining the system for a period of one year after installation.



FUNCTIONAL REQUIREMENTS:

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of the results for later consultation. The various types of outputs in general are:

External Outputs, whose destination is outside the organization.

Internal Outputs whose destination is within organization and they are the

User’s main interface with the computer. Operational outputs whose use is purely

within the computer department.Interface outputs, which involve the user in communicating directly

OUTPUT DEFINITIONThe outputs should be defined in terms of the following points:

Type of the output Content of the output Format of the output Location of the output Frequency of the output Volume of the output Sequence of the output



It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.

For Example Will decimal points need to be inserted Should leading zeros be suppressed.

Output Media:

In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:

<

The suitability for the device to the particular application. The need for a hard copy. The response time required. The location of the users The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:

The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies.

INPUT DESIGN



Input design is a part of overall system design. The main objective during the input design is as given below:

To produce a cost-effective method of input. To achieve the highest possible level of accuracy. To ensure that the input is acceptable and understood by the user.

INPUT STAGES:The main input stages can be listed as below: Data recording Data transcription Data conversion Data verification Data control Data transmission Data validation Data correction

INPUT TYPES:It is necessary to determine the various types of inputs. Inputs can be categorized as follows:

External inputs, which are prime inputs for the system.

Internal inputs, which are user communications with the system.

Operational, which are computer department’s communications to the system?

Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:



At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given Type of input Flexibility of format Speed Accuracy Verification methods Rejection rates Ease of correction Storage and handling requirements Security Easy to use Portability

Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive.

As Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device.

ERROR AVOIDANCEAt this stage care is to be taken to ensure that input

data remains accurate form the stage at which it is recorded upto the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled.

ERROR DETECTION



Even though every effort is make to avoid the occurrence of errors, still a small proportion of errors is always likely to occur, these types of errors can be discovered by using validations to check the input data.

DATA VALIDATIONProcedures are designed to detect errors in data at a

lower level of detail. Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors. The system will not accept invalid data. Whenever an invalid data is keyed in, the system immediately prompts the user and the user has to again key in the data and the system will accept the data only if the data is correct. Validations have been included where necessary.The system is designed to be a user friendly one. In other words the system has been designed to communicate effectively with the user. The system has been designed with popup menus.USER INTERFACE DESIGNIt is essential to consult the system users and discuss their needs while designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

1. User initiated interface the user is in charge, controlling the progress of the user/computer dialogue. In the computer-initiated interface, the computer selects the next stage in the interaction.

2. Computer initiated interfaces



In the computer initiated interfaces the computer guides the progress of the user/computer dialogue. Information

is displayed and the user response of the computer takes action or displays further information.

USER_INITIATED INTERGFACES

User initiated interfaces fall into tow approximate classes:1. Command driven interfaces: In this type of interface

the user inputs commands or queries which are interpreted by the computer.

2. Forms oriented interface: The user calls up an image of the form to his/her screen and fills in the form. The forms oriented interface is chosen because it is the best choice.

COMPUTER-INITIATED INTERFACES

The following computer – initiated interfaces were used: The menu system for the user is presented with a list

of alternatives and the user chooses one; of alternatives.

Questions – answer type dialog system where the computer asks question and takes action based on the basis of the users reply.

Right from the start the system is going to be menu driven, the opening menu displays the available options. Choosing one option gives another popup menu with more



options. In this way every option leads the users to data entry form where the user can key in the data.

ERROR MESSAGE DESIGN:

The design of error messages is an important part of the user interface design. As user is bound to commit some errors or other while designing a system the system should be designed to be helpful by providing the user with information regarding the error he/she has committed.This application must be able to produce output at different modules for different inputs.

PERFORMANCE REQUIREMENTS Performance is measured in terms of the output

provided by the application.

Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.



The requirement specification for any system can be broadly stated as given below:

The system should be able to interface with the existing system

The system should be accurate The system should be better than the existing

system

The existing system is completely dependent on the user to perform all the duties.



CHAPTER 6



INTRODUCTIONSoftware design sits at the technical kernel of the

software engineering process and is applied regardless of the development paradigm and area of application. Design is the first step in the development phase for any engineered product or system. The designer’s goal is to produce a model or representation of an entity that will later be built. Beginning, once system requirement have been specified and analyzed, system design is the first of the three technical activities -design, code and test that is required to build and verify software.

The importance can be stated with a single word “Quality”. Design is the place where quality is fostered in software development. Design provides us with representations of software that can assess for quality. Design is the only way that we can accurately translate a customer’s view into a finished software product or system. Software design serves as a foundation for all the software engineering steps that follow. Without a strong design we risk building an unstable system – one that will be difficult to test, one whose quality cannot be assessed until the last stage.

During design, progressive refinement of data structure, program structure, and procedural details are developed reviewed and documented. System design can be viewed from either technical or project management perspective. From the technical point of view, design is



comprised of four activities – architectural design, data structure design, interface design and procedural design.

SYSTEM WORKFLOW

Change the workflow according to your project in the Admin point of view


Home.aspx

Default.aspx

Home page to login ,Enter User Id & Password

Main Page for coordinator

frmExams.aspxfrmQuestions.aspx

frmEditexams.aspx

FrmAssignExam.aspx

Allow Admin to create new exam type Enter the

Question Assign Exam to the student

Allow to Edit the Exam Questions

Allow Admin to edit the exams

Sends Key to the Student

frmEditQuestions.aspx

FrmExamReport.aspx

Report for all the Exams

frmStudentReport.aspx

Report all the students


5.3. NORMALIZATIONIt is a process of converting a relation to a standard

form. The process is used to handle the problems that can arise due to data redundancy i.e. repetition of data in the database, maintain data integrity as well as handling

problems that can arise due to insertion, updation, deletion anomalies. Decomposing is the process of splitting relations into multiple relations to eliminate anomalies and maintain anomalies and maintain data integrity. To do this we use normal forms or rules for structuring relation.

Insertion anomaly: Inability to add data to the database due to absence of other data.Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial update

Normal Forms: These are the rules for structuring relations that eliminate anomalies.

FIRST NORMAL FORM:

A relation is said to be in first normal form if the values in the relation are atomic for every attribute in the relation. By this we mean simply that no attribute value can be a set of values or, as it is sometimes expressed, a repeating group.



SECOND NORMAL FORM:

A relation is said to be in second Normal form is it is in first normal form and it should satisfy any one of the following rules.

1. Primary key is a not a composite primary key2. No non key attributes are present3. Every non key attribute is fully functionally

dependent on full set of primary key.

THIRD NORMAL FORM:A relation is said to be in third normal form if their exits no transitive dependencies.

Transitive Dependency: If two non key attributes depend on each other as well as on the primary key then they are said to be transitively dependent. The above normalization principles were applied to decompose the data in multiple tables thereby making the data to be maintained in a consistent state.

5.4. E – R DIAGRAMS

The relation upon the system is structure through a conceptual ER-Diagram, which not only specifics the existential entities but also the standard relations through which the system exists and the cardinalities that are necessary for the system state to continue.

The entity Relationship Diagram (ERD) depicts the relationship between the data objects. The ERD is the notation that is used to conduct the date modeling activity the attributes of each data object noted is



the ERD can be described resign a data object descriptions.

The set of primary components that are identified by the ERD are

Data object Relationships Attributes Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.



DATA FLOW DIAGRAMS

A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component in a DFD is labeled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of DFD’S is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD.

The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate



amount of detail is described for analyst to understand the process.

Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to the modular design.

A DFD is also known as a “bubble Chart” has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system.

DFD SYMBOLS:In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data

2. An arrow identifies data flow. It is the pipeline through which the information flows

3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows.

4. An open rectangle is a data store, data at rest or a temporary repository of data

Process that transforms data flow.

Source or Destination of data



Data flow

Data Store

CONSTRUCTING A DFD:Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy reference. Each name should be representative of the process.

2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source.

One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal.

3. When a process is exploded into lower level details, they are numbered.

4. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized

A DFD typically shows the minimum contents of data store. Each data store should contain all the data elements that flow in and out.



Questionnaires should contain all the data elements that flow in and out. Missing interfaces redundancies and like is then accounted for often through interviews.

SAILENT FEATURES OF DFD’S1. The DFD shows flow of data, not of control loops and

decision are controlled considerations do not appear on a DFD.

2. The DFD does not indicate the time factor involved in any process whether the dataflow take place daily, weekly, monthly or yearly.

3. The sequence of events is not brought out on the DFD.

TYPES OF DATA FLOW DIAGRAMS Current Physical Current Logical New Logical New Physical

CURRENT PHYSICAL:In Current Physical DFD proecess label include the

name of people or their positions or the names of computer systems that might provide some of the overall system-processing label includes an identification of the technology used to process the data. Similarly data flows and data stores are often labels with the names of the

actual physical media on which data are stored such as file folders, computer files, business forms or computer tapes.

CURRENT LOGICAL:



The physical aspects at the system are removed as mush as possible so that the current system is reduced to its essence to the data and the processors that transforms them regardless of actual physical form.

NEW LOGICAL:This is exactly like a current logical model if the user

were completely happy with he user were completely happy with the functionality of the current system but had problems with how it was implemented typically through the new logical model will differ from current logical model while having additional functions, absolute function removal and inefficient flows recognized.

NEW PHYSICAL:

The new physical represents only the physical implementation of the new system.

RULES GOVERNING THE DFD’SPROCESS

1. No process can have only outputs.2. No process can have only inputs. If an object has

only inputs than it must be a sink.3. A process has a verb phrase label.

DATA STORE1. Data cannot move directly from one data store to

another data store, a process must move data.



2. Data cannot move directly from an outside source to a data store, a process, which receives, must move

data from the source and place the data into data store

3. A data store has a noun phrase label.

SOURCE OR SINK

The origin and /or destination of data

1. Data cannot move direly from a source to sink it must be moved by a process

2. A source and /or sink has a noun phrase land

DATA FLOW1. A Data Flow has only one direction of flow between

symbols. It may flow in both directions between a process and a data store to show a read before an update. The later is usually indicated however by two separate arrows since these happen at different type.

2. A join in DFD means that exactly the same data comes from any of two or more different processes data store or sink to a common location.

3. A data flow cannot go directly back to the same process it leads. There must be at least one other process that handles the data flow produce some other data flow returns the original data into the beginning process.

4. A Data flow to a data store means update (delete or change).

5. A data Flow from a data store means retrieve or use.



6. A data flow has a noun phrase label more than one data flow noun phrase can appear on a single arrow as long as all of the flows on the same arrow move together as one Package.

Context Level DFD

Login DFD



Admin Activities (1st Level)



Student Register



Student Activity



DATA DICTIONARY

The logical characteristics of current systems data stores, including name, description, aliases, contents, and organization. Identifies processes where the data are used and where immediate access to information needed. Serves as the basis for identifying database requirements during system design.

Uses of Data Dictionary:

To manage the detail in large systems To communicate a common meaning for all system

elements To Document the features of the system

To facilitate analysis of the details in order to evaluate characteristics and determine where system changes should be made.

To locate errors and omissions in the systems



TABLESTABLE NAME:

Appointmentsmaster, it contains details the of all the appointments. The following table explains all the fields.

Field Name Data Type SizeAPPOINTMENT ID INT 11DOCTOR NAME VARCHAR 50DOCTOR ID INT 10DESIGNATION VARCHAR 50APPOINTMENT GIVEN TO VARCHAR 50PATIENT ID INT 10NAME OF PATIENT VARCHAR 50NAME OF CHARITY VARCHAR 50DATE OF APPOINTMENT DATENO OF HOURS INT 10

TABLE NAME: Billingmaster, it contains details of all the bills. The following table explains all the fields.

Field Name Data Type SizeBILL ID INT 20NAME OF PATIENT VARCHAR 100ADMISSION FEE FLOATPERIOD OF STAY IN HOSPITAL

INT 20

ROOM ID INT 50ROOM RENT FLOATREFERED BY DOCTOR VARCHAR 200DOCTOR FEE FLOATTOTAL CHARGE FLOAT



TABLE NAME: Dischargermaster, it contains the details of discharges.The following table explains all the fields.

Field Name Data Type SizeNAME OF PATIENT VARCHAR 50PATIENT ID INT 10AGE INT 10SEX VARCHAR 10OCCUPATION VARCHAR 50NATURE OF ILLNESS VARCHAR 50DATE OF ADMISSION

DATE

DATE OF DISCHARGE

DATE

ROOM ID INT 10CONSULTANT DOCTOR

VARCHAR 50

REFERED BY DOCTOR

VARCHAR 50

INSURANCE VARCHAR 50BILL AMOUNT FLOAT



TABLE NAME: Doctorsmaster, it contains the details of doctors.The following table explains all the fields.

Field Name Data Type SizeDOCTOR NAME VARCHAR 50DOCTOR ID INT 10DATE OF JOIN DATEDESIGNATION VARCHAR 50PHONE NUMBER VARCHAR 50EXPERIENCE INT 10HOLIDAY IN WEEK

VARCHAR 50

WORKING HOURS VARCHAR 50CHARGES PER HOUR

DOUBLE

TABLE NAME:Inpatientmaster,The following table explains all the fields.

Field Name Data Type SizeNAME OF PATIENT

VARCHAR 50

NATURE OF ILLNESS

VARCHAR 50

DATE OF ADMISSION

DATE

REERED BY DOCTOR

VARCHAR 50

ROOM ID INT 10



TABLE NAME: Insurancemaster, it contains the details of insurance claiming.The following table explains all the fields.

Field Name Data Type SizeINSURANCE ID INT 10NAME OF PATIENT VARCHAR 50NAME OF APPLICANT VARCHAR 50WORKING AT COMPANY VARCHAR 50EMPLOYEE ID VARCHAR 50RELATION WITH PATIENT VARCHAR 50NATURE OF ILLNESS VARCHAR 50DATE OF ADMISSION DATEDATE OF DISCHARGE DATEPERIOD OF STAY IN HOSPITAL

VARCHAR 50

AMOUNT CLAIMED DOUBLEPLACE VARCHAR 50POLICY NUMBER VARCHAR 50CLAIM NUMBER VARCHAR 50

TABLE NAME: login, it contains the details of user id and passwords.The following table explains all the fields.

Field Name Data Type SizeUSER ID VARCHAR 50PASSWORD VARCHAR 50AUTH INT 11

TABLE NAME:



Patientsmaster, it contains the details of the patients.The following table explains all the fields.

Field Name Data Type SizeNAME OF PATIENT VARCHAR 50PATIENT ID INT 10AGE INT 10SEX VARCHAR 10OCCUPATION VARCHAR 50CONTACT NUMBERS VARCHAR 50NATURE OF ILLNESS VARCHAR 50DATE OF ADMISSION DATEADMISSIONAS VARCHAR 50INSURANCE VARCHAR 50GUARDIANNAME VARCHAR 50RELATION WITH PATIENT

VARCHAR 50

REFERED BY DOCTOR VARCHAR 50ROOM ID VARCHAR 10



TABLE NAME: Roomsmaster, it contains the details of all the rooms.The following table explains all the fields.

Field Name Data Type SizeROOM ID INT 10CATEGORY VARCHAR 50NO OF BEDS INT 50CHARGES PER DAY

DOUBLE

VISITORS ALLOWED

VARCHAR 50

VISITING HOURS

VARCHAR 50

STATUS VARCHAR 50

UNIFIED MODELING LANGUAGE



The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

User Model View

1. This view represents the system from the users perspective.

2. The analysis representation describes a usage scenario from the end-users perspective.

Structural model view

In this model the data and functionality are arrived from inside the system.

This model view models the static structures.

Behavioral Model View

It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.

Implementation Model View



In this the structural and behavioral as parts of the system are represented as they are to be built.

Environmental Model ViewIn this the structural and behavioral aspects of the environment in which the system is to be implemented are represented.UML is specifically constructed through two different domains they are

UML Analysis modeling, which focuses on the user model and structural model views of the system?

UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a user’s point of view. Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view.

Actors are external entities that interact with the system. Examples of actors include users like administrator, bank customer …etc., or another system like central database.

Use case Model



USE CASE FOR LOGIN PROCESS


SYSTEM NAME

Use case 1

Use case 2

Use case n

ActorActor



Home Page

Admin Home Page

Modify his Account

View My Account

Add Exams

Add Question

Add Question Based on Exam

Add Correct Answer to the Question

Generate Question paper key

See the Request given by the user

Assign Exam date on Student

Search

Contact US

About US

Admin



Page

Student Login

Student Home Page

View My Account

Change the Password

Request For the Exam

Receives the Test Key

Go to the Test Paper

Answer the test

View Results

Contact Us

Student


ACTIVITY DIAGRAM:

Admin Activity Diagram:





Employee Activity Diagram:



Sequence Diagram for Admin Login

Collaboration diagram for Admin Login


Home Page

Login Page

DB

Admin Home Page

: Admin

1 : Select Login()

2 : Login Button Click with empty values()

3 : Admin Enters values()

4 : If user exist()

5 : if not exist()

Home PageHome Page

Login PageLogin Page

DBDB

Admin Home PageAdmin Home Page

: Admin : Admin

1 : Select Login()1 : Select Login()

2 : Login Button Click with empty values()2 : Login Button Click with empty values()

3 : Admin Enters values()3 : Admin Enters values()

4 : If use exists()4 : If use exists()

5 : if not exist()5 : if not exist()


CHAPTER 7



ADMIN LOGIN:

Note: The above screen shows the following information.



Note: The above screen shows the following information.In the above screen shows the doctors module. In doctors

module, it will display two features. 1) view Doctors 2) New Doctor

Note: The above screen shows the following information.The above screen shows the Doctors list



Note: The above screen shows the following information.The above form shows the new doctor’s entry form.




The above screen shows the patients module.


The above screen shows the information about the appointments module.




The above screen shows the full information of all the doctors appointments.





CHAPTER 8



Software Testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding, Testing presents an interesting anomaly for the software engineer.

Testing Objectives include:

1. Testing is a process of executing a program with the intent of finding an error

2. A good test case is one that has a probability of finding an as yet undiscovered error

3. A successful test is one that uncovers an undiscovered error

Testing Principles:

All tests should be traceable to end user requirements Tests should be planned long before testing begins Testing should begin on a small scale and progress

towards testing in large Exhaustive testing is not possible To be most effective testing should be conducted by a

independent third party

TESTING STRATEGIES:

A Strategy for software testing integrates software test cases into a series of well planned steps that result in the successful construction of software. Software testing is a broader topic for what is referred to as Verification and Validation.



Verification refers to the set of activities that ensure that the software correctly implements a specific function. Validation refers he set of activities that ensure that the software that has been built is traceable to customer’s requirements

Unit Testing:

Unit testing focuses verification effort on the smallest unit of software design that is the module. Using procedural design description as a guide, important control paths are tested to uncover errors within the boundaries of the module. The unit test is normally white box testing oriented and the step can be conducted in parallel for multiple modules.

Integration Testing:

Integration testing is a systematic technique for constructing the program structure, while conducting test to uncover errors associated with the interface. The objective is to take unit tested methods and build a program structure that has been dictated by design.Top-down Integration:

Top down integrations is an incremental approach for construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main control program. Modules subordinate to the main program are incorporated in the structure either in the breath-first or depth-first manner.



Bottom-up Integration:

This method as the name suggests, begins construction and testing with atomic modules i.e., modules at the lowest level. Because the modules are integrated in the bottom up manner the processing required for the modules subordinate to a given level is always available and the need for stubs is eliminated.

Validation Testing:At the end of integration testing software is completely assembled as a package. Validation testing is the next stage, which can be defined as successful when the software functions in the manner reasonably expected by the customer. Reasonable expectations are those defined in the software requirements specifications. Information contained in those sections form a basis for validation testing approach.

System Testing:System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. Although each test has a different purpose, all work to verify that all system elements have been properly integrated to perform allocated functions.

Security Testing:Attempts to verify the protection mechanisms built into the system.

Performance Testing:This method is designed to test runtime performance of software within the context of an integrated system.



CHAPTER 9



INTRODUCTION

The protection of computer based resources that includes hardware, software, data, procedures and people against unauthorized use or natural Disaster is known as System Security.

System Security can be divided into four related issues: Security Integrity Privacy Confidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat.

DATA SECURITY is the protection of data from loss, disclosure, modification and destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate physical security and safety against external threats such as eavesdropping and wiretapping.

PRIVACY defines the rights of the user or organizations to determine what information they are willing to share with or accept from others and how the organization can be protected against unwelcome, unfair or excessive dissemination of information about it.



CONFIDENTIALITY is a special status given to sensitive information in a database to minimize the possible invasion of privacy. It is an attribute of information that characterizes its need for protection.

SECURITY IN SOFTWARE:

System security refers to various validations on data in form of checks and controls to avoid the system from failing. It is always important to ensure that only valid data is entered and only valid operations are performed on the system. The system employees two types of checks and controls:

CLIENT SIDE VALIDATIONVarious client side validations are used to ensure on the client side that only valid data is entered. Client side validation saves server time and load to handle invalid data. Some checks imposed are:

VBScript in used to ensure those required fields are filled with suitable data only. Maximum lengths of the fields of the forms are appropriately defined.

Forms cannot be submitted without filling up the mandatory data so that manual mistakes of submitting empty fields that are mandatory can be sorted out at the client side to save the server time and load.



Tab-indexes are set according to the need and taking into account the ease of user while working with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are necessary to save the system from failing and intimating the user that some invalid operation has been performed or the performed operation is restricted. Some of the server side checks imposed is:Server side constraint has been imposed to check for the validity of primary key and foreign key. A primary key value cannot be duplicated. Any attempt to duplicate the primary value results into a message intimating the user about those values through the forms using foreign key can be updated only of the existing foreign key values.User is intimating through appropriate messages about the successful operations or exceptions occurring at server side.Various Access Control Mechanisms have been built so that one user may not agitate upon another. Access permissions to various types of users are controlled according to the organizational structure. Only permitted users can log on to the system and can have access according to their category. User- name, passwords and permissions are controlled o the server side.Using server side validation, constraints on several restricted operations are imposed.



CHAPTER 10



o This System being web-based and an undertaking of Cyber Security Division, needs to be thoroughly tested to find out any security gaps.

o A console for the data centre may be made available to allow the personnel to monitor on the sites which were cleared for hosting during a particular period.

o Moreover, it is just a beginning; further the system may be utilized in various other types of auditing operation viz. Network auditing or similar process/workflow based applications...



CHAPTER 11



Oracle:

PL/SQL Programming by Scott Urman

SQL complete reference by Livion

JAVA Technologies:

JAVA Complete Reference

Java Script Programming by Yehuda Shiran

Mastering JAVA Security

JAVA2 Networking by Pistoria

JAVA Security by Scotl oaks

Head First EJB Sierra Bates

J2EE Professional by Shadab siddiqui

JAVA server pages by Larne Pekowsley

JAVA Server pages by Nick Todd

HTML:

HTML Black Book by Holzner

JDBC:

Java Database Programming with JDBC by Patel moss.

Software Engineering by Roger Pressman


Documents

Medi Tracker (1)