0% found this document useful (0 votes)
10 views

Software Development Methodologies

Details of software development methodologies

Uploaded by

Yamuna
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views

Software Development Methodologies

Details of software development methodologies

Uploaded by

Yamuna
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

SOFTWARE DEVELOPMENT METHODOLOGIES

Methodologies are used to develop systems based on SDLC. There are different
types of methodologies which suitable for a different type of projects.

1) Waterfall Model
It’s a traditional method and clarifies the process into a linear flow with the
specified sequence.

Requirements

Design

Development

Testing

Deployment

Maintenance

Waterfall Model
2) Prototype Methodology
The prototype is a software model with limited functionalities that can be
changed, added, and removed from a system. In a prototype model, a
prototype can be a phased design and get the customer evaluation or
feedback and change or update according to the feedback.

Prototype Methodology

3) Agile Methodology
Agile software development is more than practices such as pair
programming, test-driven development, stand-up planning sessions, and
sprints.
After the analyzing phase, the development will start function-wise. After
each and every function it will test. After developing the functionalities, a
demo is released to get feedback from the clients and developers to do the
changes, and finally, system testing will be done.
Integrated
& Test

Yes

No

Next Iteration

Agile Methodology

4) Rapid Application Development


RAD is a form of agile methodology. It uses a prototype and user feedback
over strict planning and requirement recording. Developers can make
multiple iterations and updates to software rapidly because of the prototype.

Rapid Application Development


5) Spiral Model
There are four main categories in the spiral model.
 Plan – plan the budget and development plan.
 Determine goals – It analysis the alternatives & goals.
 Evaluate Risk – Analyze the risks before the development.
 Develop and test – Software design & development will be started
after risk analysis

Spiral Model
6) Joint Application Development (JAD)
It is a combination of agile and rapid application development. In JAD the
client and the developers are having brainstorming sessions as well as
workshops to share their knowledge and resolve the conflicts of the system.
There are two main categories in JAD.
 Workshop and planning
 Design & development

Participants Breakdown them/ Barriers us


Create project ownership
Workshop commitment and buy in
Quickly Defines
Final project work product is
Requirements

Resolve Conflicts JAD


Also see workshop
Identifies Best Practices breakdown structure (WBS)
Helps forming, storming and
nothing of project team What, why, when, where, & how

JAD Method

7) Learn Development Methodology


The special point in this methodology is that this allows demand for the
application in a lower budget and less time period using a prototype doing
the usability testing validation internally, testing externally and getting the
points from the user behavior, and doing the user modifications to the
software.
UK Process

Boss Customer

Validate Test Learn from user


Concept Prototype
Internally Externally behavior
s
s

Iterations
Usability testing

Learn Development Methodology

8) Scrum Development Methodology


These days the scrum methodology is the most popular method of
developing applications. Hereafter the requirement analyzing phase, these
are dividing the tasks among the employees and having daily meetings
(Scrum meetings) to discuss the process and do the changes or updates. For
these scrum meetings, customers can participate when are free and this is
very flexible the scrum master is the main role of the scrum meeting. He is
the person who is in change of the meeting.

Scrum
Daily scrum meeting
Master
& artifacts update

Team Meeting
Product
Task
backlog
No changes in Review complete tasks
during or goal respective

Scrum Development Methodology

You might also like