The document discusses the Rational Unified Process (RUP) and Rapid Application Development (RAD) methodologies. RUP follows five phases - Inception, Elaboration, Construction, Transition, and Production. It aims to reduce unexpected costs and prevent waste. RAD is used for urgent projects and emphasizes prototyping. It develops components in parallel like mini-projects then assembles them. Business modeling, data modeling, process modeling, application generation and testing are key activities in RAD.

1. Software Methodologies and
Management
Jai Hind College
SY BSc IT(Sem 4)
Prof. Diksha S. W.
(MSc CS, NET,GATE)

2. Rational Unified Development
Inception Elaboration Construction Transition Production
• Unified Process Model
• Reduces the unexpected development cost and prevent wastage
of resources

3. 5 phases of RUP
1. Inception
2. Elaboration
3. Construction
4. Transition
5. Production

4. Inception
Communication and planning
Identification of project scope
Customer requirement identification
Project plan, project goal, risk identification

5. Elaboration
Describing in more details.
Redefine if we need, cancel project as well as if
needed.

6. Construction
Here we develop and complete the project based on the data
we get from previous stages.
Coding is done.
All kind of testing are also done here.
Alpha testing is done here (Team performs testing)

7. Transition
Here finally project transit from development
environment to production.
Beta testing is done
Removing all the bugs from project based on customer’s
feedback

8. Production
Final phase of the model
Project is maintained here
Project is updated here accordingly.

9. Rapid Application Development Model
(RAD)
This model helps in developing the S/W in short span (urgent cases)
It is combination of prototype and iterative model
This model puts less emphasis on planning tasks and more emphasis on development and
coming up with a prototype.
The initial activity starts communication between customer and developer for gathering
requirements.
Then requirements are divided into groups.
Planning is more important to work together on different modules.
Thus, the components or functions are developed in parallel as if they are mini projects.
The developments are time boxed (timelines), delivered and then assembled into a working
system.
The most vital point for this model to be successful is to make sure that the prototypes developed
are reusable.

10. Business modeling
Data modeling
Process modeling
Application
generation
Testing and
turnover
Business modeling
Data modeling
Process modeling
Application
generation
Testing and
turnover
Module 1
Team 2
Business modeling
Data modeling
Process modeling
Application
generation
Testing and
turnover
Team 1
Module 2
Business modeling
Data modeling
Process modeling
Application
generation
Testing and
turnover
Team 3
Module 3

11. Business modeling
Requirement gathering
What data drives the business process
What data is generated, who generates it
Where does the information go
Who process it and so on.

12. Data modeling
The information in the business modelling phase is refined into a set of objects and analysis
for the important objects for the business are done.
The attributes of each object are identified and defined the relationship between objects.

13. Process modeling
In this phase, the input of the previous two phases is put into a process.
The data objects defined in the data modeling phase are modified to fulfill the information
flow to implement the business model.
The process description is created for adding, modifying ,deleting or retrieving a data
object.

14. Application generation
In the application generation phase, the actual system is built.
Coding is done.
To construct the software, the automated tools are used. (Eclipse in
case of Java language)

15. Testing and turnover
The prototypes are independently tested after each iteration so that the overall testing is
reduced.
The data flow and the interfaces between all the components are fully tested. Hence, most
of the programming components are already tested.

16. Where can be used?
There is a need to create a system that can be modularized in 2-3 months of time.
It should be used if there’s high availability of designers for modeling and the budget is
high enough to afford code generating tools.
RAD SDLC model should be chosen only if resources with high business knowledge are
available.

17. Advantages
Changing requirements can be accommodated.
Quick initial reviews occur.
Reduced development time.
Encourages customer feedback.
It is easier to accommodate changing requirements die to the short iteration time spans.
Increases reusability of components.

18. Disadvantages
Strong team needed (Highly skilled developers/designers).
Expensive model.
More man power.