25-08-2017, 09:32 PM
CONGRUOUS PRUDENT
CONGRUOUS.doc (Size: 3.85 MB / Downloads: 72)
Introduction & Objective
• Public Scheme is a web application to automate the process for utilization of various schemes provided by Govt. for various panchayats at different levels.
• This Project tracks the status of users application by tracking the actual activities that are under process within the panchayat or at higher level at any point of time.
SYSTEM ANALYSIS
Existing System
• Most of the schemes introduced by the Government who implement the schemes could not make them available to suitable people.
• An ordinary person can’t apply to the scheme directly.
• There is no secured system to the applied person.
• The person unable to know about the rejection of an application.
The funds can’t reach to an ordinary person there is a chance of mis-utilization of funds.
Proposed System
• Public Schemes a system which enable an ordinary person to directly apply for a scheme and track the status from time to time
• Directly an Ordinary person can apply to the scheme through this portal.
• In case the application is rejected then the person will come to know the reason for the rejection.
• This system provides effective way to manage the important information in a very secure manner by authenticating users at various levels.
FEASIBILITY REPORT
Preliminary investigation examines project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All systems are feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
• Technical Feasibility
• Operation Feasibility
• Economical Feasibility
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 with 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.
Designing Stage:
The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo code, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input
Development (Coding) Stage:
The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, data management forms, data reporting formats, and specialized procedures and functions. Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software.