RAD MODEL
Rapid Applica on Development (RAD) is a so ware development life cycle (SDLC) model that
emphasizes fast development, early prototyping, con nuous user feedback, and itera ve
delivery rather than extensive upfront planning and documenta on.
RAD was formally introduced by James Mar n in 1991 as a response to the limita ons of
tradi onal SDLC models (such as the Waterfall model), which were o en slow, rigid, and
unable to accommodate rapidly changing user requirements.
With rapid applica on development, developers can quickly make mul ple itera ons and
updates to the so ware without star ng from scratch.
This helps ensure that the final outcome is more quality-focused and aligns with the end users’
requirements.
The core idea of RAD is :- “Build a working model quickly, show it to users, gather feedback,
refine it, and repeat un l a sa sfactory system is produced.”
Phases of RAD MODEL :-
1. Requirements Planning Phase :- (Planning + Requirement analysis)
This is the combina on of planning and requirements analysis
Ac vi es :-
a. Iden fy system scope
b. Iden fy constraints. i.e, budget, me, resources etc.
c. Define func onal and non func onal requirements
d. Priori ze features
Output :- Time boxes, me boxes consists high level requirement list, development
schedule
2. User Design Phase :- (Design)
Ac vi es :-
a. Build rapid prototype for system components
b. Conduct JAD (Joint applica on development)
c. Refine UI, Workflows, and features
d. Validate requirements using prototypes
e. Collect con nuous user feedback
Output :- Refined func onal requirements, approved screen layouts, validated
prototypes
3. Construc on Phase :- (Coding + Tes ng)
Ac vi es :-
a. Convert prototypes into working code
b. Integrate modules
c. Develop database and business logic
d. Perform unit and integra on tes ng
e. Op mize performance
Output :- Fully func onal system, Tested modules, Updated documenta on
4. Cutover Phase :- (Deployment)
Ac vi es :-
a. Final system tes ng
b. User acceptance Tes ng (UAT)
c. Data conversion and user training
d. System Deployment
Output :- Deployed so ware system, Trained users, Maintenance plan
Flow chart :-
FOURTH GEN TECHNIQUES
Fourth Genera on Techniques (4GT) refer to a class of high-level, non-procedural so ware
development tools and languages that allow developers to build so ware systems rapidly with minimal
manual coding.
The term “fourth genera on” dis nguishes these tools from earlier programming genera ons:
1GL – Machine language
2GL – Assembly language
3GL – High-level languages (C, Java, Python)
4GL – Very high-level, problem-oriented languages and tools
The Main goal of 4GT is :-
To increase developer produc vity, reduce development me, and simplify so ware construc on by
using automated tools and declara ve specifica ons instead of detailed procedural code.
4GT plays a major role in RAD (Rapid Applica on Development) and prototyping-based SDLC models.
Why 4GT implemented ?
In tradi onal programming (3GL), the developer specifies how to perform a task step by step.
In 4GT, the developer specifies what is required, and the system automa cally determines how to
generate the solu on.
Example :-
3GL (Procedural) 4GL (Declara ve)
for(i=0;i<n;i++){ SELECT SUM(value) FROM data WHERE value > 50;
if(arr[i] > 50) sum += arr[i];
}
Componenets of 4GT :-
It is not a single language or tool. It is a collec on of technologies, including :-
1. 4GL (4th genera on languages) – SQL, matlab, R, ABAP, etc.
2. Applica on Generators - Microso Access, Oracle Forms & Reports, PowerBuilder
3. Report Generators - SQL Report Builder, Crystal Reports etc.
4. Screen/Form Generators - Oracle Forms, Visual Studio Designer etc.
5. Query Languages – SQL, QBE(query by language)
6. Code Generators – UML to code tools
4GT is mostly used in :- RAD, Prototyping, CBD, agile development.
4GT means Automated tes ng, AI, or the work which done by system onbehalf of you.
ELABORATE 4GT more in your own words