ASSIGNMENT 01 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 09: Software Development Life Cycle
Submission date Date Received 1st
submission

Re-submission Date Date Received 2nd

submission
Student Name Student ID

Class Assessor name

Student declaration
I certify that the assignment submission is entirely my own wor k and I fully understand the consequences of
plagiarism. I understand that making a false declaration is a for m of malpractice.

Student’s signature
 Grading grid
P1 P2 P3 P4 M1 M2 D1 D2

❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Contents
Introduction..........................................................................................................................................................................
P1. Describe two iterative and two sequential software lifecycle models.......................................................................
1. Waterfall Model :...............................................................................................................................................................
2. V-model:............................................................................................................................................................................
3. Prototyping model.............................................................................................................................................................
4. Throwaway prototyping model.......................................................................................................................................10
5. Agile model.....................................................................................................................................................................11
6. Spiral model:...................................................................................................................................................................12
7. The most suitable model for project................................................................................................................................14
P2. Explain how risk is managed in the Spiral lifecycle model.....................................................................................14
1. Risk assessment:..............................................................................................................................................................14
2. Risk management steps:...............................................................................................................................................14
3. Risk Management Plan ( For example, this Risk management plan is based on a House Building Project )..............17
P3. Explain the purpose of a feasibility report................................................................................................................17
P4 .Describe how technical solutions can be compared..................................................................................................20
Conclusion...........................................................................................................................................................................21
Bibliography.......................................................................................................................................................................21
 List of Figures
Figure 1- Waterfall model ............................................................................................................................................. 6
Figure 2- V-model ......................................................................................................................................................... 8
Figure 3- Prototyping model ......................................................................................................................................... 9
Figure 4- Throwaway prototyping............................................................................................................................... 10
Figure 5- Agile model ................................................................................................................................................. 11
Figure 6- Spiral model ................................................................................................................................................. 13
Figure 7- Identify the risk with example ..................................................................................................................... 15

List of Table
Table 1- Risk Management Plan ................................................................................................................................. 17
 Introduction
Tune Source is a organisation founded in southern California. Tune Source is the
brainchild of 3 marketers with ties to the track industry: John Margolis, Megan
Taylor, and Phil Cooper. Originally, John and Phil partnered to open some of
brick- and-mortar shops in southern California specialising in hard-to-discover and
traditional jazz, rock, country, and folks recordings. Megan quickly became invited
to sign up for the partnership due to her contacts and information of classical track.
Tune Source speedy have become referred to as the area to visit discover
uncommon audio recordings. Annual income final 12 months were $forty million
with annual increase at approximately 3%–5% according to 12 months

P1. Describe two iterative and two sequential software lifecycle

models
*Sequential life cycle model :
1. Waterfall Model :
*The sequential phases in Waterfall model are :

• Requirement Gathering and analysis − The requirements of the system are

captured in this phase and documented in a requirement specification document.
• System Design − The requirement document in first phase are studied in this phase
and the system design is prepared. This system design helps defining the overall
system architecture.
• Implementation − The system is first developed unit functions, which are
integrated in the next phase. Each unit is developed and tested for its functionality,
which is referred to as Unit Testing.
• Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire
system is tested for any faults and failures.
• Deployment of system − Once the functional and non-functional testing is done;
the product is deployed in the customer environment or released into the market.
• Maintenance − There are some issues which come up in the client environment.
To fix those issues, patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the
customer environment. (Martin, 2021)
 Figure 1- Waterfall model

* Advantage:

Development moves from concept, through design, implementation, testing,

installation, troubleshooting, and ends up at operation and maintenance. Each phase of
development proceeds in strict order.
Some of the major advantages of the Waterfall Model are as follows :
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented
(Gaille, 2020)

* Disadvantage:

The major disadvantages of the Waterfall Model are as follows :

• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high risk of
changing. So, risk and uncertainty is high with this process model.
• It is difficult to measure progress within stages.
 • Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.
• Integration is done as a "big-bang. at the very end, which doesn't allow identifying
any technological or business bottleneck or challenges early.
(Martin, 2021)

2. V-model:
2.1. Business requirements:
In this first step, business analysts gathering information about the needs of the
user(client) by interview or meeting. Then the document called the user
requirements is created. The user requirements document describe all information
of the application : the interface, data, security, system ‘s functional, performance.
The users will carefully review this document because it would serve as the
guideline for the system designers in the system design stage. The user acceptance
tests are also designed in this step (Hamilton, 2021).

2.2. System requirements:

After analyze and understand the detailed requirements document, it is the time to
design the complete system. System engineers calculate possibilities and
techniques that can be performed follow the user requirements.If any of the
requirements are inappropriate , the user is notified of the problem.Then the
resolution is suggested and the requirements document is edited after that.In this
step, the application specification document is generated for the development
stage.It contains the general, menu structures, data structures system
organization.The system test plan is developed in this step, the earlier the system
test plan is prepared , the more time for unit testing executed later (Kumar, 2019).

2.3. High level design (Architecture design)

Based on the technical and financial possibility , software architects would realize
the system design by broken down it into modules taking up different
functionality, brief functionality of each module, their interface relationships,
dependencies, database tables, architecture diagrams, technology details . The
integration tests would be designed in this stage (Rajkumar, 2016).

2.4. Low level design ( Module design)

In this steps , the designed system is broken up into smaller modules with the very
specification details so the developers can start coding .The module design
document will contain a detailed functional of the modules :
 + All elements of the database tables.
+ All interface details with complete API references.
+All dependency issues
+ Error message listings
It is very important that the module designed is appropriate with the other modules
in the system construction and the the other external systems.The unit tests can be
developed in this stage based on the internal module designs (Rajkumar, 2016).

Figure 2- V-model

*Advantage:
• This is a highly-disciplined model and Phases are completed one at a time.
• Works well for smaller projects where requirements are very well understood.
• Simple and easy to understand and use.
• Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
(Thakur, 2020)
*Disadvantage:
• High risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high risk of
changing (Naveen, 2015).
3. Prototyping model
Software prototyping is the activity of creating prototypes of software
applications, i.e., incomplete versions of the software program being
developed. It is an activity that can occur in software development and is
comparable to prototyping as known from other fields, such as mechanical
engineering or manufacturing (Lewis, 2015).
 Figure 3- Prototyping model

*Advantage:

• Users are actively involved in the development

• Since in this methodology a working model of the system is provided, the users
get a better understanding of the system being developed.
• Errors can be detected much earlier.
• Quicker user feedback is available leading to better solutions.
• Missing functionality can be identified easily
(Prasanna, 2021)

*Disadvantage:
• Leads to implementing and then repairing way of building systems.
• Practically, this methodology may increase the complexity of the system as scope
of the system may expand beyond original plans.
• Incomplete application may cause application not to be used as the full system was
designed incomplete or inadequate problem analysis

(Sparrow, 2012)

4. Throwaway prototyping model

Throwaway or rapid prototyping refers to the creation of a model that will
eventually be discarded rather than becoming part of the final delivered software.
When this goal has been achieved, the prototype model is 'thrown away', and the
system is formally developed based on the identified requirements (Vennapoosa,
2013).
 Figure 4- Throwaway prototyping

*Advantage:
• you reduce risk in a project by quickly stepping through the initial
development phases.
• you are selecting (or at least you better be) a prototyping language or
framework that allows you to rapidly development your application and meet
your prototyping goals.
• you can usually select a programming language that lends itself to being
thrown away – further reducing the incentive to try and “make it work’. Yes,
programmers and companies can easily be “hoarders” if they are not careful.
• The last primary benefit, is that it is in-itself an agile development exercise
for the participants and stakeholders in a project that helps define goals,
realize potential pitfalls and generate better risk assessment or the project as a
whole
(Juan, 2020)
*Disadvantage:
• You have to commit time and resources to actually undertake this effort.
• You may not be using the prototyping time to maximum efficiency, however,
throwaway prototyping doesn’t mean you throw and bunch of things at a wall
(metaphorically speaking) and see if they stick. This is not a reason to not
have a well thought out plan and execute according to the goals you want to
achieve
(Lewis, 2015)

5. Agile model
Agile modeling is a methodology for modeling and documenting software systems
based on best practices. It is a collection of values and principles, that can be
applied on an software development project (Long, 2018).

Figure 5- Agile model

*Advantage:
 • Customer satisfaction by rapid, continuous delivery of useful
software.
• People and interactions are emphasized rather than process and tools. Customers,
developers and testers constantly interact with each other.
• Working software is delivered frequently (weeks rather than months).
• Face-to-face conversation is the best form of communication.
• Close, daily cooperation between business people and developers.
• Continuous attention to technical excellence and good design.
• Regular adaptation to changing circumstances.
• Even late changes in requirements are welcomed
(Shamil, 2021)

*Disadvantage:

• In case of some software deliverables, especially the large ones, it is difficult to

assess the effort required at the beginning of the software development life cycle.
• There is lack of emphasis on necessary designing and documentation.
• The project can easily get taken off track if the customer representative is not clear
what final outcome that they want.
• Only senior programmers are capable of taking the kind of decisions required
during the development process. Hence it has no place for newbie programmers,
unless combined with experienced resources.

(Naveen, 2015)
6. Spiral model:
The spiral model has four phases. A software project repeatedly passes through these
phases in iterations called Spirals.

6.1. Identification
This phase starts with gathering the business requirements in the baseline spiral. In the
subsequent spirals as the product matures, identification of system requirements,
subsystem requirements and unit requirements are all done in this phase.
This phase also includes understanding the system requirements by continuous
communication between the customer and the system analyst. At the end of the spiral,
the product is deployed in the identified market (Martin, 2021).
6.2. Design
The Design phase starts with the conceptual design in the baseline spiral and involves
architectural design, logical design of modules, physical product design and the final
design in the subsequent spirals. (Gurendo, 2015).
6.3. Construct or Build
 The Construct phase refers to production of the actual software
product at every spiral. In the baseline spiral, when the product is just
thought of and the design is being developed a POC (Proof of Concept) is developed in
this phase to get customer feedback.
Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These
builds are sent to the customer for feedback (Naveen, 2015).
6.4. Evaluation and Risk Analysis
Risk Analysis includes identifying, estimating and monitoring the technical feasibility
and management risks, such as schedule slippage and cost overrun. After testing the
build, at the end of first iteration, the customer evaluates the software and provides
feedback.
The following illustration is a representation of the Spiral Model, listing the activities in
each phase.
Based on the customer evaluation, the software development process enters the next
iteration and subsequently follows the linear approach to implement the feedback
suggested by the customer. The process of iterations along the spiral continues
throughout the life of the software (Sparrow, 2012).

Figure 6- Spiral model

*Advantage:
• Changing requirements can be accommodated.
• Allows extensive use of prototypes.
• Requirements can be captured more accurately.
• Users see the system early.
• Development can be divided into smaller parts and the risky parts can be
developed earlier which helps in better risk management
(Gurendo, 2015)
*Disadvantage:
 • Management is more complex.
• End of the project may not be known early.
• Not suitable for small or low risk projects and could be expensive for small
projects.
• Process is complex
• Spiral may go on indefinitely.
• Large number of intermediate stages requires excessive documentation.
(Anon., 2019)

7. The most suitable model for project

Following an examination of the project's various models, the waterfall model
appears to be the best fit for the Tune Source project. It satisfies practically all of
the project's requirements. Because the Tune Source project's requirements are
explicit, the waterfall model allows the project to be developed step by step
without the need to change the system.
Furthermore, this approach is simple to use and comprehend the various stages that
must be completed.

P2. Explain how risk is managed in the Spiral lifecycle model.

An effective risk management process is an important component of a successful IT
security program. .The risk management process should not be treated primarily as a
technical function carried out by the IT experts who operate and manage the IT
system, but as an essential management function of the organization. The principal
goal of an organization‘s risk management process should be to protect the
organization and its ability to perform their objectives. (Spiral model: the risk-driven
software development process model, 19)

1. Risk assessment:
Risk assessment is the first process in the risk management methodology.Using
risk assessment to determine the extent of the potential threat and the resulting
impact of that adverse event on the organization. Consequence is the level of
impact that the potential risk event can have on the achievement of business
objectives..5 level rating scale in the risk survey including : 25-Almost Certain,
20-likely, 15-Possible, 10-Unlikely, 5-Rare (Kirkpatrick, 2018).
 2. Risk management steps:

a) Indentify the risk:

• Anticipating possible pitfalls of a project doesn't have to feel like

gloom and doom for your organization. Quite the opposite.
Identifying risks is a positive experience that your whole team can
take part in and learn from.
• Leverage the collective knowledge and experience of your entire
team. Ask everyone to identify risks they've either experienced
before or may have additional insight about. This process fosters
communication and encourages cross-functional learning.

Figure 7- Identify the risk with example

• Use a risk breakdown structure to list out potential risks in a project

and organize them according to level of detail, with the most
highlevel risks at the top and more granular risks at the bottom. This
visual will help you and your team anticipate where risks might
emerge when creating tasks for a project.

b) Analyze the risk

• Once your team identifies possible problems, it's time to dig a little
deeper.
 • During this step, your team will estimate the probability and fallout
of each risk to decide where to focus first. Factors such as potential
financial loss to the organization, time lost, and severity of impact
all play a part in accurately analyzing each risk.
• By putting each risk under the microscope, you’ll also uncover any
common issues across a project and further refine the risk
management process for future projects.

c) Prioritize the risk

• Now prioritization begins. Rank each risk by factoring in both its
likelihood of happening and its potential effect on the project.
• This step gives you a holistic view of the project at hand and
pinpoints where the team's focus should lie. Most importantly, it’ll
help you identify workable solutions for each risk.
• This way, the project itself is not interrupted or delayed in
significant ways during the treatment stage.

d) Treating the risk

• Once the worst risks come to light, dispatch your treatment plan.
Starting with the highest priority risk first, task your team with
either solving or at least mitigating the risk so that it’s no longer a
threat to the project
• Effectively treating and mitigating the risk also means using your
team's resources efficiently without derailing the project in the
meantime.
• As time goes on and you build a larger database of past projects
and their risk logs, you can anticipate possible risks for a more
proactive rather than reactive approach for more effective
treatment.

e) Monitoring the risk

• Not all risks can be eliminated – some risks are always present.
• Under manual systems monitoring happens through diligent
employees. These professionals must make sure that they keep a
close watch on all risk factors. Under a digital environment, the
risk management system monitors the entire risk framework of the
organization.
• If any factor or risk changes, it is immediately visible to everyone.
Computers are also much better at continuously monitoring risks
than people. Monitoring risks also allows your business to ensure
continuity.
 • And more importantly, clear communication among your team and
stakeholders is essential when it comes to ongoing monitoring of
potential threats.
(Montgomery, 2020)

3. Risk Management Plan ( For example, this Risk management plan is based on a
House Building Project )

Risk Description Risk Analysis

Case Description Cause Consequences Likelihood Impact Risk

ranking
Insufficient care The house
1 Not stable foundation during might Possible Major Extreme
preparation collapse
during heavy
weather
Insufficient care Broken fence
2 Stiffed fence during may ruin Possible Moderate Moderate
preparation appearance of
the house
Insufficient care Cause bad
3 Poor ventilation during smell all Possible Major Moderate
preparation around the
house
Insufficient care May cause
4 Bad paint job during owner to be Possible Moderate Moderate
preparation unhappy

Not enough lighting Insufficient care Hard to

5 around the house during identify the Possible Moderate Moderate
preparation house when
dark

Table 1- Risk Management Plan

P3. Explain the purpose of a feasibility report.
1. Purpose of Feasibility Study
• The purpose of a feasibility study is to analyze a business proposal to
determine if the project is viable and if it should be followed through with.
Determining if a business is feasible prior to establishing it prevents an
investor from wasting money and time on a failed business venture .
• A feasibility study is conducted in the idea stage of planning a business. It
is not to be confused with a business plan. A business plan is only created
after a feasibility study is conducted and a decision is made to move
forward with the business (Maycock, 2019).

2. Applying Feasibility Criteria to the Project

2.1. Technical Feasibility

This assessment focuses on the technical resources available to the
organization. It helps organizations determine whether the technical
resources meet capacity and whether the technical team is capable of
converting the ideas into working systems. Technical feasibility also
involves the evaluation of the hardware, software, and other technical
requirements of the proposed system. As an exaggerated example, an
organization wouldn’t want to try to put Star Trek’s transporters in their
building—currently, this project is not technically feasible (Simplilearn,
2021).

2.2. Economic Feasibility

This assessment typically involves a cost/ benefits analysis of the project,
helping organizations determine the viability, cost, and benefits
associated with a project before financial resources are allocated. It also
serves as an independent project assessment and enhances project
credibility—helping decision-makers determine the positive economic
benefits to the organization that the proposed project will provide
(Osarome, 2011).

2.3. Operational Feasibility

This assessment involves undertaking a study to analyze and determine
whether—and how well—the organization’s needs can be met by
completing the project. Operational feasibility studies also examine how a
project plan satisfies the requirements identified in the requirements
analysis phase of system development (Osarome, 2011).
 3,. Technical solution
Although self-sufficiency, according to the article, will require more
resources than hiring an outside vendor or developer, the goal
remains the same: to construct a system for the project. However,
compromise is unavoidable when it comes to information security
challenges
• Custom development
The ideal way to develop a system is to start from scratch because it
gives you complete control over how the system and its functions
work. If the corporation wants a Web that is tightly tied to its
existing CD sales system, the project will be complex and require a
high degree of knowledge. Furthermore, TS can work in a technical
environment that has standard technologies and the appropriate
assistance. Creating a highly responsive system from the start might
thus be quite effective (Jain, 2017).

• Package Software
There are many commercial software programs available to serve
different purposes. In other words, multi- purpose development
companies instead of developing their own applications, they use
written packaging software. They will quickly be installed and
areusually contributed by the experts created (Hope, 2019).
P4 .Describe how technical solutions can be compared.
An alternative matrix can be used to organize the pros and cons of the design
alternatives so that the best solution will be chosen in the end. This matrix is created
using the same steps as the feasibility analysis. The only difference is that the alternative
matrix combines several feasibility analyses into one matrix so that the alternatives can
easily be compared. An alternative matrix is a grid that contains the technical, budget,
and organizational feasibilities for each system candidate. Sometimes weights are
provided for different parts of the matrix to show when some criteria are more important
to the final decision.To create the altrnative matrix, draw a grid with the alternatives
across the top and different criteria (feasibilities, pros, cons,…) along the side. Next, fill
in the grid with detailed descriptions about each alternative. This becomes a useful
document for discussion because it clearly presents the alternatives being reviewed and
comparable characteristics for each one.
 Conclusion
Here is the full report about how to developing a project. This project will let customers
be able to search for and purchase digital music downloads. All about SDLC model,
risk management process/matrix or feasibility study has been clearly presented so that
customers can better understand about Tune Source.

Bibliography
Anon., 2019. What’s Spiral Model? Advantages and Disadvantages. [Online]
Available at: testbytes.net/blog/spiral-model-advantages-and-disadvantages/ [Accessed
20 May 2019].
Gaille, L., 2020. 15 Advantages and Disadvantages of a Waterfall Model. [Online] Available
at: https://vittana.org/15-advantages-and-disadvantages-of-a-waterfall-model [Accessed 19
March 2020].
Gurendo, D., 2015. Software Development Life Cycle (SDLC). Spiral Model. [Online] Available
at: https://xbsoftware.com/blog/software-development-life-cycle-spiral-model/ [Accessed 26
October 2015].
Hamilton, T., 2021. V-Model in Software Testing. [Online]
Available at: https://www.guru99.com/v-model-software-testing.html [Accessed
8 October 2021].
Hope, C., 2019. Packaged software. [Online]
Available at: https://www.computerhope.com/jargon/p/packsoft.htm [Accessed
30 September 2019].
 Jain, S., 2017. What Is Custom Software
Development?. [Online] Available at:
https://dzone.com/articles/custom-software-
development-3 [Accessed 25 February 2017].
Juan, 2020. PROS AND CONS OF PROTOTYPING COMPLEX PROJECTS. [Online]
Available at: https://qpsoftware.net/blog/pros-and-cons-prototyping-complex-projects [Accessed
28 March 2020].
Kirkpatrick, J., 2018. What is a Risk Assessment? – Learn The 5 Steps to a Risk Assessment. [Online] Available
at: https://kirkpatrickprice.com/video/what-is-risk-assessment-five-steps-to-a-risk-assessment/ [Accessed 27
March 2018].
Kumar, 2019. Software Engineering | SDLC V-Model. [Online]
Available at: https://www.geeksforgeeks.org/software-engineering-sdlc-v-model/ [Accessed
21 May 2019].
Lewis, S., 2015. Prototyping Model. [Online]
Available at: https://searchcio.techtarget.com/definition/Prototyping-Model
Long, S., 2018. What is the Agile SDLC Model? – Phases and Methodology. [Online]
Available at: https://7t.co/blog/what-is-the-agile-sdlc-model-phases-and-methodology/
Martin, M., 2021. Spiral Model: When to Use? Advantages & Disadvantages. [Online]
Available at: https://www.guru99.com/what-is-spiral-model-when-to-use-advantages-disadvantages.html
[Accessed 7 october 2021].
Martin, M., 2021. What is Waterfall Model in SDLC? Advantages and Disadvantages. [Online]
Available at: https://www.guru99.com/what-is-sdlc-or-waterfall-model.html [Accessed 7
October 2021].
Maycock, S., 2019. What Is The Purpose Of Conducting A Feasibility Study?. [Online]
Available at: https://www.vickeryholman.com/news/what-is-the-purpose-of-conducting-a-feasibility-study/
[Accessed 24 September 2019].
Montgomery, O., 2020. Follow the 5 Steps of the Risk Management Process to Build a Plan for Your Business.
[Online]
Available at: https://www.softwareadvice.com/resources/5-steps-of-the-risk-management-process/
[Accessed 9 October 2020].
Osarome, 2011. 1. TECHNICAL FEASIBILITY 2. OPERATIONAL FEASIBILITY 3. ECONOMIC FEASIBILITY.
[Online]
Available at: https://osarome.blogspot.com/2011/10/1-technical-feasibility-2-operational.html [Accessed
7 october 2011].
Prasanna, 2021. Advantages and Disadvantages of Prototype Model | Prototyping Model in Software Engineering for
Testing. [Online]
Available at: aplustopper.com/advantages-and-disadvantages-of-prototype-model/ [Accessed
17 August 2021].
Rajkumar, 2016. V Model in Software Development Life Cycle. [Online]
Available at: https://www.softwaretestingmaterial.com/v-model-in-sdlc/
[Accessed 18 April 2016].
Shamil, F. R., 2021. Advantages and disadvantages of Agile Model SDLC. [Online]
Available at: https://t4tutorials.com/agile-model-in-software-engineering-agile-model-advantages-
anddisadvantages/
[Accessed 14 September 2021].
Simplilearn, 2021. Feasibility Study And Its Importance in Project Management. [Online]
Available at: https://www.simplilearn.com/feasibility-study-article [Accessed 23 jun
2021].
Sparrow, P., 2012. Prototype Model: Advantages and Disadvantages. [Online]
Available at: https://www.ianswer4u.com/2011/11/prototype-model-advantages-and.html
Thakur, D., 2020. What is V-model ? Advantages and Disadvantages of V Model.. [Online]
Available at: https://ecomputernotes.com/software-engineering/v-model
Vennapoosa, C., 2013. Throwaway Prototyping Model. [Online]
Available at: http://www.exforsys.com/career-center/project-management-life-cycle/throwaway-
prototypingmodel.html
[Accessed 14 January 2013].