In this approach, both the systems are run in parallel for a specific period of time. During the period of if any serious problems were identified while using the new system, the new system is dropped and the older system is taken at the start point again.In this approach, the existing system is converted to the new system abruptly, some times over a weekend or even overnight. The old system is used until a planed conversion day. There exist no parallel activities.In this approach, a working version of the system is implemented in one art of the organization such as a single work area or department. When the system is deemed complete it is installed through out the organization either all at once (direct cut-over) or gradually (phase-in).
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' Once aspect of analysis is defining the boundaries of the system and determining whether or not candidate system should consider other related system. During analysis, data are collected on the available files, decision points and transactions handled by the present system.Software Requirement Specification is the starting point of 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 handled by the client needs the SRS is the means of translating the ideas of the minds of clients (the inputs) into a formal document (the output of the requirement phase).
The SRS phase consists of two basis activities:
1) Problem/Requirement Analysis: The process is order and more nebulous of the two, deals with understand the problem, the goal and constraint.
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 requirements phase terminates with the production of the validate SRS document. Producing the SRS document is the basic goal of the phase.
Role of SRS:
The purpose of the Software requirement is to reduce the communication gap between clients and the developers. Software Requirement Specification is the medium through which the client and user needs are accurately specified. It forms the basic of software development. A good SRS should satisfy all the parties involved in the system.
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.
This project mainly comprises three modules:
Creation and modification of tables
Connecting User Forms to the tables and retrieving data using these forms
Generation of Reports
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