Download Software Development Life Cycle (SDLC) Models: A Comprehensive Guide and more Essays (high school) Technology in PDF only on Docsity!
ASSIGNMENT 01 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 0 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name DO THE SON Student ID GCD Class GCD1002 Assessor name PHYOMIN TUN Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature SƠN Grading grid P 1 P 2 P 3 P4 M 1 M 2 D1 D 2
❒ Summative Feedback: ❒ Resubmission Feedback: Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date:
Table of Contents
- Introduction
- I. Describe Two Iterative and Two Sequential Software Lifecycle Models. (P1)
- Describe the following SDLC
- Two Sequential Software Lifecycle Models........................................................................................................................................................................................
- Waterfall Model:
- V-Model:
- Prototyping Model:
- Scrum:........................................................................................................................................................................................................................................
- Spiral Model:
- Model suitable for the project:...................................................................................................................................................................................................
- Discuss the suitability of each of the SDLC models for the project
- II. Explain how risk is managed in the Spiral lifecycle model (P2)
- What is Risk Management:............................................................................................................................................................................................................
- Process of Risk Management:
- III. Explain the Purpose of a Feasibility Report (P3)
- Definition of feasibility report
- Discuss the purpose of conducting a feasibility study
- IV. Describe how technical solutions can be compared(P4)
- The Purpose of Technical Solutions:
- Create alternative solutions and compare them.
Reference ................................................................................................................................................................................................................................................... 23 Figure 1 Waterfall model............................................................................................................................................................................................................................. 7 Figure 2 v-model ......................................................................................................................................................................................................................................... 9 Figure 3 Prototyping .................................................................................................................................................................................................................................. 12 Figure 4 scrum ........................................................................................................................................................................................................................................... 13 Figure 5 spiral ............................................................................................................................................................................................................................................ 15 Introduction
Software Development Life Cycle (SDLC) is the process of understanding how an information system may serve business goals,
designing the system, implementing it, and delivering it to users. It is a framework that contains a set of activities to be
accomplished at each step in the software development process. It is a technique of presenting a full notion of the development,
design and maintenance of a software project by guaranteeing that all functionality along with user requirements, goals and
ultimate objectives are addressed together. With SDLC, the quality of the software project and the whole software development
process is better. If you've attended a coding class or have coded yourself, this could seem straightforward. However, in the
actual world, it is not that simple. So, in my assignment, I will present clearly about how SDLC is crucial
Actual development starts at this stage. Each developer must closely conform to the agreed-upon plan. Also, verify that
developers have a good coding style and process standards in place
At this step, the developers verify and discover the faults that exist in the program and correct them so that the product has the
highest quality before it gets to consumers
The objective of this stage is to deploy the program to the production environment so that users can begin using the product.
Furthermore, this lets any remaining problems to be found before the product is distributed SDLC is significant because it offers
an effective foundation and process to design software applications. It assists in efficiently planning before commencing the real
development. SDLC helps developers to examine the requirements. It assists in eliminating excessive expenses during
development.
2. Two Sequential Software Lifecycle Models
1. Waterfall Model:
Waterfall model is an example of a Sequential model. In this paradigm, the software development activity is separated into
several stages and each phase consists of a number of activities and has different goals.
Waterfall model is the pioneer of the SDLC procedures. In fact, it was the first model which was extensively adopted in the
software business. It is separated into stages and the output of one phase becomes the input of the following phase. It is required
for a phase to be finished before the following phase begins.
Figure 1 Waterfall model
Different Phases of Waterfall Model in Software Engineering
Different phases Activities performed in each stage
Requirement Gathering stage During this phase, comprehensive requirements of the software system to
be built are acquired from customer
Design Stage • Plan the programming language, for Example Java, PHP, .net
- or database like Oracle, MySQL, etc.
- Or other high-level technical details of the project
2. V-Model:
V Methodology is a highly disciplined SDLC model which features a testing phase simultaneous to each development phase. The
V model is an extension of the waterfall paradigm whereby software development and testing is conducted in a sequential
method. It is known as the Validation or Verification Model.
Figure 2 v-model
Different phases Activities performed in each stage
Requirement Gathering stage Gather as much information as possible regarding the specifics & specs
of the necessary program from the customer. This is nothing just the
Requirements collecting stage.
Design Stage Plan the programming language like Java, PHP, .net; database like
Oracle, MySQL, etc. Which would be suited for the project, including
some high-level functionality & architecture
Built Stage After the design stage, it is build stage, it is nothing but really code the
program
Test Stage Next, you test the program to ensure that it is constructed as per the
requirements are supplied by the customer.
Deployment stage Deploy the program in the appropriate environment
Maintenance stage Once your system is ready to use, you may need to alter the code later on
as per client request
Advantages of V Model Disadvantages of V Model
Phases are finished one at a time under this model, which requires
extreme discipline.
high uncertainty and danger
works effectively for smaller projects with clearly defined criteria. Unsuitable as a model for intricate and object-oriented projects.
Simple, clear, and convenient to use. It is challenging to go back and update a functionality once an
application has entered the testing phase.
Because of the model's rigidity, it is simple to manage. Specific
deliverables and a review process are included at each phase.
It takes till the end of the life cycle for any working software to be
generated.
Figure 3 Prototyping
4. Scrum:
Scrum is an agile development approach used in the creation of Software based on an iterative and incremental procedures.
Scrum is adaptive, rapid, flexible and effective agile framework that is meant to offer value to the client throughout the
development of the project. The major purpose of Scrum is to meet the customer’s requirement via an atmosphere of transparency
in communication, joint ownership and continual improvement. The development begins with a rough notion of what needs to be
developed, constructing a list of characteristics ordered by priority (product backlog) that the owner of the product wishes to get.
Figure 4 scrum
Figure 5 spiral
Spiral Model Phases Activities performed during phase
Planning It comprises calculating the cost, timing and resources for the iteration. It
also entails knowing the system requirements for constant
communication between the system analyst and the client
Risk Analysis Identification of possible risk is done while risk mitigation strategy is
created and finished
Engineering It comprises testing, creating and installing software at the customer
location
Evaluation Evaluation of software by the client. Also, encompasses identifying and
monitoring risks such as schedule slippage and cost overrun
6. Model suitable for the project:
According to the information presented, the project of Tune Source firm has an initial investment capital and a projected annual
revenue of roughly 2 million USD, therefore this is a large-scale enterprise, supplying packed clients. So, the corporation requires
cautious structure and growth to prevent blunders.
Water fall model is an ancient model that is used a lot in a small project, but the percent of failure in the project is quite high if it
used for large and object-oriented projects. Furthermore, the expense of addressing such faults is too great since we must change
everything from the paperwork to the rationale. Another method, if the software development documentation is not appropriately
finished, the project will most likely go astray while building this product.
V-model also has certain weakness that is not acceptable for our purpose. All needs are known up-front hence this approach
cannot simply handle dynamic changes in requirements. But, V-model does not incorporate risk analysis activities, it is
challenging to manage risk and it has high percent of projects failure.
So, after all reason I prepared, Spiral model is the best because:
- Prioritse the risk: At this moment, offer you a complete analysis of the project and pick where to focus the team's efforts.
Most crucially, it will help the construction of practical solutions for every risk. The project won't be materially disrupted
or delayed as a consequence of the processing time.
- Treat the risk: As soon as the most pressing hazards are identified, an action plan must be devised for risk reduction. As
time goes on and you create a bigger database of past projects and related risk profiles, you will be able to forecast
upcoming hazards and handle them more effectively.
- Monitor the risk: Communication between team members and stakeholders, as well as continual monitoring for prospective
threats, are crucial. And despite though it frequently seems like herding cats, the project's approach to risk management and
threat registers makes it simple to maintain eyes on those change targets. separated from danger.
1. Identify some risks and discuss an approach to manage them
No Risk Possible Cause Consequence Solution
1 Outdated technology 45% Employees are not
trained or lazy to
learn new
technologies
Cannot create
convenient features to
attract users and
compete with other
brands
Always update the
newest and latest
technology
2 Lack of personal 15% Employees are
resigned or fired
Project completed
over time
Prepare more staff
and manage staff to
do task together
3 Lack of budget 10% Covid-19 affect to
source of income
Lack of funds to
develop
Take advantage of
old but highly
effective technologies
to reduce costs
4 Slow progress 15% Unequal distribution
of work
Loss of company
reputation
bind tasks for easy
management as well
as unified opinions
III. Explain the Purpose of a Feasibility Report (P3)
1. Definition of feasibility report
A feasibility study is a report that assesses a group of potential project pathways or solutions to see whether they are feasible. The
individual who writes a feasibility report assesses the feasibility of numerous ideas and then picks their proposal for the best
alternative.
They then give the feasibility study to their firm and make their suggestion
2. Discuss the purpose of conducting a feasibility study
The goal of the feasibility report is to provide the project parameters and explain the prospective solutions to the identified issue,
need, or opportunity. Having brainstormed a variety of potential solutions, the project team expands on each of these potential
solutions, providing sufficient detail, including very high-level costing information, to permit the project leader to recommend to
the approving authority all of the viable potential solutions that should be further analyzed in the next phase (Business Case)
(Business Case). Project restrictions and limitations of spending are among the several criteria that will affect viability
