ASSIGNMENT 1 BRIEF

Qualification BTEC Level 5 HND Diploma in Computing

Unit number Unit 9: Software Development Life Cycle

Assignment title Planning a Software Development Lifecycle

Academic Year 2019 – 2020

Unit Tutor Thai Thi Thanh Thao

Issue date 28th September 2020 Submission date 12th October 2020

IV name and date

Submission Format:
Format: The submission is in the form of 1 document
You must use font Calibri size 12, set number of the pages and use multiple line spacing at
1.3. Margins must be: left: 1.25 cm; right: 1 cm; top: 1 cm and bottom: 1 cm. The reference
follows Harvard referencing system.
Submission Students are compulsory to submit the assignment in due date and in a way requested by
the Tutors. The form of submission will be a soft copy posted on
http://cms.greenwich.edu.vn/
Note: The Assignment must be your own work, and not copied by or from another student or from
books etc. 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 know how to reference
properly, and that understand the guidelines on plagiarism. If you do not, you definitely get failed

Unit Learning Outcomes:

LO1 Describe different software development lifecycles

LO2 Explain the importance of a feasibility study
Assignment Brief and Guidance:

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 specializing
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

Page 1
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.
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.
You need to discuss the following Tasks:

Page 2
Task 1
You are a project manager of ABC company. Your company now collaborating with Tune Source to
complete the project. You have to create a report about SDLC models which could be used in Tune
Source. You report should contain the following content:
Describe 4 SDLC models: Waterfall, V-Model, Spiral, Rapid Development. Which method is best for Tune
Source and why?
Your report also should list some risks and offer an approach to manage risks.
Task 2
Discuss why a team need to conduct feasibility study and what areas should be conducted in feasibility
study?

Page 3
Learning Outcomes and Assessment Criteria

Pass Merit Distinction

LO1 Describe different software development lifecycles

P1 Describe two iterative and M1 Describe, with an example, D1 Assess the merits of applying
two sequential software why a particular lifecycle model the Waterfall lifecycle model to a
lifecycle models. is selected for a development large software development
environment. project.
P2 Explain how risk is
managed in the Spiral
lifecycle model.

LO2 Explain the importance of a feasibility study

P3 Explain the purpose of a M2 Discuss the components of a D2 Assess the impact of different
feasibility report. feasibility report. feasibility criteria on a software
investigation.
P4 Describe how technical
solutions can be compared.

Page 4
Figures of content
Figure 1:Imaage of waterwall..........................................................................................................................................6
Figure 2:Image of V-model..............................................................................................................................................8
Figure 3:Image of Spiral Model......................................................................................................................................10
Figure 4:Image of DSDM Model.....................................................................................................................................13

Figures of table
Table 1:PROS AND CONS OF THE SPIRAL MODEL..........................................................................................................12
Table 2:Alternative Matrix Comparision........................................................................................................................17

Table of Contents

FIGURES OF CONTENT................................................................................................................................................5

FIGURES OF TABLE.....................................................................................................................................................5

INTRODUCTION:......................................................................................................................................................6
1 LO1 DESCRIBE DIFFERENT SOFTWARE DEVELOPMENT LIFECYCLES..........................................................................................6
1.1 P1 DESCRIBE TWO ITERATIVE AND TWO SEQUENTIAL SOFTWARE LIFECYCLE MODELS....................................................................6
1.2 P2 EXPLAIN HOW RISK IS MANAGED IN THE SPIRAL LIFECYCLE MODEL:....................................................................................14
2. LO2 EXPLAIN THE IMPORTANCE OF A FEASIBILITY STUDY.................................................................................................15
2.1 P3 EXPLAIN THE PURPOSE OF A FEASIBILITY REPORT............................................................................................................15
2.2 P4 DESCRIBE HOW TECHNICAL SOLUTIONS CAN BE COMPARED..............................................................................................15
REFERENCES:............................................................................................................................................................18

Page 5
INTRODUCTION:
The process of building computer software and information systems has been always dictated by different
development methodologies. A software development methodology refers to the framework that is used
to plan, manage, and control the process of developing an information system. Formally, a software
development methodology is known as SDLC short for Software Development Life Cycle. This methodology
or process is divided into some phases such as: Requirement Analysis, Design, Coding, Testing, Installation
and Maintenance.

1 LO1 Describe different software development lifecycles

1.1 P1 Describe two iterative and two sequential software lifecycle models.
* Sequential SDLC
The Waterfall Model was the first Process Model to be introduced. It is also referred to as
a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed before the next phase can begin and there is no overlapping in the
phases.
The Waterfall model is the earliest SDLC approach that was used for software development.

Here are phases of the water fall model:

Requirements: The first phase involves
understanding what needs to design and what
is its function, purpose, etc. Here, the
specifications of the input and output or the
final product are studied and marked.
Figure 1:Image of waterwall
Design: The requirement
specifications from the first phase are studied in this phase and system design is prepared. System
Design helps in specifying hardware and system requirements and also helps in defining overall
system architecture. The software code to be written in the next stage is created now.
Implementation: With inputs from system design, the system is first developed in small programs
called units, which are integrated into the next phase. Each unit is developed and tested for its
functionality which is referred to as Unit Testing.

Page 6
 Integration and Testing: All the units developed in the implementation phase are integrated into a
system after testing of each unit. The software designed, needs to go through constant software
testing to find out if there are any flaws or errors. Testing is done so that the client does not face
any problem during the installation of the software.
Maintenance: This step occurs after installation, and involves making modifications to the system
or an individual component to alter attributes or improve performance. These modifications arise
either due to change requests initiated by the customer, or defects uncovered during live use of
the system. The client is provided with regular maintenance and support for the developed
software.
When to use waterfall model:
⇨ Waterfall model is used only when the requirements are very well known in advance, clear
and not supposed to change in future.
⇨ Product definition is stable.
⇨ Technology is understood.
⇨ There are no ambiguous requirements.
⇨ The project is short

Advantages of the Waterfall model:

⇨ Each stage has well defined deliverable or milestone
⇨ simple to use and understand
⇨ acts as template into which methods for analysis, design, code test and maintenance can be
placed
⇨ Work well for smaller projects where requirements are very well understood
⇨ easy to manage due to the rigidity of the model. Each phase has specific deliverables and a
review process.
Disadvantages of the waterfall model:
⇨ No woriking sofware is produced until late during the life cycle
⇨ High amoutns of risk and uncertainly
⇨ Not a good model for complex and object-oriented projects
⇨ Poor model for long and ongoing projects
⇨ Not suitable foe the projects where requirements are at a moderate to high risk of changing
⇨ It is difficult to measure progress within stages

 V-model:
The V-model is a type of SDLC model where process executes in a sequential manner in V-shape. It is also
known as Verification and Validation model. It is based on the association of a testing phase for each
corresponding development stage. Development of each step directly associated with the testing phase. The
next phase starts only after completion of the previous phase i.e. for each development activity, there is a
testing activity corresponding to it.

Page 7
 Figure 2:Image of V-model

Design Phase:
⇨ Requirement Analysis: This phase contains detailed communication with the customer to
understand their requirements and expectations. This stage is known as Requirement
Gathering.

⇨ System Design: This phase contains the system design and the complete hardware and
communication setup for developing product.

⇨ Architectural Design: System design is broken down further into modules taking up

different functionalities. The data transfer and communication between the internal modules
and with the outside world (other systems) is clearly understood.

⇨ Module Design: In this phase the system breaks dowm into small modules. The detailed
design of modules is specified, also known as Low-Level Design (LLD).

Testing Phases:
⇨ Unit Testing: are develop in module design step would performance now. The unit tests are
a very necessary part of any application develop procedure and helps eliminate most of errors
that can generate at a very early phase.

⇨ Integration testing:  Intergration testing performed to meake sure that all of the modules
created before which tested independently in UTPs can coexist and communicate among
themselves within the system. Then test results are shared wtih the client’s team.

Page 8
 ⇨ System Testing: System testing test the complete application with its functionality, inter
dependency, and communication. It tests the functional and non-functional requirements of
the developed application.

⇨ User Acceptance Testing (UAT): UAT is performed in a user environment that resembles the
production environment. UAT verifies that the delivered system meets user’s requirement and
system is ready for use in real world.

Advantages of The V-model:

⇨This is a highly-disciplined model and phases are completed one at time

⇨ Works well for smaller projects where requirements are very well understood

⇨ Simple and easy to use

⇨ Easy to manages due to the rigidity of the model. Each phase has a specific deliverables and a
review process

Disadvantages of The V-model:

⇨ High amoutns of risk and uncertainly
⇨ Not a good model for complex and object-oriented projects
⇨ Poor model for long and ongoing projects
⇨ Not suitable foe the projects where requirements are at a moderate to high risk of changing
⇨ Once an application is in the testing stage, it is difficult to go back and change a functionality
⇨ No working software is produced until late during the life cycle

* Iterative Model:
In the Iterative model, iterative process starts with a simple implementation of a small set
of the software requirements and iteratively enhances the evolving versions until the
complete system is implemented and ready to be deployed.
An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part of the
software, which is then reviewed to identify further requirements. This process is then
repeated, producing a new version of the software at the end of each iteration of the model

 Spiral Model: The spiral model is a software development process combining elements of both
design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom up
concepts.
Page 9
The spiral model has four phases: Identification, Design, Construct or Build and Evaluation and Risk
analysis
A software project repeatedly passes through these phases in iterations called Spirals.

Figure 3:Image of Spiral Model

When to use the Spiral Model:

The Spiral Model is a widely used methodology in the software industry, this is due to the fact that
it is in sync with the natural development process of any product. For instance: learning with
maturity: which involves minimum risk for the client as well as the development team.

⇨ When there is a budget constraint on the project and the risk evaluation is important.

⇨ For projects that are medium-high risk.

⇨ Projects that are long-term committed, due to potential changes in economic priorities as
the requirements may change with time.

⇨ The client is not usually 100% sure of the requirements at the very beginning.

⇨ The requirements are complex and require thorough evaluation to get proper clarity.

⇨ A new product line that should be released in phases to obtain enough customer feedback
to implement any changes in the following release.

Page 10
 ⇨ Significant changes to the product are expected during the development life cycle

Advantages of the Spiral Model:

⇨ Better productivity through reuse capabilities.

⇨ Proper control over cost, time and manpower requirement for a project work.

⇨ Errors are eliminated in early phases of project development only.

⇨ Risk handling:
The Spiral Model revolves around risk analysis, hence it involves risk analysis in every phase. By
doing so, it improves security and the chances of avoiding attacks/breakages allowing the system to
become vulnerable. Moreover, the iterative development process also facilitates risk management.

Disadvanatges of the Spiral Model:

⇨ High cost:
The Spiral model is regarded to be expensive and therefore is not suitable for small projects.

⇨ Dependence on risk analysis:

It is essential for personnel to have expertise in risk assessment, since successful completion of the
project depends on effect risk handling.

⇨ Complexity:
In terms of complexity, the Spiral Model is one of the most complex methodologies compared with
other SDLC options. Therefore meaning that for it to operate productively and efficiently, protocols
must be followed closely and strictly.

⇨ Hard to manage time:

When starting out a project, establishing the number of required phases is often difficult, therefore
making time management almost impossible. All of this means that there is always a risk for falling
behind schedule or even possibly going over budget.

⇨ More documentation:
There is more documentation required when applying the Spiral model as the model involves
intermediate phases.

 Summary of The Spiral Model:

The Spiral Model is a systems development lifecycle (SDLC) method, just like many other methods,
such as Rapid Application Development, that is used for risk management that combines the
iterative development model with elements of the Waterfall Model. The Spiral Model is generally
favoured for large scale, expensive, and complicated projects.

Phases involved in the Spiral Model:

⇨ Identification
Page 11
 ⇨ Design
⇨ Construct/Build
⇨ Evaluation and Risk Analysis

Advantages and Disadvantages of the Spiral Model:

Advantages Disadvantages

Risk of not meeting the schedule or not

Additional functionality or changes can be done at a
complying to the budget that was set out at
later stage
the beginning

Prototype building is done in small fragments,

It works best for large projects, the groups
therefore allowing cost estimation of the project to
must also have risk assessment expertise
be more straightforward

Continuous or repeated development aid risk For its smooth operation, this model has to
management be followed very strictly

Development occurs in a faster manner, and the Due to having more intermediate phases,
fractures are added in a systematic way this requires more documentation

It is not recommended for smaller projects,

Always room for customer feedback
as it might cost them extra

Table 1:PROS AND CONS OF THE SPIRAL MODEL

 DSDM model
DSDM was first created in 1994 and originally sought to provide some discipline to the rapid
application development method. DSDM ATERN is the latest version of the popular DSDM approach
to Agile.

Page 12
 Figure 4:Image of DSDM Model

THE PRINCIPLES OF DSDM:

⇨ Active user involement
⇨ Teams must be empowered to make their own decisions
⇨ Frequent releases more important than maximizing quality
⇨ Primary criteria for deliverables is meeting business needs
⇨ terative development is essential to reach correct solution
⇨ The most high-level requirements should be unchangeable
⇨ Testing shall occur throughout the life cycle of the project
⇨ All skateholders must cooperate

Advantages pf DSDM Model:

⇨ Responding to change
⇨ Accepting uncertainty
⇨ Faster review cycles

Disadvantages of DSDM Development

⇨ Lack of understanding
⇨ Flexibility can lead to bad behaviours
⇨ Challenges at scale

Page 13
1.2 P2 Explain how risk is managed in the Spiral lifecycle model
An effective risk management process is an imporatnt 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 mange 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.

 Risk assessment:
Risk assesment 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.

 Calculating Inherent Risk:

Inherent risk specify the exposure arising from a risk event before any action has been taken to
manage it.
Inherent Risk = Consequence x Probability Inherent risk rating will be exhibited on a 4 level rating
scale: Extreme Risk, High Risk, Moderate Risk, Low Risk.

 Risk assessment reports:

There are different kinds of risk assessment reports:
⇨ Detail-Risk Report: detail risk at different stages based on cost, schedule, resource and
manpower factors.
⇨ Scope-Risk Report: The scope statement or mission statement may be assessed for risks at the
beginning of a project.
⇨ Cost evaluation risk Report: Cost or funds are at constant risk in a project. It has to be
maintained and controlled with as little deviation as possible from the forecasted values.
⇨ Schedule Evaluation Risk Report: Time is luxury that a project cannot afford. It is imperative that
time schedulesare met with as little delay as possible. Time delays can impact the progress of a project nad
put it at risk. Such risks are documented in the schedule evaluation risk report.
⇨ Technical Evaluation Risk Report: Risks related to resources, manpower and departments fall
under this category. Risk arising due to quality constraints and those which are due to desig n errors and
poor planning also fall under this group.
 Keys for a successful risk management:
⇨ Senior management’s commitment.

Page 14
 ⇨ The full support and participation of the IT Team.

⇨ The competence of the risk assessment team, which must have the expertise to apply the risk
asssessment methodology to a specific site and system, identify missiomn risks and provide cost-effective
safeguards that meet the needs of the organization.

⇨ The awareness and cooperation of members of the user community, who must follow procedures
nad comply with the implemented controls to safeguard the mission of. Their organization.

2. LO2 Explain the importance of a feasibility study

2.1 P3 Explain the purpose of a feasibility report.

The main purpose of a feasibility report: Identifies the important risks associated with the project
that must be managed if the project is approved
 A project feasibility study is a comprehensive report that examines in detail the five frames of
analysis of a given project. It also takes into consideration its four Ps, its risks and POVs, and its
constraints (calendar, costs, and norms of quality).
 The goal is to determine whether the project should go ahead, be redesigned, or else abandoned
altogether.
The five frames of analysis are: The frame of definition; the frame of contextual risks; the frame of
potentiality; the parametric frame; the frame of dominant and contingency strategies.
 The four Ps are traditionally defined as Plan, Processes, People, and Power. The risks are
considered to be external to the project (e.g., weather conditions) and are divided in eight
categories: (Plan) financial and organizational (e.g., government structure for a private project);
(Processes) environmental and technological; (People) marketing and sociocultural; and (Power)
legal and political. POVs are Points of Vulnerability: they differ from risks in the sense that they are
internal to the project and can be controlled or else eliminated.
 The feasibility report will look at how a certain proposal can work in a long-term basis or endure
financial risks that may come. It is also helpful in recognizing potential cash flow. Another important
purpose is that it helps planners focus on the project and narrow down the possibilities.
Accordingly, a feasibility study can provide reasons not to pursue the said project or proposal.
When it comes to the operational aspect, the analysis determines whether the plan has the
necessary resources for it to be practicable. Feasibility report will also help we figure out whether or
not the people will support the subsequent product or service. Additionally, it provided knowledge
on the trends because a feasibility study looks at the present-day market and studies the
anticipated growth of your target business sector.
Feasibility studies are prevalent in all business industries. Whether Hotel, Hospitality, Restaurant, Real
Estate, Medical, Office or Industrial. Getting a head start on a Feasibility study will ensure you save time
and money

Page 15
2.2 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 alternative 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.

Evaluation Relative Alternartive1: Score(1 Weighte Alternative2: Score(1 Weighted

criteria importance plugin using -5) d Using -5) Score
C# Score Javascript
Tecnical
issues
C1.Support 10 Current 5 50 Support full 5 50
front-end and system uses stack
back-end Windows
server
C2. Able to run 10 Current 5 50 Current 5 50
on Windows system uses system fully
server Windows support JS
server
C3. Support 10 Microsoft 5 50 Easy to find 4 40
multimedia support what open source
libraries we need library
Economic
Issues
C4. License costs 10 Visual studio 4 40 Free 5 50
less then $5000 + for
netframework commercial
cost $4500 use
C5. Server costs 10 Reuse current 5 50 Reuse server 5 50
less than server
$10000/year
Page 16
Organizational
issues
C6. Able to 10 Very high 3 30 Not easy to 3 30
recruit a senior Salry find
developer
C7.Able to 10 Easy to find 5 50 Easy to find 5 50
recruit a
experienced
project manager
C8. Able to hire a 30 Easy to find 5 150 Easy to find 5 150
tester with chare
less than
$10000/month
Total 100 470 470
1. We build a system of criteria. For each criteria we make relative
importance
2. We build a set of candidate solutions. For each solution we make score
and explaination. Score is from 1-5, 1 = poor fit, 5 = perfect fit.
3. For each solution and each criteria we compute weighted score by formula
weighted score = relative importance*score
4. For each solution we compute total score by SUM all weighted score
5. We compare candidate solution by its total score. Great is better
Table 2:Alternative Matrix Comparision

References:
www.researchgate.net/publication/319716548_SOFTWARE_DEVELOPMENT_LIFE_CYCLE_SDLC_A
NALYTICAL_COMPARISON_AND_SURVEY_ON_TRADITIONAL_AND_AGILE_METHODOLOGY

Page 17
www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm
-www.tutorialspoint.com. (2018). SDLC Quick Guide. [online] Available at:
https://www.tutorialspoint.com/sdlc/sdlc_quick_guide.htm [Accessed 19 Nov. 2018].
-UserVoice Blog. (2018). The Pros and Cons of Agile ProductDevelopment| UserVoice Blog.
[online] Available at: https://community.uservoice.com/blog/the-pros-and-cons-of-agile-
product- development/ [Accessed 19 Nov. 2018].
-Ijera.com. (2018). [online] Available at:
https://www.ijera.com/papers/Vol2_issue4/DJ24712716.pdf [Accessed 19 Nov. 2018].
-En.wikipedia.org. (2018). Feas ibility s tudy. [online] Available at:
https://en.wikipedia.org/wiki/Feasibility_study#Formal_definition [Accessed 19 Nov. 2018].
-Trumanmox.com. (2018). Why a Feas ibility S tudy is Important for any B us iness | TrumanMox.
[online] Available at: https://www.trumanmox.com/why-a-feasibility-study-is-important-for-any-
business [Accessed 19 Nov. 2018].
-Arxen.com. (2018). [online] Available at:
http://www.arxen.com/descargas/PulzarCloud/Books/systems-analysis-and-design-with-uml-
5th- edition.pdf [Accessed 19 Nov. 2018].

Page 18