P. 1
IDSP Report

IDSP Report

|Views: 166|Likes:
Published by Pranav Khanna

More info:

Published by: Pranav Khanna on Nov 25, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less






  • 1.1 About NIC:
  • 2.3.1 Purpose:
  • 2.3.2 Scope:
  • 2.3.3 Objective:
  • 4.1 Introduction to System Design Development Life Cycle
  • 4.2.1 Technical Feasibility
  • 4.2.2 Operational Feasibility
  • 4.2.3 Economical Feasibility
  • 5.1 Introduction:
  • 5.2 Functional Requirements:
  • 5.3 Nonfunctional Requirements:
  • 6.1 Introduction:
  • 6.2 Structured System Analysis:
  • 6.3 Tools for Structured Analysis:
  • 7.1 Tool and Technology Used:
  • 7.2.1 Java
  • 7.2.2 Tomcat 6.0
  • 7.2.3 PostgreSQL 8.2
  • 8.1.1Logical Design
  • 8.1.2Physical Design
  • 8.2Structured Design:
  • 8.3Database Design
  • 9.2 Introduction:
  • 9.3 Types of testing:
  • 9.4 System Implementation:



UNDER THE GUIDENCE OF INTERNAL GUIDE Mr. SUBHRAJYOTI BORDOLOI Lecturer Deptt. Of Computer Application Assam Engineering College Guwahati SUBMITTED BY

EXTERNAL GUIDE J.R.D KAILAY (Sr. Technical Director) TRAINING DIVISION National Informatics Centre New Delhi


National Informatics Centre
This is to certify that Mr. Jayanta Baishya ID.N0 10039 a student of Master of Computer Application from Assam Engineering College (Gauhati University) has done his full-semester project training at Training Division , NIC, New Delhi, from 2nd July to 14th November. The project work entitled “Integrated Disease Surveillance Project” embodies the original work done by Mr. Jayanta Baishya during his above full semester project training period.

Project Guide/HOD

Head, Training Division


I, Jayanta Baishya, hereby declare that the project entitled “Integrated Disease Surveillance Project” which is being submitted in partial fulfillment of the requirements for the awards of degree of Master of computer application from the Assam Engineering College, Guwahati is an own record carried out by me under the supervision of J.R.D Kailay, Project Head and Sr. Technical Director of National Informatics Centre. The matter embodied in this project has not been submitted so far for the award of any degree or diploma.

Jayanta Baishya Assam Engineering College Gauhati University

Jayanta Baishya. This project work has been prepared as a fulfillment of the requirement for the degree of MCA to be awarded by Gauhati University. Guwahati-781013. Delhi is a excellent work carried out by Mr. This work has not been presented earlier for any other academic activity. . Assam Engineering College. I wish him all success in life. Jyotiprakash Goswami Assistant Professor In-charge. Mr. a student of Assam Engineering College. Department of Computer Application. Guwahati.ASSAM ENGINEERING COLLEGE DEPERTMENT OF COMPUTER APPLICATIONS GUWAHATI 781013 CERTIFICATE This is to certify that the project work entitled “ Integrated Disease Surveillance Project: Implementation of Form S” for NIC.

a student of Assam Engineering College. He has done this project under my supervision and guidance to the best of my knowledge. Department of Computer Application.ASSAM ENGINEERING COLLEGE DEPERTMENT OF COMPUTER APPLICATIONS GUWAHATI 781013 CERTIFICATE This is to certify that the project work entitled “ Integrated Disease Surveillance Project: Implementation of Form S” for NIC. Mr. Guwahati-781013. I wish him all success in life. This work has not been presented earlier for any other academic activity. Assam Engineering College. This project work has been prepared as a fulfillment of the requirement for the degree of MCA to be awarded by Gauhati University. Delhi is a excellent work carried out by Mr. Guwahati. Jayanta Baishya. . Subhrajyoti Bordoloi Lecturer.

and Mr J P Goswami. Training Division Group NIC. Lecturer of CA Department.No job in this world. The present line of accomplishment is not a formality but an honest word of appreciation that has exactly been felt by during my Training. I also take this opportunity to express my indebtedness to all my respected teachers and worker of Assam Engineering College for their kind consent. valuable suggestions and affectionate encouragement. I would hereby take the opportunity to express my indebtedness to people who have helped me to accomplish this task. for his constant guidance and inspiration throughout MCA. Jayanta Baishya MCA.Acknowledgements The ability to help and patience to exercise diligence and provide support is a quality admonished by very few .Delhi for providing unwavering support and the opportunity to work in this organization and also to Mr. I am immensely thankful to my internal supervisor Mr S. Bordoloi. Technical Director. Scientist of NIC for his great advice and support throughout this project. I am also wish to express my sincere gratitude and thanks to Maushumi Barooah madam for providing unwavering support throughout my MCA life. First and foremost I would like to thanks J. expert guidance. however trivial or tough cannot be accomplished without the assistance of the others. Assam Engineering College. for his incessant and perpetual cooperation and encouragement. Assam Engineering College.D Kailay (HOD/GUIDE) Sr.R. Sanjay Kumar. Assistant Professor.6th Semester Assam Engineering College .

Any system that intends to the futuristic will need to take this variability into account and cater to the differential needs of the country and will need to be decentralized and state specific. As a front end I will use three tier architecture to develop the system. Health problems of some states are predominantly due to communicable diseases while in others it is due to Non communicable diseases. .0 PostgreSQL 8. Through an effective disease surveillance program health of vulnerable populations in underdeveloped regions in India will be better understood and corrective steps will be taken to improve their conditions. which is the SYNDROMIC SURVILLANCE.0 Windows XP NIC Division Allotted: Training Division (Health Ministry of India) Module Name: Implementation of Form S (Syndromic Surveillance).ABSTRACT OF THE PROJECT Project Title: Integrated Disease Surveillance Project (IDSP) Abstract: IDSP developing task is carries by training division at NIC under the Health ministry. in those states with advanced health delivery the implementation will be to improve the functions further while in those states with poor health delivery the program will establish a basic and essential module of surveillance Equity in health delivery is one of the emphases for the government. As a project by WHO. As we know India is currently passing through epidemiological transition. In the first phase of IDSP. Tools and Technologies used: JDK 1. The program will take into account the wide geo-political and socio-economic differences in the country and tailor its implementation to levels suitable for the given region of the country. I am doing my project which is mainly based on FORM S.2 Tomcat 6. I will use Jsp/Servlet and PostgreSQL as back end. India Health Ministry implementing this surveillance project in various level. The user is a district level user and details are collected from various reporting unit. After all the syndromic data are properly submitted to the central server my next task is to generate various reports which are again based on FORM S. Reports are submitted to central server each week. Many states in India have good health delivery systems while other states are lagging far behind. In this project I am going to develop a system in which a registered user can submit all the syndromic surveillance details for a particular reporting unit.5 MyEcllipse 6.

3 System Specification Chapter 6: System Analysis 6.1 About National Informatics Centre Chapter 2: System Study 2.3 Technical Feasibility 4.4 Data Dictionary Chapter 7: System Environment 7.0 7.2 Existing System 2.3 Data Flow Diagram 6.2 Technology Used 7.2 .1 Introduction 5.2 Requirement Specification 5.1 Introduction 4.CONTENTS Chapter 1: Organizational Profile 1.4 PostgreSQL 8.3.4 Behavioral Feasibility Chapter 5: Requirement Specification 5.3 Tomcat 6.3.1 Client-Server Paradigm 7.1 Introduction 6.3.3 Objective Chapter 3: Project Description Chapter 4: Feasibility Study 4.1 Purpose 2.1 Problem Definition 2.2 Economic Feasibility 4.3 Proposed System 2.2 Tools used for system analysis 6.2 Scope 2.

2 Introduction 9.4 System Implementation Chapter 10: System Security Chapter 11: Future Enhancement Chapter 12: Conclusion Chapter 13: Project Snap Shots Appendix A: Bibliography .1 Introduction 8.3 Types of System Testing 9.3 Database Design Chapter 9: Testing and Implementation 9.Chapter 8: System Design 8.2 Structured Design 8.1 Overview 9.


1.1 About NIC: National Informatics Centre (NIC) of the Department of Information Technology is providing network backbone and e-Governance support to Central Government, State Governments, UT Administrations, Districts and other Government bodies. It offers a wide range of ICT services including Nationwide Communication Network for decentralized planning, improvement in Government services and wider transparency of national and local Governments. NIC assists in implementing Information Technology Projects, in close collaboration with Central and State Governments, in the areas of (a) Centrally sponsored schemes and Central sector schemes, (b) State sector and State sponsored projects, and (c) District Administration sponsored projects. NIC endeavors to ensure that the latest technology in all areas of IT is available to its users. NIC Headquarters is based in New Delhi. At NIC Headquarters, a large number of Application Divisions exist which provide total Informatics Support to the Ministries and Departments of the Central Government. NIC computer cells are located in almost all the Ministry Bhawans of the Central Government and Apex Offices including the Prime Minister’s Office, the Rashtrapati Bhawan and the Parliament House. Apart from this, NIC has various Resource Divisions at the Headquarters, which specialize into different areas of IT and facilitate the Application Divisions as well as other NIC Centres in providing state-of-the-art services to the Govt. At the State level, NICs State/UTs Units provide informatics support to their respective State Government and at the District level lie the NIC District Informatics Offices. NIC has conceptualised, developed and implemented a very large number of projects for various Central and State Government Ministries, Departments and Organisations. Many of these projects are continuing projects being carried out by various divisions of NIC at New Delhi Headquarters and State/District centres throughout the country. Some of the most important note worthy projects, which offer a glimpse of the multifaceted, diverse activities

of NIC, touching upon all spheres of e-governance and thereby influencing the lives of millions of citizens of India are given below:

             

Agricultural Marketing Information Network (AGMARKNET) Central Passport System Community Information Centres (CICs) Computerized Rural Information Systems Project (CRISP) Court Information System (COURTIS) Department of Agriculture Network (DACNET) Examination Results Portal India Image Land Records Information System (LRIS) National Hazardous Waste Information System (NHWIS) Public Grievance Redress and Monitoring System (PGRAMS) Spatial Data Infrastructure (SDI) Training Video Conferencing


There will also be a graphical format of report for various types of report. The next main problem I have to implement in this project is to sending the data that submitted in a local server to the central server. The next problem is to generate various types of reports which are also base on FORM S.1 PROBLEM DEFINITION: To make a system in which a registered user can submit the Syndrominc Surveillance details of a week for a particular reporting unit. i.e. But on the other hand for a big state. 2. Additionally the user can also update the details that he already submitted and also he/she can delete an entry. it is also become quite difficult to collect the data form different parts of the state such they can give the details to the central government in time.2. . The user will be district level user and only he/she can submit the details to central server. The existing system is indirect one. then this user will upload the file to the central server machine and there the data of the FORM S from the text file is restored into the database. There is no any direct source by which the central health ministry becomes aware about the condition in any part of the country in time. The various reports mainly contains “Form Submission Report” i. For there will be a process by which a district level user can create a text file which contains the data of FORM S in a local server.2 EXISTING SYSTEM: As India is a big country it is very difficult to monitor the health status of the people in different region. Progressive report.e. the state government has to give the details about the condition to the central ministry. Comparison Report. this reports shows which reporting unit submitted the Syndromic data in time or late. weekly Form S report. Then the other reports are like.

In the proposed system each reporting unit has to submit the report to main server in every week.3 PROPOSED SYSTEM 2.3 Objective: The underlying objective of the system is to be able to give the health support to the people of that region who are affected by the communicable disease.1 Purpose: The proposed system aims at making the above system automated and online. In the proposed system there will be a facility by which it gives an alert to the government about highly affection by communicable disease in a particular region.3. The primary aim of development of current phase of the program is to introduce a uniform and systematic approach towards monitoring of the affect of communicable disease in the country and to help the government to give a health support and moral support to the people of the country. 2. Again as mentioned by world health organization (WHO) the number of people infected or died by the communicable disease is become very large in India. The proposed system will give a direct way by which government can get full details about the affect of communicable disease in the country. 2.3. This online system gives the central ministry a direct source by which it can able to get the all health status in different region in the country at any time. Now with the proposed system the government can get the details about the people that are affected by the communicable disease and take necessary steps in time.2. So it gives an excellent support to prevent the communicable disease. .2 Scope: The system will provide the user interfaces such that the record keeping and retrieval of the relevant information becomes matter of just few clicks without any hassle. As mentioned earlier there is no any direct source by which the central government can get the details about the health condition in different parts of the country. so government will get the current status at any time. So there should be quick steps to prevent this.3.

Integrating disease surveillance activities. *************************************** . To avoid duplication and facilitate sharing of information across all disease control programs so that valid data are available for appropriate health decision.The program was initiated with a goal of help reduce the burden of morbidity and mortality due to various communicable diseases in the country by: Establishing a sustainable decentralized system of disease surveillance for timely and effective public health action. Under this program a weekly web-based reporting system has been established in all districts.


In the absence of surveillance. By the time the outbreak is recognized. IDSP will provide essential data to monitor progress of on going disease control program and help in allocation of resources and will be crucial in obtaining political and public support for the health programs. Through an effective disease surveillance program health of vulnerable populations in underdeveloped regions and tribal populations in India will be better understood and corrective steps will be taken to improve their conditions. It will help to identify areas of health priority where more inputs are necessary. because sick people would be seen in small numbers by many individual health care workers. The Integrated Disease Surveillance Project (IDSP) covering all states in India seeks to assist the central and state governments to shift from a centrally driven. individual health care workers may not recognize the new disease. Surveillance is essential for the early for the early detection of emerging (new) or re-emerging (resurgent) infectious diseases.3. The continuous monitoring is essential for the ‘early signals’ of any outbreak of any endemic. in those states with advanced health delivery the implementation will be to improve the functions further while in those states with poor health delivery the program will establish a basic and essential module of surveillance Equity in health delivery is one of the emphasis for the government. Integrated Disease Surveillance Program is intended to be the back bone of public health programs in the country.1 PROJECT DESCRIPTION The system to be developed will be referred as Integrated Disease Surveillance Project (IDSP). In the absence of surveillance. districts and communities. Many states in India have good health delivery systems while other states are lagging far behind. vertically organized disease surveillance system to one which is coordinated by the center and implemented by the states. Any system that intends to the futuristic will need to take this variability into account and cater to the differential needs of the country and will need to be decentralized and state specific. In the first phase of IDSP. new or resurgent disease and the action . disease may spread unrecognized by the responsible health care or public health agency. India is currently passing through epidemiological transition. the best opportunity to take intervention measures might have been over. Health problems of some states are predominantly due to communicable diseases while in others it is due to Non communicable diseases. Surveillance is particularly important for the early detection of outbreaks of diseases. The program will take into account the wide geo-political and socio-economic differences in the country and tailor its implementation to levels suitable for the given region of the country.

loop to take effective public health action should be short and effective if disease surveillance were to prevent emerging epidemics. . Integrated Disease Surveillance Project (IDSP) is a decentralized. It is also expected to provide essential data to monitor progress of on-going disease control programs and help allocate health resources more efficiently. Common to both of them are their purpose in describing the health problem. This approach provides for a rational use of resources for disease control and prevention. monitoring trends.  Several activities are combined into one integral activity to take advantage of similar surveillance functions. resources are combined to collect information from a single focal point at each level. private hospitals. The IDSP proposes a comprehensive strategy for improving disease surveillance and response through an integrated approach. resources and target populations. skills. Indian people facing a lot of trouble due to the communicable diseases and non communicable diseases .  The IDSP integrates communicable and non-communicable diseases.  The IDSP integrates both public and private sector by involving the private practitioners. state based surveillance program in the country. Surveillance data can be effectively used for the purpose of social mobilization and make public participate more effectively in control of important diseases. It is intended to detect early warning signals of impending outbreaks and help initiate an effective response in a timely manner. So Indian government tries to take necessary actions for prevention of those diseases in the specific affected area in time with the help of the data comes from different regions in India.  Integration of both rural and urban health systems as rapid urbanization has resulted in the health services not keeping pace with the growing needs of the urban populace. etc and also emphasis on community participation. estimating the health burden and evaluating programs for prevention and control. In the integrated disease surveillance system:  The district level is the focus for integrating surveillance functions. This is an important step in reducing the burden of disease in the community.  All surveillance activities are coordinated and streamlined. private labs. Rather than using scarce resources to maintain vertical activities. NGOs. In recent years.

 The gaps in receiving health information from the urban areas needs to be bridged urgently. Syndromic – Diagnosis made on the basis of symptoms/clinical pattern by paramedical personnel and members of the community. so that valid data are available for decision making at district. Confirmed – Clinical diagnosis confirmed by an appropriate laboratory test. The overall general objective of the IDSP is to provide a rational basis for decision-making and implementing public health interventions that are efficacious in responding to priority diseases. iii. state and national levels. The cases that have been detected and recorded need to be compiled and transmitted to the next level on a regular basis. disease surveillance in IDSP will be of following three categories: i. This should be done every Monday from each type of . Keeping this in mind the main objectives of the IDSP are:  To establish a decentralized district-based system of surveillance for communicable and non-communicable diseases so that timely and effective public health actions can be initiated in response to health challenges in the urban and rural areas  To integrate existing surveillance activities (to the extent possible without having a negative impact on their activities) so as to avoid duplication and facilitate sharing of information across all disease control programs and other stake holders. Types of Surveillance in IDSP: Depending on the level of expertise and specificity. Presumptive – Diagnosis made on typical history and clinical examination by Medical Officers.  Integration with the medical colleges (both private and public) would also qualitatively improve the disease surveillance especially through better coverage. ii.

which must be carried out at each level.reporting unit. PHC/CHC. . on Syndromic Surveillance . All reporting centers will provide zero reporting if no cases were detected. There are five steps in the surveillance procedure. starting from the Primary Health Centre (PHC). 2. Reports from sub. i. 1. Implementation of Form S. Private Hospitals etc should be sent to the district surveillance unit of each district on Monday of every week. Create a backup file of Form S entry in database. Medical Colleges. SPPs. In this project the user in the district level will submit the Form S fields weekly.centers. Each level must have the capacity for analyzing and using surveillance data for early detection. The five recommended steps are:  Collection of data  Compilation of data  Analysis and interpretation  Follow up action  Feedback My work in this project is based on the first type of surveillance in IDSP. The user is also able to edit and delete an entry. 2. prevention and control of outbreaks. The main function to perform in this project are like ..e . So in this project my overall task is to maintain the Form S. upload that file to central server And then restore that backup file in the database of central server. To generate various reports that based on Form S. I have to maintain the syndromic surveillance details in form s .


Economical feasibility. FEASIBILTY STUDY 4. a process consisting of two major steps of System Analysis and Design.All system are feasible if they are unlimited resources and infinite time. 3. The System Development Life Cycle (SDLC) method is thought of as the set of activities that analysts. 2. . 4. designers and users carry out to develop and implement an information system The Systems Development Life Cycle method consist of the following activities: 1. Operational and Economical feasibility of the development computerized system .1 Introduction to System Design Development Life Cycle System development. starts when Management or sometimes system development personnel realize that a particular business system needs improvement. Technical Feasibility.4. Preliminary investigation. System Design. There are three aspects in the feasibility study portion of the preliminary investigation: 1. Implementation.The main objective of the feasibility study is to test the technical.2 Feasibility Study Preliminary investigation examine project feasibility. Determination of system requirements. 2. 5. System testing. the likelihood the system will be useful to the organization . 4. 3. which comprises of Feasibility Study. Operational Feasibility.

all validation checks. Will the system be used and work properly if it is being developed and implemented? III.2 Operational Feasibility Proposed projects are of course beneficial only if can be turned into information systems that will meet the organization’s operating requirements.4. Operational feasibility aspects of the project are to be to be taken as an important part of the project implementation.2. if required in the future. 2. Following questions helped us to test the operational feasibility of system: I. 4. reliability. ease of access and data security 4. So the new system guarantees accuracy. New modules can be added later on the application. and across the world also if loaded on web. has well equipped Labs where all the H/W and S/W tools are available that are needed to run the application. The application will have User-friendly Forms and Screens. Expandability will be maintained in the new system. Is there sufficient support for the project for management? From user? II. So it doesn’t require extra investment to run the proposed application.2. The technical issues raised during the feasibility stage of the investigation were: 1.C. inside and outside the organization.1 Technical Feasibility It involves determining whether or not a system can actually be constructed to solve the problem at hand.I. The proposed application will provide all the necessary information to all the users. Will there be any resistance from the users that will undetermined the possible Application benefits? . 3. N.

3 Economical Feasibility A system that can be developed technically and that will be used if installed must still be a good investment for the organization.The system is targeted to be in accordance with the above-mentioned issues. The system is economically feasible. the management issues and user requirements has been taken into consideration. Beforehand . 4. **************************************** . Since the interface for Integrated Diseases and Surveillances Program is very new and resources such as tools and technology are freely available.2. In the economical feasibility. Financial benefits must equal or exceed the cost. So there is no question of resistance from the users that can undetermined the possible application benefits. the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.


Description: In this process user will submit all necessary details that necessary in the Form S and submit it to the server. the system will give a feedback to the user as he/she successfully submitted or not. Description: In this process user will edit all necessary details that already submitted in the Form S. Main tasks in this phase include Requirement Determination. it contain three sub module. Communication with the Customer is carried out using any of the following means of communication. Description: User will log into the system and after successful login it can go to the IDSP Form S process. before the feasibility study). During this phase our Project Manager is in constant contact with the Customer to find out requirements of the project in detail (A rough estimation is made during the first phase of SDLC.e. Voice Chat or personal meeting.5. Email.2 Functional Requirements: R1: Title: IDSP Form module. A System Requirement Specification Document is prepared at the end of this phase. Output: After successfully submitting the Form S. i. REQUIREMENT SPECIFICATION 5. such as Instant Messenger. and deciding Deliverables. name of supervisor and user will submit all details about the seek people (number of people affected and died by a particular diseases give in the Form S) under the given reporting unit. Input: Updated details about the seek people (number of people affected and died by a particular diseases give in the Form S) under the given reporting . 5.1 Introduction: Requirement Specification is the most important phase of the SDLC. Risk Analysis. Setting up Schedules.2: Title: Form S edit module.1: Title: Form S submission module. R1. User will enter the name of the BLOCK and its corresponding reporting unit name for whom Form S will be going to submit by the user also user will enter the reporting week (the week no for reporting) then user can go to any of the following three module. i. Phone. R1. Input: Name of the health worker.e.

reporting week no and year.unit. Input: Name of the block. Output: After updating the Form S. In this report the user will give the details about the diseases and type of report that he/she want and according to that different report should display.1: Title: Form S form submission report module. R2. reporting unit and reporting week no. how many reporting unit is in time or delay in a given reporting week and then it should display which reporting unit is delay or in time. the system will give a feedback to the user as he/she successfully updated or not. Description: This report should display. . Description: This module will give the all-necessary report that needed by user about Form S.2: Title: Form S syndromic surveillance report module. R2. Input: Name of the block. Output: Firstly it should display the report as block wise i.e. R2: Title: Form S report generation module. i. the different module will display the different reports.3: Title: Form S delete module. the system will give a feedback to the user as he/she successfully deleted or not. Output: After updating the Form S. Each report should display in hierarchal order.e. reporting unit. Output: According to the types of report. Input: User will select the type of report that he/she wants to see. how many reporting unit is delay or in time for a particular reporting week under a particular block and then it should display which reporting unit under that given block is in time or late. Description: This report should give the details about the Form S. In the report generation module various types of reports are to display according to user selection. then block wise under the selected district and then reporting unit wise under the selected block. Description: In this process user will delete all necessary details that already submitted in the Form S. R1. first it should display the report district wise.

R2.e. Description: It should generate the reports according to the year as entered by user but the report should be a comparable one with respect to the previous year of the entered year. it should give the details of the entry in Form S according to the week as entered by the user. Progressive.e it should give the details of the entry in Form S about the effected people in a particular week number and should show the progressive status with respect to the previous week. type of report (Weekly. state name. state name. i. Input: Week number.Input: Type of diseases. Output: Type wise it should display the report to the user.1: Title: Form S weekly syndromic surveillance report module. Comparison. i. Output: Report as district wise. i. then block wise and finally reporting unit wise. Description: It should generate the reports according to the week as entered by user but the report should be a progressive one. it should display the number of the diseases effected people in two successive year in comparable way. Input: Year. state name.3: Title: Form S comparison report module. Output: Report as district wise. Output: Report as district wise.2. R2. .e. Description: It should generate the reports according to the week as entered by user. R2.2: Title: Form S progressive report module. Name of the state and week number.2. Input: Week number. then block wise and finally reporting unit wise. Line Chart and Bar Chart).2. then block wise and finally reporting unit wise.

2.Security: The whole system is about security and that’s why security is must. It must be highly secure and difficult to break without detection.3 Nonfunctional Requirements: 1. ********************************************* .5.Maintainabilty: Back up of database should be taken periodically. 3. 4. 6.Usability: The system should be easy to use and should have a very easy to use user interface. 5.Extensibilty: The system could be extended to integrate with the main IDSP system.Portability: This application will run on both WINDOWS and UNIX platform.Reliabilty: The system will be highly reliable and cannot be fooled.


details until later. Use graphics whenever possible. The goal of structured analysis: 1. 6. Differentiate between logical and physical entity. ANALYSIS OF THE SYSTEM 6. Structured analysis aids in defining the requirements the new system so that the user has a system they need. The result of the analysis should understand the problem as a preparation of design. The purpose of the object-oriented analysis is to model the real world system so that it can be understood. dynamic and functional models but during analysis of PIS we have skipped the object and dynamic model as the activities and actions are clearly defined.1 Introduction: System analysis is a detailed study of various operation performed by a system. 4. 2. how it done and avoid implementation decisions. Analysis of PIS is performed by the following object-oriented methodologies.6. . To do this we have to abstract important real world system features first and defer small. 3.2 Structured System Analysis: Structured System Analysis is asset of techniques and graphical tools that allow the analysis to develop a new kind of specification that are easily understandable to the user. Begin with an examination of the board picture of the system. The aim of the system analysis is to deliver system in line with the user requirements. It is activity that encompasses most of the task that we can collectively call Computer System Engineering. The successful analysis model states that what we must done. It is an ordered approach that works from the high level views to lower level details in which the user needs are presented through the use of dataflow diagram. The real world model consists object. Build a logical system model of the proposed system from the physical model to express the building blocks of the system to programmer analyst. without restricting.

Context Diagram: The model. 3. It shows the system flow sequence among the process of the system. concise and highly readable manner. 2. interacts with the system. It depicts a picture of what is being specified and easy to understand presentation of the application. Some basic tools are: 1. 3.Characteristics of the structured analysis: 1. It calls for rigorous study of the user area.3 Tools for Structured Analysis: A number of structured tools are used for analysis for the candidate system. . But it plays a very important role studying the current system. 2. which represents the whole system in a single process showing the external entities that. The process is portioned. It contains a single process. is called Context Diagram. Data dictionary. so that a clear picture about the system flow from general to specific can be made. System flowchart is the graphical representation of the system operational sequences within the system. Dataflow diagram. It shows all external entities that interact with the system and dataflow between these entities and the system. Context diagram. 6. The element of the system specify in the precise.

An arrow indicates the direction of the flow and the line is labeled by the name of the dataflow. External entities that use system data are sometimes called sinks. A circle or a bubble represents a process that transforms incoming data flow into outgoing dataflow. Process will be expanded in sequent level DFD. each of which has its meaning. what transformation of the data are done. The high level processes in a system are: o Receivable process. These are represented by square of rectangle. o Verifiable process. External entities that supply data into a system are sometimes called Sources. Each high level process may be consisting of more than one lower level processes. . 3. It is the starting point in the system that decomposes the requirement specifications down to the lowest level detail. Each process has one or more data inputs and one or data outputs. It clarifies system requirements and identifies major transformation that will become programs in a system design. DFD also provide an overview of data that a system process. 2. o Disposal process. They are given below: 1.Dataflow Diagram: Dataflow diagram is a graphical representation of a system that indicates the flow of data to and run from the system. Dataflow models that passages of data in the system and are represented by line by joining system components. Process show that the systems do. The four symbols in DFD. External entities are outside to system but they either supply input data in the system or use the system output. Circles in DFD represent them. DFDs are nothing more than a network of related system functions and indicate from where information is received and to where it is sent. what files are used and where the results flow.

File or data store is a repository of data. . : The external entities i. The following diagrams illustrate the notation and the symbols used to create the DFDs. data at rest. They contain data that is retained in the system. Process can enter data into data store or retrieved data from the data store.4.e. : Database. : A Process. user. : The arrowhead shows the flow of information. : The table in which information will be stored. An open rectangle is a data store.

Context Diagram IDSP System: .DFD for the proposed System: The Data Flow Diagram (DFD) for the proposed system is shown in the following pages in order of their process from the highest level to the lowest level of procedures.

Late Entry. . Of People Died. Of Infected People.Level 1 DFD for IDSP System: NOTE: (a) No. No.

Level 2 DFD for Report Generation Process: .

Level 3 DFD for Form Submission Report Process: .

Level DFD for Syndromic Surveillance Process: Level 4 DFD for Weekly Report: .


Level 4 DFD for Bar Chart Generation Process: Level 4 DFD for Line Chart Generation: .

Level 2 DFD for Form S Process: .

Level 2 DFD for Form S Process: (Cont…) .

Level 2 DFD for Create New User Process: .

a data dictionary is a structured respiratory of data about data. It is a set of rigorous definition of all DFD data elements and data structures and serves as a valuable document to the organization at the time of future enhancement.Data Dictionary: It is a structured place to keep details of the contents of data flows. processes and data store. .

2. 3.There are three classes of items to be defined in the data dictionary. Data Element: The smallest unit of data that provides for no further decomposition is called data element. Data Flows and Data Stores: Data Flows are data structures in motion. Data Structures: It consists of a group of data elements handled as a unit. A data stores is a location where data structures are temporarily located. . whereas data stores are data structures at rest. 1.

Disease_threshold. form_s. District. form_s Reporting Unit District Block Reporting Unit Disease. User_table District Block. User_table State District. form_s.SL. Block. Disease_threshold Disease Disease_threshold 2 3 statename districtcode character varying character varying character varying character varying character varying character varying character varying Long Int Long Int Long Int character varying character varying Integer 50 3 State Name District Code 4 5 6 7 8 9 10 11 12 13 14 districtname blockcode blockname reporting_code reporting_name district_pop block_pop reporting_pop disease_code disease_name threshold_value 50 3 50 5 50 5 50 - District Name Block Code Block Name Reporting Unit Code Reporting Unit Name District Population Block Population Reporting Unit Population Disease Code Disease Name Threshold value of Diseases 15 16 17 18 myear name_worker supervisor_name dt_week_from Integer character varying character varying Date 30 30 - Year of reporting Name of the health worker Name of the supervisor Date of reporting form_s form_s form_s form_s . Block. Disease_threshold. Block Reporting Unit. form_s. No 1 FIELD NAME statecode DATA TYPE character varying FIELD LENGTH 2 DESCRIPTION State Code SOURCE State. Reporting Unit. Reporting Unit. Reporting Unit.

19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 Id_dsu fever_c_m fever_c_f fever_d_m fever_d_f wtrystool_c_m wtrystool_c_f wtrystool_d_m wtrystool_d_f Jaundice_c_m Jaundice_c_f Jaundice_d_m Jaundice_d_f paralysis_c_m paralysis_c_f paralysis_d_m paralysis_d_f unusualsympt_c_m unusualsympt_c_f character Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer 3 - DSU ID No of male for fever case No of female for fever case No of male died for fever case No of female died for fever case No of male died for fever case No of male for Loose Watery Stool case No of female for Loose Watery Stool case No of male died for Loose Watery Stool No of female died for Loose Watery Stool No of female for Jaundice case No of male died for Jaundice No of female died for Jaundice No of male for Paralysis case No of female for Paralysis case No of male died for Paralysis No of female died for Paralysis No of male for Unusual Symptom No of female for Unusual Symptom form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s form_s .

38 39 40 41 42 43 44 45 46 47 48 49 50 unusualsympt_d_m Integer unusualsympt_d_f weekno late mdate u_id pwd add remarks permission_frm permission_to user_status date Integer Integer Character Timestamp Character varying Character varying Character varying Character varying Character varying Character varying Character varying Date 1 10 10 50 50 50 50 50 - No of male died for Unusual Symptom No of female died for Unusual Symptom Reporting week Late entry for reporting Time of reporting User ID Password User Address User Remark From where permission is given To whom permission is given User Status Date of login form_s form_s form_s form_s form_s User Table User Table Master Table Master Table Master Table Master Table Master Table Master Table .

Each step in the process flow is represented by a different symbol and contains a short text description of the process step in the flow chart symbol. The flow chart symbols are linked together with arrow connectors (also known as flow lines).Flow Charts: A flow chart is a graphical or symbolic representation of a process. IDSP FORM SUBMISSION STATUS (WEEKLY REPORT) .




2 Architectural Fundamentals Client-Server Paradigm The paradigm of arranging for one application program to wait passively for another application to initiate communication pervades so much of distributed computing it has been given a name: .1 Tool and Technology Used: The following tools and technology are used to develop the system Hardware: Intel Pentium® processor at 500 MHz Minimum 512 MB memory Software: Component Operating System Web Server Database Browser Database Connectivity Java Development Kit Client script language Application Servlet Java Server Pages Software Name and Version Windows XP Tomcat 6.0 or higher Availability Shareware Freeware Freeware Licensed Freeware Freeware Freeware Freeware Freeware 7.7. IE explorer PstgreSQL Driver 8.4 or higher JSP 2.5.0 PostgreSQL 8.2 J2SDK1. System Environment 7.2_05 Java Script Servlet 2.2 Mozila Firefox.

the computer needs only a single physical connection to the Internet. and be shared among several users. known as a client that connects over a network to the server running SQL Server. Users access the server through a client or Server application: ♦ In a two-tier Client/Server system. The application that actively initiates contact is called a client. The term Client and Server refer to the two application involved in a communication.The Client .Server paradigm of interaction. user runs an application on their local computer. On such system. Running many servers on a single computer is practical because a server does not consume computational resources while waiting for a request. Although a computer can operate multiple servers. one server program runs for each service being offered. Client/Server Database System Client/Server system are constructed so that the database can reside on a central computer. . known as a server. Multiple Services on One Computer A single. while the application that passively waits for contact is called server. server – class computer can offer multiple services at the same time. and is also known as a thick client. The client application runs both business logic and the code to display output to the user.

where models are created with the JSP bean and controlling is done by servlet and view is done by JSP. Also we used JavaServer Pages Model 2 architecture that is also known as MVC architecture .The server application is the one that opens connections to the database server and can be running on the same server as the database. where presentations are done with JSP and all business logics are performed in JSP bean and servlet. An output of a Java compiler is not executable code. . The use of bytecode enables the java run-time system to execute programs much faster. Translating a java program into bytecode helps makes it much easier to run a program in a wide variety of environments. Which is itself a multithread application capable of working with many concurrent users . or it can connect across the network to a separate server operating as a database server. To develop this system we used three-tier architecture.2. Because the execution of every java program is under the control of JVM. the JVM can contain program and prevent it from generating side effects outside of the system.2 Technology Used 7. the client application logic is run in two locations: • • The thin client is run on the user’s local computer and is focused on displaying results to the user. 7. Java was designed to be easy for professional programmer to learn and use efficiently.1 Java Java is an object-oriented language. Java can be used to create two types of programs-applications and applets. Benefits of using Java • Java is Secure. Java achieves the protection by confining a java program to the java execution environment and not allowing it to places extraordinary demands on a page. Java inherits the C/C++ syntax and the objectoriented features of C++. The business logic is located in server application running on a server. it is a byte code. which is called the java virtual machine. Byte code is a highly optimized set of instruction that is designed to be executing by the Java Run-time system. Rather.♦ In multi-tier client/server system. Thin clients request functions from the server application.

which allows you to write pages that perform multiple tasks simultaneously. Java was designed to meet the real-world requirement of creating interactive. Java is robust. networked pages. Thus. This makes is possible to dynamically link code in a safe and expedient manner. it also checks your code at run time. Web Servers were made to just serve basic text content and images. • Java is multithreaded. Web Applications allow a web site to be dynamic rather than straight static pages. In other words. Java programs carry with them substantial amount of run-time type information that is used to verify and resolve accesses to objects at run time. JSP was developed by Sun Microsystems to allow server side development. Access to other parts of the computer. Introduction to Java Servlets: Java Servlets provide the means through which Web Applications can be written in Java. Java programs can be dynamically downloaded to all the various types of platform. To accomplish this. Java supports multithreading programming. However. This interface was standardized as CGI. However. it is portable. The multi-platform environment of the web • • • Introduction to JSP : JavaServer Pages (JSP) is a technology based on the Java language and enables the development of dynamic web sites. It is a strictly typed language. JSP files are HTML files with special Tags containing Java source code that provide the dynamic content. The hard-to-trackdown bugs are simply impossible to create in Java. Servlets transform a web site with plain text and images into a rich interactive environment for the user. Java’s exception handling avoids the problem of checking errors and handling them manually and brings run time error management into objectoriented world. . Thus the ability to create robust program was given high priority in the design of java. In the beginning. in order to provide an interactive environment. Java’s exception handling. Java is dynamic. the web server had to be extended to allow programs or scripts to be executed. it checks your code at compile time.because the programs must execute reliably in a variety of system.

The most fundamental advantage of Servlets is that they are tightly coupled to the Web Server. Second. It has to: • • • Allocate memory for the process. Copy information about the environment that the parent process was running in so that there is a security context. If you recall from the diagram above. First. the user would fill in the form and submit it to the web server. And the web server (parent process) must be constantly aware of the child process in order to send the CGI output back to the user's web browser. operating systems typically incur some overhead in simply launching another process. When you think about it. . it outputs the relevant HTML or other data back to the Web Server. an interpreted language typically has to load an entire program to interpret the script before the program can even execute. which acts as a middleman and sends the data back to the browser. the web server whose lifetime exists only during the particular user request typically launches CGI scripts as a separate process. Even on a small program and a relatively fast machine. this is the Perl executable. Then. a Java program can take a second or more to start. an operating system really has to do quite a bit. When the CGI program runs. In the case of Java. The diagram below illustrates the life cycle of a browser getting results from a CGI program.The browser would load an HTML page consisting of some form elements such as text boxes or check boxes. it is the Java binary. It turns out that the CGI model is extremely inefficient and slow especially with interpreted languages such as Perl or Java. Why Use Servlets? Servlets have a variety of enhancements over plain CGI. The Web Server would take the form data and submit the data to the CGI program. In the case of Perl.

your program can large and complex. This was appositively impact on performance. 7. Modularity: When developing a complete server-side application. you can freely move your Servlets to any other platform that supports Java. • • • Reusability: Creating component parts to an application is one-way to achieve reuse. Java Servlets. A java servlet can send and receive emails. as does a CGI program. Tomcat Directory Structure . Platform Independence: The servlet code is compiled into byte code that are interpreted by a platform-specific Java Virtual Machine (JVM) on the web server.2. and returning the request to a client. using object-oriented to encapsulate shared functionality is another Java uses both.2 Tomcat 6. JSPs and Java Beans provide a way to modularize your application-breaking application down into tiers and tasks. It is a completely object-oriented language and as such provides mechanism for reuse. Since the Servlets themselves are made up of machine independent byte code. It is always better to break down an application into discrete modules that are responsible for specific task. When you do this. and prevent the machine grinding to halt. keeping database connection open. This makes it possible for hundred and thousand of users to access the same servlet simultaneously without bringing down the server.0 Tomcat is a server container responsible for handling client request. Servlets also have more alternatives than do regular CGI programs for optimization such as catching previous computations. passing the request on to a servlet. When a Servlet receives a user request it simply spawns another thread within the same process and handles the request. A CGI program needs to create a separate process for each user request. and the like. they can access all the java APIs. generate multiple request do not generate processes.Moreover we use Java Servlet because of the following reasons: • Efficient: As compared with the CGI. make use of Java Beans (EJB) or any other parts of java platform. Java Servlet provides a much more efficient method of handling user request. this makes your application very easy to maintain and understand. Good server implementations use thread pools to constrains the number of thread that can be used to services the client request. invoke method of remote objects using RMI or COBRA. obtain directory information using the JNDI package. It includes many additional features that makes it useful platform for developing and deploying web application and web services. Access to enterprise java APIs: Since Servlets are the extension of the java platform.

3 PostgreSQL 8. This is where the Tomcat places its log and output files.Directory Name bin config Description Contains start-up/shutdown Scripts.2.xml that sets the default values for the various web application deployed Tomcat. The servlet APIs source files. support.xml (Tomcat’s main configuration file) and web.2 PostgreSQL is an object-relational database system that has the features of traditional commercial database systems with enhancements to be found in next-generation DBMS systems.2: features. and price. Additional class libraries and support files required by the Development tools. . There are several ways of measuring Postgresql8. Contains various configuration files including server. performance. reliability. These are only the empty interfaces and abstract classes that should be implemented by any servlet container. doc lib logs src webapps 7. Contains sample web application. PostgreSQL is free and the complete source code is available. Contains miscellaneous documents regarding Tomcat.

triggers. slower for others. and the source code often make PostgreSQL support superior to other DBMSs. Support : Our mailing lists provide contact with a large group of developers and users to help resolve any problems encountered. Each release has at least one month of beta testing. like user-defined types. solid releases that are ready for production use. Price : . the user community. Direct access to developers. We believe we compare favorably to other database software in this area. or it is worthless. inheritance. Performance : PostgreSQL's performance is comparable to other commercial and open source databases. We strive to release well-tested. subselects. and our release history shows that we can provide stable. There is commercial per-incident support available for those who need it. manuals. It is faster for some things. foreign key referential integrity. We have some features they do not have. stable code that has a minimum of bugs. While we cannot guarantee a fix. Reliability : We realize that a DBMS must be reliable. rules. and multi-version concurrency control to reduce lock contention. Our performance is usually +/-10% compared to other databases. commercial DBMSs do not always supply a fix either.Features : PostgreSQL has most features present in large commercial DBMSs. and sophisticated locking. like transactions. views.

You can add our code to your product with no limitations. both commercial and non-commercial.We are free for all use. ********************************************* . except those outlined in our BSD-style license stated above.

SYSTEM DESIGN 8.1 Introduction .

2.The system design is a solution. Logical Design and 2. 8. and prepare a Logical design walkthrough. All in a format that meets user requirements. Design of the physical system • • • Design the database and specify backup procedures. Logical design specify the user specify the user needs a level of detail that virtually determines the information flow into and out of the system and require data resources. Design physical information flow through the system and physical design walkthrough. device a test and implementation plan. outputs. the system implementation. The physical design consist of the following steps: 1. The physical design maps out details of physical system plan. a “how to” approach to the creation of a new System. make edit security. .2 Physical Design The physical design produces the working system by defining the system specification that tells the programmers exactly what the candidate system must do.1 Logical Design A Data Flow Diagram shows the logical flow of system and defines the boundaries of the system. and specify any new hardware and software. The design phase focuses on the detailed information of the system recommended in the feasibility study. Logically design describes the. Plan system implementation • Prepare a conversion schedule and a target date. prepare input and output specification.1. detail the implementation plan. The design phase is a transition from a user-oriented document to a document oriented to programmers or database personnel. and control specification. Specify input/output media. System design goes through two phases of development: 1. databases and procedures. 8.1. Emphasis is on translation of performance specification into design specification. Physical Design Logical design review the present system.

2 Structured Design: Structured design is flow methodology. One of the important steps in designing the database is normalization. Designing of project consist of number of steps. 3. Normalization is the process of refining the data model and making the data more efficient.3 DATABASE DESIGN INPUT /OUTPUT DESIGN Database Design The design of database describes how data should be organized around the user requirements. It should be designed in the line with the activity and volatility of the information and the nature of the storage media and devices. Structured design begins with system specification that identifies inputs and outputs describe the functional aspects of the system. It should be organized around the user requirements. which are independent and contain no unnecessary or redundant data.• Determine the training procedure. E R Diagram: . This technique logically groups the data over the number of tables. courses and timetable. 8. The design of the Integrated Disease Surveillance Program (IDSP) consists of the following steps: • • 8. It is an attempt to minimize the complexity and makes a problem manageable by subdividing it into smaller segments or module. Devise a test and implementations plan and specify any new hardware and software.

There are three basic elements in ER models: Entities are the "things" about which we seek information. Diamonds are normally used to represent relationships and ovals are used to represent attributes. Attributes are the data we collect about the entities. ER diagrams often use symbols to represent three different types of information. . Boxes are commonly used to represent entities. Relationships provide the structure needed to draw information from multiple entities.An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database.


but the last two are mainly academic and will not be discussed). . There are two goals of the normalization process: eliminate redundant data and ensure data dependencies make sense. In other words there must not be any transitive dependency in out tables. As stated earlier. tables must already be in 1NF and there must be a primary key in each table. Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored. First Normal Form: The normalization process involves getting our data to conform to three progressive normal forms. In our case database has been normalized in 1NF. The first normal form or 1NF involves removal of redundant data from horizontal rows. We want to ensure that there is no duplication of data in a given row.Table Design: Normalization: Basically database normalization is the process of efficiently organizing data in a database. the normal forms are progressive. but dependant on other value in the table. second normal form deals with redundancy of data in vertical columns. Second Normal Form: Where the 1NF deals with redundancy of data across a horizontal row. and a higher level of normalization cannot be achieved until the previous levels have been achieved(there are actually five normal forms. and that every column stores the least amount of information possible(making the field atomic). Third Normal Form: In 3NF we are looking for data in our tables that is not fully dependant on primary key. since there is primary key in every table upon which other key is dependant. In our case database has been normalized in 2NF. so to achieve 2NF. since there is not any non-atomic field.

All the tables are interrelated using the key code that is unique in each case entity. reporting_population. The database consisting of 9 tables. In this project this table contain data as reporting_code. since there is not any transitive dependency in our tables. Block (TABLE) This is the table containing the data about the blocks. In this project this table contain data as state_code and state_name. Reporting Unit (TABLE) This is the table containing the data about the Reporting Units. district_name. reporting_name. In this project this table contain data as block_code. block_name. . Considering by various records regarding the IDSP (Form S) system. District (TABLE) This is the table containing the data about the districts.In our case database has been normalized in 3NF. the design of the database is developed so that it can satisfy the entire requirement and should be efficient enough. In this project this table contain data as district_code. block_population. State (TABLE) This is the table containing data about the states. district_population.

User (TABLE) This table contain the user information of IDSP. . block_code. permission_from. threshold_value. state_code. Disease_Threshold (TABLE) This is the table containing the data about the disease threshold. The data contain in this table as user_ID. Patient_info (TABLE) This is one of the important table in this project. permission_to etc. district_code. address. ru_code. In this project this table contain data as disease_code. week_no. The different data contains in this table are nos of effected people in different disease.district_code. As main issue of IDSP is to maintain the details about the effected people by different disease in the country.Disease (TABLE) This is the table containing the data about the Diseases. As each district has different threshold values . state_code. Master_table (TABLE) This table contain the user information that are used for official purpose. year.to maintain those value this table is used. In this project this table contain data as disease_code. The data contain in this table as user_ID. district_code. So this table maintain the those details . like the name of the supervisor under whom the user worked. who gave the permission to the user etc. state_code . disease_name. password.

block_code) Foreign Key (state_code. district_code) Foreign Key (state_code) 3.Table Name: Reporting Unit FIELD NAME reporting_code block_code district_code DATA TYPE character varying character varying character varying FIELD LENGTH 5 3 3 .Table Name: District FIELD NAME district_code state_code district_name district_pop DATA TYPE character varying character varying character varying bigint FIELD LENGTH 3 2 50 - Constrains: Primary Key (state_code.Table Name: Block FIELD NAME block_code district_code state_code block_name block_pop DATA TYPE character character character character bigint varying varying varying varying FIELD LENGTH 3 3 2 50 - Constrains: Primary Key (state_code.1.Table Name: State FIELD NAME state_code state_name DATA TYPE character varying character varying FIELD LENGTH 2 50 Constrains: Primary Key (state_code) 2. district_code) 4. district_code.

block_code) 5.Table Name: Disease FIELD NAME disease_code disease_name DATA TYPE character varying character varying FIELD LENGTH 5 50 Constrains: Primary Key (disease_code) 6. district_code) 7.state_code reporting_name reporting_pop character varying character varying bigint 2 50 - Constrains: Primary Key (state_code.Table Name: patient_info FIELD NAME state_code district_code block_code myear name_worker supervisor_na me reporting_unit dt_week_from id_dsu fever_c_m fever_c_f DATA TYPE character character character integer character character varying varying varying varying varying FIELD LENGTH 2 3 3 30 30 30 3 character varying date character integer integer . district_code.Table Name: Disease_threshold FIELD NAME disease_code state_code district_code threshold_value DATA TYPE character varying character varying character varying integer FIELD LENGTH 5 2 3 - Constrains: Primary Key (state_code. disease_code) Foreign Key (state_code. block_code. district_code. reporting_code Foreign Key (state_code. district_code.

reporting_unit) 8. block_code.Table Name: User_Table FIELD NAME u_id pwd district_code state_code DATA TYPE character character character character varying varying varying varying FIELD LENGTH 10 10 3 2 Constrains: Primary Key (u_id) Foreign Key (state_code. district_code. weekno) Foreign Key (state_code. district_code. myear.fever_d_m fever_d_f wtrystools _c_m wtrystools _c_f wtrystools _d_m wtrystools _d_f Jaundice_c_m Jaundice_c_f Jaundice_d_m Jaundice_d_f paralysis_c_m paralysis_c_f paralysis_d_m paralysis_d_f unusualsympt_ c_m unusualsympt_ c_f unusualsympt_ d_m unusualsympt_ d_f weekno late mdate integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer character Timestamp time zone 1 without Constrains: Primary Key (state_code. district_code) . block_code. reporting_unit.

Table Name: Master_Table FIELD NAME u_id add remarks permission_frm permission_to user_status date DATA TYPE character character character character character character Date varying varying varying varying varying varying FIELD LENGTH 10 50 30 30 30 30 - Constrains: Primary Key (u_id) Foreign Key (u_id) .9.


Once source code has been generated, software must be tested to uncover and correct as many errors as possible before delivering to the customer. Thus the goal is to design a series of test cases that have a high like hood of finding errors. Testing begins in the small and progresses to the large. This means that early testing focuses on a single component to uncover errors in program logic and function. After individual components are tested, they must be integrated. Testing continues as the software be constructed. Finally, a series of high order tests are executed once the full software is operational. 9.2 Introduction: During the system testing, the system is used experimentally to ensure that the software does not fail, that is, it run according to its specifications and in the way user expect. System testing is vital to the success of the system. The idea behind testing is to come up with the errors that otherwise may become an obstacle during the functioning of the project. Test cases are devised with this purpose in mind. A test case is a set of data that the system will process as normal input. However, the data are created with the express intent of determining whether the system will process them correctly. The importance of software testing and its limitations with respect to software quality cannot be over emphasized. Because of its importance and the large amount of project effort associated with it, it becomes necessary to the test the system before its implementation. Necessity of system testing: Some of the necessities of testing process include the following: 1. Once a system has been designed, it is necessary to undergo an exhaustive testing before installing the system. This is important because in some cases a small system error, not detected and corrected before installation, may explode into much larger problem later on. 2. Inadequate testing or non-testing may lead to errors that may be costly when they appear months later on. 3. Another necessity for the system testing is its utility as a user oriented vehicle before implementation, since even the best program is worthless if it does not meet the user requirement.

9.3 Types of testing: Some types of testing that are used in the system are: String testing (Input Validation) In this type of testing, the input data are tested to examine whether they confirm to the given standards. Client-side and Server-side Validation codes are written to catch my invalid input data. Unit Testing: Unit testing focuses verification effort on the smallest unit of software design- the software component or module. In unit testing, each module are taken and tested extensively to uncover as many errors as possible. Integration Testing: Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program structure that has been dictated by design. Regression Testing: Regression testing is type of integration testing. In this testing, some subset of tests that have already been conducted is re-executed to ensure that changes have not been propagated unintended side effects.

Validation Testing: Validation Testing is successful when a software functions in a manner that can be reasonably expected by the customer. Reasonable expectations are defined in the system Requirement Specification that describes all user- visible attributes of the software. Test cases are designed to ensure that all the functional requirements are satisfied, all the

behavioral characteristics are achieved and all the performance requirements are attained. Various modules are tested thoroughly to see whether all the requirements that were specified in SRS are met.

System Testing: System Testing is series of different tests whose primary purpose is to fully exercise the web-based system. The some essential tests that are done are:

Recovery Testing: Recovery testing is system test that forces the system to fail in a variety of ways and verifies that recovery is performed either automatically or manually. Test has been conducted to put an array out of bound and check weather the system is able to handle this situation or stops functioning all together.

Security Testing: Security testing attempt to verify that protection mechanism built into the system will, in fact protect it from improper penetration. During testing, the tester plays the role of the individual desires to penetrate the system. As the system being developed in web based system and is a project undertaken by the Health Ministry of India, it needs to be fool proof as far as security is concerned. 1. Anybody who does not have a Login ID and Password cannot enter to the system to add, delete and update the data. 2. A user can register him/herself into the system if he/she is a valid health worker. He has to submit all necessary details at the time of registration. 3. The connectivity to the database is secure, so that only authorized user can access the database.

The end user is always concerned about security along with increased dependence on the computer. the system is ready for implementation. SYSTEM SECURITY Every candidate system must provide built in features for security and integrity of data. before the system is up and running. the developer and the system analyst must consider measures for maintaining data integrity and controlling security at all times. This involves built-in hardware features. In the system development. This involve creating compatible files . The new design implementation simply means converting a new system design into an operational one. fire and natural disaster. fraud. 10. After a through testing of the system as described above. training and operating staff and installing hardware and terminal etc. . programs and procedure to protect candidate system from unauthorized access. Without safeguard against unauthorized access. The system has been demonstrated recently to the WHO person and officers related to IDSP. a system could be so vulnerable as to threaten the survival of the organization. The objective of implementation is to put the tested system into operation while holding costs and risks.9. embezzlement.4 System Implementation: A crucial phase in the systems life cycle is successful implementation of new system.

Database Security The proper use of the file library is another important security features. like Form P. The internal controls required means that the programmer and analyst build controls into every system. uploading the file and restore it on the central server. This module can be integrated with the other module in the IDSP system. fire. theft. Developing a corporate auditing policy will ensure that future system meet the minimum requirements for security and control against fraud and embezzlement. databases and documentation. It is possible to eliminate such error proper testing routines. Transaction Entry A logical failure occurs when activity to the database is interrupted with no chance of completing the currently executing transactions. Neither the auditor nor the user can verify the system check itself. File backup means keeping duplicates copies of the master and the other key files and storing them in suitable environmental conditions.Physical Security The most costly loss in software is program error. Application Security The complexity of the system makes auditing necessary. Through still readable. flood. Physical security provides safeguards against the destruction of hardware. and loss of power through proper backup. This involves adequate file backup and reliable personal to handle file documentation when needed. and Form W etc also with IDSP GSI system. When the system is and running again it is not known whether or not modification are still in memory or were made to the actual data. Form L. sabotage and cave dropping. 11. Moreover there are various tasks are there in the IDSP system. Parallel runs should be implemented whenever possible. the database may be inaccurate. . FUTURE ENHANCEMENT: In this module I developed the system only for Form S and also on creation of backup file.

PROJECT SCREEN SHOTS: .based and an undertaking of Health Ministry. Only after the system is fool proof then the system be uploaded to Internet. needs to be thoroughly tested and hence better encrypted facility and be developed to enhance the security of the system.This system being web. 13.

IDSP Home Page: .

Here user will select the form type he/she going to submit/update or delete.IDSP select form type page: In this page appears after successfully logged in by the authenticated user. .

Reporting Unit Name. The user will select mainly Block Name. . Week No (From and To).Form S Detail selection page: In this page the user will select the necessary option for Form S submission.

After submitting all details the user will click submit button to stored datas into server.Form S Submit Form: In this form the user will submit all details of Form S. .


this validation will appear.Form Submit validation: After successfully inserting the datas unto server. .

Form S update form: .

Form S update validation: .


Form S update/delete validation if data is not available: Form S delete form: .


.IDSP Form S report menu page: In this menu the user will select the diseases types and report types for which he/she wants to view the report.

IDSP report view district wise: .

Form S district wise bar chart view: .

Form S district wise bar chart view( weekly): .

Form S district wise line chart view: .

Form S district wise line chart view (weekly): .

.Back up file upload page: 12. related to health status to the people of India. CONCLUSION: The objective of the project was to develop IDSP (Form S) system. which helps to perform the function.

The concept of peer-review helped to rectify the problems as and when they occurred and also helped me to get some valuable suggestions that were incorporated by me. Bibliography: Books: . Working together in a team helped me to communicate better.It was a good experience developing this project. I understand the importance of planning and designing as a part of software development. Developing the project has helped me to gain some experience on real-time development procedures.

Korth.com www.com .java. H. JSP. Fifth Edition By A. F. Sudarshan.sun. Silberschatz. Awad  Database System Concepts. and EJB By Budi Kurniawan  System Analysis and Design By Elias M.com www.  Mastering Java Script By James Jaworski Websites:      www.roseindia.javaworld.w3school. Complete Reference in JAVA By Herbert Schildt  Java for the Web with Servlets.com www. and S.com www.devguru.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->