INSTITUTE OF PUBLIC ADMINISTRATION AND MANAGEMENT

UNIVERSITY OF SIERRA LEONE

Module Code & Title: Computer Programing

Level: (Undergraduate)
Module Study Guides - Academic Year 2023/24
Lecturer: Mohamed Fouard Kanu (MSc.)

PRESENTATION GROUP M
TOPIC
SOFTWARE DEVELOPMENT METHODOLOGIES

From Group M (Java Extreme)

 SOFTWARE DEVELOPMENT METHODOLOGY
2

NAMES OF GROUP
GEORGE CHRISTIAN BENDU DICKSON
• Introduction • Dynamic Development methodology
• Definition
• Types RASHID KABBA SUMARA
• Prototype Development methodology
BOCKARIE ARUNA
• Agile development methodology EMANUEL AJALA
• Joint Application Development
ZANIAB JALLOH methodology
• DevOps development
methodology DESMONDA
• Rational unified development
ISHMAIL methodology
• Waterfall development
methodology
YEALIE TURAY
• Conclusion
RAHAMA
• Rapid development
methodology
From Group M (Java Extreme)
 SOFTWARE DEVELOPMENT METHODOLOGY
3

INTRODUCTION
 Software development methodologies are essential frameworks that
guide the process of creating software applications. They provide
structure, best practices, and processes for teams to follow, ultimately
aiming to improve efficiency, productivity, and the quality of the final
product. In this presentation, we'll delve into various software
development methodologies, their characteristics, advantages, and
when to use them.
 Software development methodology involves different processes for
developing the software project and follows a development life cycle.
 The methodology is selected based on the aims and objectives of the
project.
 Software development methodology is an approach in software
engineering that provides a framework for defining the structure, plan,
and control different processes while developing an information
system (Vick, 1984).
From Group M (Java Extreme)
 DEFINATION
4

 A software development methodology is a process by which

developers design, implement and test new computer
programs. Following a methodology benefits developers
because these processes lay out a structured sequence of steps
that guide professionals through each stage of development.

 Additionally, development methodologies often follow a design

philosophy, which can help developers align their process and
the product's features with its functional goals. For example,
the developer may define what the software product does and
what problems it solves for users as part of their design
philosophy.

From Group M (Java Extreme)

 SOME COMMON SOFTWARE DEVELOPMENT
MEDTHODOLOGY
5

THERE ARE MANY SOFTWARE DEVELOPMENT METHODOLOGY

 Agile development methodology

 DevOps development methodology
 Waterfall development methodology
 Rapid development methodology
 Dynamic systems and development method
 Prototype development methodology
 Joint application development methodology
 Rational unified process development methodology

From Group M (Java Extreme)

 6
Agile development methodology

Agile is a type of project management methodology. It emphasizes

a fast and flexible approach by allowing the development team to
divide larger projects into smaller tasks. The team can complete
these tasks in shorter iterations while gaining feedback on these
smaller portions for more consistent communication with clients
and test users. This methodology is useful for reducing risks,
expediting development, improving customer satisfaction and
reducing redundancies. Since developers gain client feedback
throughout the development and testing cycle, this can be a great
method to use for projects that require significant collaboration.

From Group M (Java Extreme)

 DevOps development methodology

Similar to the agile method, DevOps is another great

methodology to use for developers working in collaboration with
clients.
 DevOps refers to a development strategy that combines
development and operations.
 This means that this process integrates continuous testing and
delivery of applications.
 For example, when the development team completes a portion
of a project, the operations team then tests the new addition for
functionality.
 The operations team can deliver feedback to the development
team to further optimize the feature so there's a continuous
stream of feedback and improvement between departments.

From Group M (Java Extreme)

 Waterfall Development Methodology
8

The waterfall method involves breaking a task down into a

sequence of stages. With this process, developers need to
complete each stage in its entirety before moving to the next
step. Although this process may be less efficient than those
where developers work on several stages of a project
concurrently, the waterfall method is effective for ensuring
thoroughness at every level of project development. This method
also minimizes redundancies because it prevents overlap between
tasks at different stages.

From Group M (Java Extreme)

 Rapid development methodology
9

This development methodology focuses on rapidly producing

and releasing new prototypes. It places greater emphasis on
designing products quickly rather than developing a rigid plan.
The benefits of this include increased flexibility and faster
development. For example, a development team works with a
client to understand their goals for new software. Instead of
drafting a multi-phase plan for developing the software, they
may create a general plan and develop the product with the
primary goal as the focus. After developing the product
prototype, the testing phase may happen more holistically
rather than in stages

From Group M (Java Extreme)

 Dynamic systems and development method

10

The dynamic systems development method (DSDM) functions

similarly to the rapid application method. It focuses on
collaboration and relies on an iterative process. Additionally,
this method works incrementally, meaning that developers
create the base version of a product and deliver it to the client
for feedback before adding the remaining features to complete
the prototype. The four phases of this development method are
feasibility and business study, functional model and prototype
iteration, design and build iteration and implementation.

From Group M (Java Extreme)

 Prototype development method
11

With the prototype methodology, developers build a complete

prototype and then test it for refinement. Rather than
developing different features or functions of a completed
product and testing each of them before combining them into
the final product, this method focuses on creating a whole
product before testing it and getting client feedback. This
development model can work well for simple software,
software upgrades or products that rely on relatively few
features to operate. The six phases of the prototype method
are goal setting and analysis, quick design, prototype building,
user evaluation, refinement, implementation and maintenance

From Group M (Java Extreme)

 Joint application development
12

The joint application development model highlights the

relationship between developers, clients and users. It's the
most collaborative of all the development methodologies. It's
used most often when clients or end-users require specialised
software for their needs. For example, a client may hire a
software developer to design a program that allows them to
more efficiently a specific task in their industry. Since the
client has specialised needs, they work closely with the
development team to clarify what features benefit them the
most in achieving their goals.

From Group M (Java Extreme)

 Rational unified process
13

 The rational unified process is another agile-based

development methodology. It uses four phases
1. Inception: In this stage, developers determine the
feasibility of a project, and they establish what resources
they need to complete the project.
2. Elaboration: Developers use this stage of the
development process to anticipate costs, set budgets and
identify the uses for the product.
3. Construction: The construction phase involves the
designing, building and testing of the product.
4. Transition: Developers transition the product into its
operational phase, at which point end-users apply the
product to their needs and provide feedback for
refinement.

From Group M (Java Extreme)

 CONCLUSION
14

Software development methodologies play a crucial role

in guiding teams through the complex process of
creating software applications. Each methodology has its
own strengths and weaknesses, and the choice of
methodology should be based on the specific needs,
requirements, and constraints of the project. By
understanding and applying these methodologies
effectively, teams can enhance collaboration, improve
productivity, and deliver high-quality software products
to meet customer expectations.

THANK YOU FOR THE ATTENTION

From Group M (Java Extreme)
From Group M (Java Extreme)