Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Understanding SDLC: Methodologies, Risks, and Benefits - Prof. ALI, Assignments of Software Development

National University of Sciences and Technology (NUST)Software Development

The software development life cycle (sdlc) is a systematic approach to designing, developing, and maintaining software projects. The various sdlc methodologies, including waterfall, agile, iterative, and v-shaped, and discusses the risks associated with each. It also highlights the benefits of using sdlc to improve software quality and reduce development costs.

Typology: Assignments

2020/2021

Uploaded on 04/15/2021

ultra-channel
ultra-channel 🇵🇰

5

(2)

5 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
2 SDLC: (SOFTWARE DEVELOPMENT LIFECYCLE)
SDLC represents the System Development Life Cycle. It is a process that
provides a complete overview of the design, and maintenance of a software
project by ensuring that all operational and user needs, objectives, and end
objectives are addressed. With SDLC, the software project quality and the
entire software development process are improved. By
2.2 HOW THE SDLC OPERATES
SDLC works by reducing software development costs while simultaneously
improving quality and shortening production time. SDLC achieves these
seemingly different goals by following a program that removes the common
pitfalls of software development projects. That program begins by checking
for existing error programs.
Next, It outline the requirements for the new system. It then creates
software through stages of analysis, planning, design, development, testing
and distribution. By anticipating costly errors such as failing to ask the end
user or client for feedback, SLDC can eliminate unwanted redundancies even
after the fact.
(Alexandria Alvander, April 8,2019)
3 SDLC's VARIOUS METHODS
• Waterfall
• Agile
• Iterative
• V-Shaped
3.1 WATERFALL
Some experts say that the Waterfall model was never designed to be a real
project model. No matter, the Waterfall model is widely considered to be the
oldest planned SDLC method. And it's a very straightforward approach: finish
one phase, then move on to the next. There is no going back. Each section
relies on information from the previous section and has its own project plan.
pf3
pf4

Partial preview of the text

Download Understanding SDLC: Methodologies, Risks, and Benefits - Prof. ALI and more Assignments Software Development in PDF only on Docsity!

2 SDLC: (SOFTWARE DEVELOPMENT LIFECYCLE)

SDLC represents the System Development Life Cycle. It is a process that provides a complete overview of the design, and maintenance of a software project by ensuring that all operational and user needs, objectives, and end objectives are addressed. With SDLC, the software project quality and the entire software development process are improved. By 2.2 HOW THE SDLC OPERATES SDLC works by reducing software development costs while simultaneously improving quality and shortening production time. SDLC achieves these seemingly different goals by following a program that removes the common pitfalls of software development projects. That program begins by checking for existing error programs. Next, It outline the requirements for the new system. It then creates software through stages of analysis, planning, design, development, testing and distribution. By anticipating costly errors such as failing to ask the end user or client for feedback, SLDC can eliminate unwanted redundancies even after the fact. (Alexandria Alvander, April 8,2019) 3 SDLC's VARIOUS METHODS

  • Waterfall
  • Agile
  • Iterative
  • V-Shaped 3.1 WATERFALL Some experts say that the Waterfall model was never designed to be a real project model. No matter, the Waterfall model is widely considered to be the oldest planned SDLC method. And it's a very straightforward approach: finish one phase, then move on to the next. There is no going back. Each section relies on information from the previous section and has its own project plan.

The downside of Waterfall is its toughness. Indeed, it is easy to understand and easy to handle. But premature delays can lose the entire project timeline. Since there is little room for review once a phase has been completed, problems cannot be resolved until you get to the repair stage. This model does not work well if flexibility is required or if the project is long and continuous. (Robert Half, May 2019) 3.2 AGILE The Agile model has been around for almost a decade. But recently, it has been a major factor in driving software development in many organizations. Some businesses value this Agile approach so much that they now use it for other types of projects, including non-technical applications. For the Agile model, “quick failure” is a good thing. This method produces continuous discharge cycles, each with minor changes, growing from previous releases. In each iteration, the product is tested. The Agile model helps teams identify and address minor issues in projects before they turn into more important issues, and engage business stakeholders and get their feedback across the development process. As part of their acceptance of this approach, many teams also use an Agile framework known as Scrum to help plan complex development projects. Scrum teams work in “sprints,” which usually last two to four weeks, to complete tasks assigned to them. Daily Scrum meetings help the whole team monitor progress throughout the project. And ScrumMaster is tasked with keeping the team focused on its mission. (Robert Half, May 2019) 3.3 ITERATIVE Iterative model is repetition performed on the body. Instead of starting with fully known needs, project teams use a set of software requirements, and then test, evaluate and identify other needs. A new type of software is developed for each phase, or iteration. Clean and repeat until the complete system is ready.

5.0 RISK MANAGEMENT METHODS OF THESE LIFECYCLES

5.1 RISKS OF WATERFALL

Waterfall risk are minimized and expired with the help of Waterfall risk management. It uses many common Waterfall tools. Their main feature is the ability to create charts. Accidents at Waterfall are also managed with the help of charts. The risk chart starts when risk is identified. After that the management followed its development. As the risk increases with the project, its line on the chart rises. In such cases engineers and managers try to find product features that enhance the risk and reciprocate. If the risk line on the chart goes down and the project progresses, the risk is considered as high as the priority. The dangerous waterfall charts are divided into three categories. The first of these starts when the danger is discovered and ends when the engineers begin to search for a solution. The second stage lasts until a solution is found. The third stage is the risk removal phase. It expires on the end of the risk period. Such model of risk management permits body of waterfall developers to avoid several bugs in their production and improve its quality and client acceptance.