11-05-2012, 11:49 AM
GOVERNMENT SCHEME MANAGEMENT SYSTEM
GOVERNMENT SCHEME MANAGEMENT SYSTEM.docx (Size: 741.66 KB / Downloads: 108)
ABSTRACT
Most of the schemes introduced by the Government go into dustbin just because the officials who implement the schemes could not make them available to suitable people. So there is a secured and transparent system needed which enable an ordinary person to directly apply for a scheme and track the status from time to time and know whether he is entitled to receive the fruit or his application is rejected by the officials. In any case, the applicant should be able to know the reason for rejection openly. This catches trust in the Government from the people and avoids mis-utilization of funds.
Government Scheme Management System is a software application to automate the process for utilization of various schemes provided by government for various panchayats. Government Scheme Management System Software takes care of the activities related to the schemes provided by the government. The major responsibility is to take care of the proper utilization of different schemes in a transparent way.
This system clearly keeps track of the status of user’s application by tracking the actual activities that are under process within the panchayat or at higher level at any point of time, by the administrators. This system provides effective way to manage the important information in a very secure manner by authenticating users at various levels.
This system design is modularized into various categories covering the internal official management concepts associated with the information of the panchayats and user applications with different levels of abstraction.
This system has very good GUI so that a novice user did not feel any operational difficulties. This system mainly concentrated in designing various reports requested by the users as well as higher authorities such as Scheme wise details report, Panchayat wise details report, User wise report etc.
When the user applies for a scheme, his details will be stored in the database and sent to the panchayat for verification. Panchayat people conduct a physical verification and sends their remarks to the DDO who would write his comments. These details are sent to final approving authority and help him to approve or disapprove the person for the scheme. The same details can be viewed by the user so that the user would get a clear picture of what is happening from time to time.
Technologies used: J2SE, Servlets, JSP, JDBC and Java Script.
SYSTEM ANALYSIS
INTRODUCTION
After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.
ANALYSIS MODEL
The model that is basically being followed is the SPIRAL MODEL, which states that the phases are organized in a linear order. First of all the feasibility study is done. Once that part is over the requirement analysis and project planning begins. If system exists one and modification and addition of new module is needed, analysis of present system can be used as basic model.
The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are: -
• Requirement Analysis
• Project Planning
• System design
• Detail design
• Coding
• Unit testing
• System integration & testing
Here the linear ordering of these activities is critical. End of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall requirement of the system.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.