Software Development Life Cycle

Name: Phạm Nguyễn Tuấn Anh

Class: GCS190538

1
 ASSIGNMENT 01 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 09: Software Development Life Cycle
Date Received 1st
Submission date
submission
Date Received 2nd
Re-submission Date
submission
Student Name Pham Nguyen Tuan Anh Student ID GCS190538

Class GCS0903B Assessor name Thai Thanh Thao

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

Grading grid
P1 P2 P3 P4 M1 M2 D1 D2

❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

2
Signature & Date:

Assignment Brief 01 (RQF)

Higher National Certificate/Diploma in Business

Student Name/ID Number: Pham Nguyen Tuan Anh / GCS190538

Unit Number and Title: Unit 09: Software Development Life Cycle

Academic Year:

Unit Assessor:

Assignment Title: Plan a software development life cycle

Issue Date: 07/12/2020

Submission Date:

Internal Verifier Name:

Date:

Submission Format:

Format:
● The submission is in the form of 1 document.
● You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3 and
margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation and
references must follow the Harvard referencing style.
Submission:
● Students are compulsory to submit the assignment in due date and in a way requested by the
Tutor.
● The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/.
● Remember to convert the word file into PDF file before the submission on CMS.
Note:

3
 ● The individual Assignment must be your own work, and not copied by or from another student.
● If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you
must reference your sources, using the Harvard style.

● Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to comply
this requirement will result in a failed assignment.

Unit Learning Outcomes:

LO1 Describe different software development lifecycles.

LO2 Explain the importance of a feasibility study.

Assignment Brief and Guidance:

Assignment scenario
Tune Source is a company headquartered in southern California. Tune Source is the brainchild of three
entrepreneurs with ties to the music industry: John Margolis, Megan Taylor, and Phil Cooper.
Originally, John and Phil partnered to open a number of brick-and-mortar stores in southern California
specialising in hard-to-find and classic jazz, rock, country, and folk recordings. Megan soon was
invited to join the partnership because of her contacts and knowledge of classical music. Tune Source
quickly became known as the place to go to find rare audio recordings. Annual sales last year were $40
million with annual growth at about 3%–5% per year. Tune Source currently has a website that enables
customers to search for and purchase CDs. This site was initially developed by an Internet consulting
firm and is hosted by a prominent local Internet Service Provider (ISP) in Los Angeles. The IT
department at Tune Source has become experienced with Internet technology as it has worked with the
ISP to maintain the site.

System Request
Project Sponsor: Carly Edwards, Assistant Vice President, Marketing.
Business Need: This project has been initiated to increase sales by creating the capability of selling
digital music downloads to customers through kiosks in our stores, and over the Internet using our
website.
Business Requirements: Using the Web or in-store kiosks, customers will be able to search for and
purchase digital music downloads. The specific functionality that the system should have includes the
following:
● Search for music in our digital music archive.
● Listen to music samples.
● Purchase individual downloads at a fixed fee per download.
● Establish a customer subscription account permitting unlimited downloads for a monthly fee.
● Purchase music download gift cards.

4
Business Value: We expect that Tune Source will increase sales by enabling existing customers to
purchase specific digital music tracks and by reaching new customers who are interested in our unique
archive of rare and hard-to-find music. We expect to gain a new revenue stream from customer
subscriptions to our download services. We expect some increase in cross-selling, as customers who
have downloaded a track or two of a CD decide to purchase the entire CD in a store or through our
website. We also expect a new revenue stream from the sale of music download gift cards.
Conservative estimates of tangible value to the company include the following:
● $757,500 in sales from individual music downloads.
● $950,000 in sales from customer subscriptions.
● $205,000 in additional in-store or website CD sales.
● $153,000 in sales from music download gift cards.

Special Issues or Constraints:

● The marketing department views this as a strategic system. The ability to offer digital music
downloads is critical in order to remain competitive in our market niche. Our music archive of
rare and hard-to-find music is an asset that is currently underutilized.
● Many of our current loyal customers have been requesting this capability, and we need to
provide this service or face the loss of these customers’ business.
● Because customers have a number of music download options available to them elsewhere, we
need to bring this system to the market as soon as possible.

Tasks
Complete the following tasks:
Task 1 – SDLC model
You are a project manager of a company named ABC. Your company has been hired by Tune Source to
carry out a project that helps them develop a software for the requirements specified in the system
request. As the first step, you need to:
1. Describe the following SDLC models: waterfall, v-model, prototyping, scrum and spiral. Choose
one that you think suitable for the project and explain why.
● 350 - 500 words for each model.
● Explanation: 400 – 600 words.

Discuss the suitability of each of the SDLC models for the project. For each model, specify whether
it is most, moderately or least suitable.
● Word limit: 800 - 1000 words.

Discuss the merits of applying the waterfall model to a large software development project.
● Word limit: 800 – 1200 words.

5
2. Identify some risks and discuss an approach to manage them.
You will have the present what is Risk Management process with clear illustrations and
explanations.
Then you will create a Risk Management Matrix to assess and manage risks of Tune Source
project.

● Word limit: 600 – 1000 words.

Task 2 – Feasibility study

1. Discuss the purpose of conducting a feasibility study for the project.

● Word limit: 400 – 600 words.

2. Discuss how the three feasibility criteria (technical, economic, organizational) are applied to the
project. Discuss whether the project is feasible.
Discuss alternative technical solutions using the alternative matrix.
● Word limit: 1200 – 1500 words.

3. Explain the components of a feasibility report.

Discussion economic feasibility study on Tune Source project (NPV, Cashflow, Break-Even Point)
● Word limit 350 – 500 words.

Discussion organizational feasibility study on Tune Source project

● Word limit 350 – 500 words.

4. Assess the impact of each feasibility criterion on a software investigation.

Discussion and represent as feasibility alternatives matrix for Tune Source project
● Word limit: 500 – 700 words.

6
Learning Outcomes and Assessment Criteria (Assignment 01):
Learning Outcome Pass
P1 Describe two
iterative and two
sequential software
LO1 Describe different
lifecycle models.
software development
lifecycles P2 Explain how risk is
managed in the Spiral
lifecycle model.
P3 Explain the purpose
of a feasibility report.
LO2 Explain the
importance of a P4 Describe how
feasibility study technical solutions can
be compared.
7
Merit Distinction
M1 Describe, with an
D1 Assess the merits of
example, why a
applying the Waterfall
particular lifecycle
lifecycle model to a
model is selected for a
large software
development
development project.
environment.
D2 Assess the impact of
M2 Discuss the
different feasibility
components of a
criteria on a software
feasibility report.
investigation.
ASSIGNMENT 01 FRONT SHEET 2

Assignment Brief 01 (RQF) 3

Introduction 9

Describe predictive and adaptive software development models that consider at least two
iterative and two sequential models. 9

Software Development Cycle (SDLC) 9

Iterative Models 10
Prototype Model 10
Sequential models 12
Waterfall Model 12

Risks in Software Development Life Cycle 14

RISK MANAGEMENT MATRIX OF TUNE SOURCE PROJECT 15

FEASIBILITY STUDY 16

REFERENCES 17

8
 Introduction

Tune Source is a company headquartered in southern California. Tune Source is the brainchild of three
entrepreneurs with ties to the music industry: John Margolis, Megan Taylor, and Phil Cooper. Tune
Source quickly became known as the place to go to find rare audio recordings. Annual sales last year
were $40 million with annual growth at about 3%–5% per year. Tune Source currently has a website that
enables customers to search for and purchase CDs. This site was initially developed by an Internet
consulting firm and is hosted by a prominent local Internet Service Provider (ISP) in Los Angeles. The IT
department at Tune Source has become experienced with Internet technology as it has worked with the
ISP to maintain the site. This project has been initiated to increase sales by creating the capability of
selling digital music downloads to customers through kiosks in our stores, and over the Internet using our
website.

Describe predictive and adaptive software development models that consider at least two iterative
and two sequential models.

Software Development Cycle (SDLC)

The software development life cycle (SDLC) is a flowchart that lays out the tasks that must be completed
at each stage of the software development process. Within a software company, the SDLC is a design
process that a development team follows.
It comprises a detailed plan for developing, maintaining, and replacing specific software. The life cycle is
a mechanism for enhancing software quality and the development process as a whole.

9
Iterative Models

Prototype Model

A prototyping model is a systems development process in which a prototype (an early

estimate of a complete system or product) is produced, tested, and tweaked as needed
until an acceptable prototype is obtained, from which the whole system or product can
now be developed.

The following steps give a brief description about the Spiral model phases:
Step 1: Gathering and analysing requirements
A requirement analysis is the first step in a prototyping model. The system's requirements are defined in
depth during this phase. Throughout the process, users of the system are interviewed to learn what they
anticipate from it.
Step 2: Quick design
A preliminary design, sometimes known as a fast design, is the second phase. A simple system design is
created at this stage. It is, however, not a complete design. It gives the user a quick overview of the
system. The prototype development is aided by the rapid design.
Step 3: Build a Prototype
The information acquired during rapid design is used to create an actual prototype in this phase. It's a
scaled-down version of the required system.
Step 4: Initial user assessment
The proposed system is submitted to the client for an initial evaluation at this stage. It aids in determining
the working model's strengths and weaknesses. Customer feedback and recommendations are gathered
and forwarded to the developer.
Step 5: Fine-tuning the prototype
If the user is dissatisfied with the present prototype, you must improve it based on the user's feedback and
suggestions.
This phase will not be completed until all of the user's needs have been met. A final system is produced
based on the approved final prototype once the user is pleased with the developed prototype.

10
Step 6: Implement and Maintain the Product
The final system is thoroughly tested and deployed to production when it is developed based on the final
prototype. Routine maintenance is performed on the system to save downtime and prevent large-scale
failures.

Advantages Disadvantages

➔ The lack of functionality is immediately ➔ It's a time-consuming process because the

discernible.
➔ As a result, the development team and the
customer have a clear understanding of the
requirements and the product's output.
➔ Customer satisfaction is possible in this
situation.
➔ The prototype can be used again during the
design phase and for similar applications.
➔ Customer rejection is lower in this model
than in other models.
➔ Early detection of problems is possible.
prototype can be changed by the buyer.
➔ It will also waste our time by altering the
dummy (prototype) often, which will cause
the real project to be delayed.
➔ Although there is no requirement review,
there is a prototype review.
➔ Because there are no parallel deliverables,
the two teams are unable to collaborate.
➔ It's possible that the partial application will
cause the software to be utilised differently
than it was intended.
➔ Inadequate or incomplete problem
analysis.
➔ We may also lose the interest of customers
if they are dissatisfied with the final
product or prototype.

Spiral Model
The spiral model is a risk-detection pattern with a directed pattern. The spiral model, which is based on
particular risk models, aids the development team in increasing the model's efficiency by removing the
majority of the potential dangers. The software development life cycle includes numerous spiral loops in

each.

The following steps give a brief description about the Spiral model phases:

11
1. Planning: During this phase, customers and system analysts communicate continuously to gain a better
grasp of the system needs.
2. Risk Analysis: During this phase, a procedure is followed to identify risk and potential alternatives. At
the end of this phase, a prototype is created.
3. Development/Engineering: This phase involves the creation of software as well as testing.

4. Evaluation Phase: This phase allows the customer to assess the project's output before moving on to the
following spiral or round.

Advantages Disadvantages

➔ The development process moves quickly. ➔ It is prohibitively expensive for smaller

➔ All stages of development are under projects.

control. ➔ Because there are intermediary steps, the

➔ Customer feedback is taken into account, requirements documentation may be

and modifications are made as quickly as extensive.

feasible. ➔ The risk analysis step necessitates the use

➔ Many new features are being added in a of an expert authority.

systematic manner. ➔ There's a good probability you won't make

➔ Ideal for large-scale, high-risk projects. the deadline or stick to the budget.

➔ Risk management is aided by continuous ➔ Spiral model protocol must be properly

assessment. followed for effective delivery.

➔ It's the best model for situations where

requirements change frequently.

Sequential models
Waterfall Model
The waterfall model for software development is one of the most established and widely
used software development approaches. This life cycle approach is commonly referred to as the
"traditional" way of developing software. This model depicts the software development process
as a linear sequential flow, with each phase beginning only after the previous phase has been

12
completed. This method of development does not specify how to return to a prior phase to
address changes in requirements.

The following steps give a brief description about the waterfall process:
1. Discovery: From the customer needs, the team compiles a comprehensive list of
requirements for the entire project.
2. Design: Software architects decide how the application will be built and how it will function.
3. Coding: Developers put the design into action according to the specifications.
4.Testing: QA engineers look for bugs and inconsistencies throughout the entire codebase.
5.Deployment: Developers put the final product together and organise a demo for stakeholders.
6.Maintenance: The team assists users and fixes bugs that they find.

Advantages Disadvantages

➔ Easy to use, simple to use. ➔ All criteria must be identified in

➔ Easy to structure and manage because of
the rigidity of the model
➔ Milestones requirements are well
understood, suitable for small projects.
➔ Easy to control and manage employee
plans to save time.
➔ Testing is easier because it can refer to the
advance.
➔ Each phase's deliverables are deemed
fixed, which limits flexibility.
➔ Can provide the sense of progress
when it isn't.
➔ Iterations of phases do not reflect the
problem-solving nature of software
development.

13
 situations defined in the specification. ➔ At the end of the day, integration is a
big bang.

Risks in Software Development Life Cycle

A possible problem that may or may not emerge in the future is referred to as a risk. It's usually
caused by a lack of knowledge, control, or time. A software risk is the chance of sustaining a
loss throughout the software development process. Anything can result in a loss, such as a rise
in production costs, the development of low-quality software, or the inability to complete the
project on time. These kinds of hazards occur in our project or developing system since the
future is unclear, and there are numerous unknown and known facts that we can't include in the
project plan.

❖ Risks involved in Prototype Model

Apart from the benefits, prototyping models have their own hazards. The greatest risk is that
everybody interested in the project will decide if the final product is nearly ready or not after
seeing a functional prototype. Another risk of adopting prototype models is that end users will
demand delivery of the genuine system after seeing the early prototype, even if he is unhappy with
the first produced prototype. Without good management, the iterative process of prototype
refinement can take a long time when employing this approach in the software development
process, and developers may wind up with sub-optimal solutions if they rush to produce a
prototype. In practice, utilizing this strategy may raise the system's complexity because
the system's scope may go beyond the initial software development plans. As this
strategy leads to adopting and then correcting the software development process, there
are a number of risks to be aware of.

❖ Risks involved in Waterfall model

Because software development involves very few client encounters and products can
only be demoed once they are ready, the cost of addressing such flaws is very expensive
once the software is built, and we must update everything from the documents to the
logic. Another concern is that if software development documentation isn't done properly,
there's a good chance of getting off track while developing software. When needs are at
a moderate to high risk of altering, there is always a lack of project fit when employing

14
 this approach. If we utilize this paradigm for complicated and object-oriented projects,
there is a substantial risk of project failure.

❖ Risks involved in V-model

Because it is too simplistic to correctly reflect the software development process, it might
lull managers into complacency. The V-Model is based on a project management
approach to software development, and it is designed for project managers, accountants,
and lawyers, not software developers or users. Although novices can grasp it quickly,
such understanding is only beneficial if the novice goes on to learn more about the
development process and how the V-Model must be developed and extended in practice.
It is rigid and linear in its approach to software development, and it has no intrinsic ability
to adjust to change.

RISK MANAGEMENT MATRIX OF TUNE SOURCE PROJECT

RISK Impact Action plan

Loss of key member workforce medium ➔ Hiring third party

➔ Increase the salary for
the remaining employees
➔ Recruiting new members
for the project

15
Project team members conflict
low ➔ Set up team building
before expected
➔ Leader leader explains
conciliation, or tough
closing.

TTechnology is not enough to medium ➔ Increase technology

meet market demand knowledge with
employees
➔ There is a need for a
system improvement
maintenance schedule

Lost data medium ➔ Backup data regularly

Lose a source of money high ➔ Find an alternative

source
➔

System security: customer high ➔ Create firewall

information leaks, the system is ➔ System data encryption
hacked by hackers

FEASIBILITY STUDY

PURPOSE OF CONDUCTING FEASIBILITY STUDY

❖ Determine whether a project is viable and can be implemented successfully to avoid
wasting money and manpower.
❖ Establish the product or development standards that the user will accept.

THREE FEASIBILITY CRITERIA

1.TECHNICAL FEASIBILITY
● The following concerns are taken into account when determining technological feasibility.
● Whether or not the necessary technology is available
● Whether or not the resources required are available -
● Programmers, testers, and debuggers are all needed.
● Hardware and software
● Once the technical viability has been verified, the financial aspects must be considered.

16
 2. Economic Feasibility
Consider whether the software is required to produce a profit for the company.
Costs incurred when purchasing a product, as well as the actions required to
develop software.
3. ORGANISATIONAL FEASIBILITY

To address business problems and user needs, go through a number of software

evaluation procedures.
Determines whether the user's request contains high-priority issues.
Whether or if a user adjusts to new software.
Determine whether the development team's suggestions are satisfactory to the
organisation.
Determine whether or not the solutions given by the software team are acceptable.

REFERENCES
Dennis, A. and Haley, W. (2009) Systems Analysis and Design. John Wiley & Sons Ltd.
IJCSI International Journal of Computer Science Vol. 7, Issue 5, September 2010 “A
Comparison Between Five Models Of Software Engineering”
IJCSI International Journal of Computer Science Vol. 6, Issue 1, 2015 “Software Development
Life Cycle Models – Comparison, Consequences”
Craig Larman, Victor R. Basili (June 2003). "Iterative and Incremental Development: A Brief
History
Aras, O, Barbara, C, & Jeffrey, L. (2008). Secure software development-the role of it audit.
Information Systems Control Journal, 4.
Dowd, M, McDonald, J, & Schuh, J. (2007). The art of software security assessment. Boston,
MA: Pearson Education, Inc.

17