23-05-2012, 10:23 AM
Generic E-Tools In the web applications
Generic E-Tools.doc (Size: 236 KB / Downloads: 31)
Abstract
The project is entitled “Generic E-Tools “ helps to handle the web applications. It is very difficult for a programmer to create user interface forms and to provide database connectivity for each and every form separately whenever he needs it. The work will be very fast if he had a utility, which can provide him all the activity, which he has to do for creating those forms.
Hence, it was received that there was a strong need for generating a utility which can help the programmer with on-fly user interface forms and providing database. Connectivity to those form and to maintain the database
Description of the Project
It is very difficult for a programmer to create user interface forms and to provide database connectivity for each and every form separately whenever he needs it. The work will be very fast if he had a utility, which can provide him all the activity, which he has to do for creating those forms.
Hence, it was received that there was a strong need for generating a utility which can help the programmer with on-fly user interface forms and providing database. Connectivity to those forms and to maintain the database.
This project mainly comprises modules:
Creation Mailing Lists
Creating User Forms to the tables and retrieving data using these forms
Display Existing Forms
Generating Reports by Form wise and List Wise
Using Google search from our application
These modules deal with several kinds of information related from linking a user applicable form to the database to retrieving information and updating the database.
The information is stored in the database in a systematic way so that it can be easily retrieved whenever required through queries by the reporting module. Data capturing is done through user-friendly screens depending upon the type of data. The entire system is being protected by a user level password to enable different assigned activities so that no intruder can access the data. The user for this application is a person who wants to generate a new web enabled dynamic content application and not the end user working at the client side.
SYSTEM ANALYSIS
Analysis is the detailed study of the various operations performed by a system and their relationships within and outside of the system. A key question is: What must be done to solve the problem? One aspect of analysis is defining the boundaries of the system and determining whether or not 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.
System Requirement Specification
What is SRS?
Software Requirement Specification (SRS) is the starting point of the software developing activity As system grew more complex it became evident that the goal of the entire system cannot be easily comprehended. Hence the need for the requirement phase arose. The software project is initiated by the client needs. The SRS is the means of translating the ideas of the minds of clients (the input) into a formal document (the output of the requirement phase.)
The SRS phase consists of two basic activities:
1) Problem/Requirement Analysis:
The process is order and more nebulous of the two, deals with understand the problem, the goal and constraints.
2) Requirement Specification:
Here, the focus is on specifying what has been found giving analysis such as representation, specification languages and tools, and checking the specifications are addressed during this activity.
The Requirement phase terminates with the production of the validate SRS document. Producing the SRS document is the basic goal of this phase.
ROLE OF SRS:
The purpose of the Software Requirement Specification is to reduce the communication gap between the clients and the developers. Software Requirement Specification is the medium though which the client and user needs are accurately specified. It forms the basis of software development. A good SRS should satisfy all the parties involved in the system.
Conclusion
The project is able to successfully incorporate all the requirements specified by the user. Proper care has been taken during database design to maintain data integrity and to avoid data redundancy. A client side validation has also been done with utmost care by considering all the possibilities and requirements of different users to avoid data inconsistency. The user is provided with a very friendly interface, hiding all the technical intricacies. Design procedures and user manuals are also included in the project to help users better understand the system.
The project is designed and coded in such a way that any further modifications that are needed in future can be easily implemented without affecting the functionality of the system. The technical documentation provided in the project report helps the application developers understand the internal architecture of the system and thus assists them in enhancing the system.