3.

0 Methodology of the study (Software Engineering Paradigm)

1.Requirements Planning phase combines elements of the system planning and systems analysis
phases of the Systems Development Life Cycle (SDLC). Users, managers, and IT staff members
discuss and agree on business needs, project scope, constraints, and system requirements. It ends
when the team agrees on the key issues and obtains management authorization to continue.
2.System design phase during this phase, users interact with systems analysts and develop models
and prototypes that represent all system processes, inputs, and outputs. The RAD groups or
subgroups typically use a combination of Joint Application Development (JAD) techniques and
CASE tools to translate user needs into working models. User Design is a continuous interactive
process that allows users to understand, modify, and eventually approve a working model of the
system that meets their needs.
3.Development phase focuses on program and application development task similar to the SDLC.
In RAD, however, users continue to participate and can still suggest changes or improvements as
actual screens or reports are developed. Its tasks are programming and application development,
coding, unit-integration and system testing.
4.Cutover phase resembles the final tasks in the SDLC implementation phase, including data
conversion, testing, changeover to the new system, and user training. Compared with traditional
methods, the entire process is compressed. As a result, the new system is built, delivered, and placed
in operation much sooner.

The RAD (Rapid Application Development) model is based on prototyping and iterative
development with no specific planning involved. The process of writing the software itself involves
the planning required for developing the product.

Rapid Application development focuses on gathering customer requirements through workshops or

focus groups, early testing of the prototypes by the customer using iterative concept, reuse of the
existing prototypes (components), continuous integration and rapid delivery.

What is RAD?
Rapid application development (RAD) is a software development methodology that uses minimal
planning in favor of rapid prototyping. A prototype is a working model that is functionally equivalent
to a component of the product.

In RAD model the functional modules are developed in parallel as prototypes and are integrated to
make the complete product for faster product delivery.

Since there is no detailed preplanning, it makes it easier to incorporate the changes within the
development process. RAD projects follow iterative and incremental model and have small teams
comprising of developers, domain experts, customer representatives and other IT resources working
progressively on their component or prototype.

The most important aspect for this model to be successful is to make sure that the prototypes
developed are reusable.

RAD can be used:

RAD should be used only when a system can be modularized to be delivered in incremental manner.

It should be used if theres high availability of designers for modeling.

It should be used only if the budget permits use of automated code generating tools.

RAD SDLC model should be chosen only if domain experts are available with relevant business
knowledge.

Should be used where the requirements change during the course of the project and working
prototypes are to be presented to customer in small iterations of 2-3 months.

4.0 Data Gathering Procedures

1. Requirements Gathering
Requirement gathering is a process of collecting the user needs to solve a problem or issues and
achieve an objective. It is basically a software capability needed by the user to solve a problem or
achieve an objective. This is really an important phase/ milestone in a project life cycle. If the
requirement gathering is not done properly/ completely, all the hierarchy phases given below stay
incomplete, no matter how best the design, until and unless requirements are complete. So we should
carefully plan and carry out the requirements gathering with a systematic approach. The developers
did some observations regarding the transaction in the company, which eventually led to the
discovery of problems of the said institution.
As a developer, our group brained storming to make a specific question and searching in the internet
about the park.We provide a little question by a computerized paper about the specific background
and process of the park,We also used recording during the interview .We interview personally to
gathered information clearly.

5.0 Software/Project Estimation

5.1 Schedule of Activities