ASSIGNMENT 1 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 9: Software Development Life Cycle

Submission date 06/04/2020 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name Hồ Nhật Long Student ID GCD18543

Class GCD0704 Assessor name Trần Trọng Minh

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:

Signature & Date:

 SOFTWARE DEVELOPMENT LIFE CYCLE

School: University Of Greenwich VietNam

Name: Hồ Nhật Long
Student ID: GCD18543
Class: GCD18543
Teacher: Trần Trọng Minh
 TABLE OF CONTENT
CHapter P1 Describe two iterative and two sequential software lifecycle models. .................................................... 6
I. Describe two iterative and two sequential software lifecycle models. ................................................................ 6
1. Interative models. ............................................................................................................................................. 6
2. Sequential models............................................................................................................................................. 8
CHAPTER P2 Explain how risk is managed in the Spiral lifecycle model..................................................................... 10
I. Explain how risk is managed in the Spiral lifecycle model................................................................................... 10
1. What is the spiral model? ............................................................................................................................... 10
2. Explain how risk is managed ........................................................................................................................... 10
Chapter p3 Explain the purpose of a feasibility report. .............................................................................................. 12
I. Explain the purpose of a feasibility report........................................................................................................... 12
1. What is a Feasibility Study? ............................................................................................................................ 12
2. the purpose of conducting a feasibility study for the project. ....................................................................... 12
3. How to make a feasibility report that can help project managers in project selection, planning and design 12
CHAPTER P4 Describe how technical solutions can be compared. ............................................................................ 14
I. Describe how technical solutions can be compared. .......................................................................................... 14
1. Purpose ........................................................................................................................................................... 14
2. Technical feasibility ......................................................................................................................................... 14
3. Economic feasibility ........................................................................................................................................ 14
4. organizational feasibility ................................................................................................................................. 14
5. How To Evaluate Technical Solutions ............................................................................................................. 15
Reference .................................................................................................................................................................... 16
 TABLE OF FIGURE
Picture 1: Spiral Model...................................................................................................................................... 6
Picture 2: Agile Model....................................................................................................................................... 7
Picture 3: Waterfall Model ............................................................................................................................... 8
Picture 4: V Model ............................................................................................................................................ 9
Picture 5: Spiral Model.................................................................................................................................... 10

TABLE OF TABLE
Table1: Advantages and Disadvantages of Spiral model .............................................................................. 6
Table2: Advantages and Disadvantages of Agile model ............................................................................... 7
Table 3: Advantages and Disadvantages of Waterfall model ....................................................................... 8
Table 4: Advantages and Disadvantages of V model .................................................................................... 9
 CHAPTER P1 DESCRIBE TWO ITERATIVE AND TWO SEQUENTIAL SOFTWARE
LIFECYCLE MODELS.
I. DESCRIBE TWO ITERATIVE AND TWO SEQUENTIAL SOFTWARE LIFECYCLE MODELS.
1. Interative models.
- Spiral:
• A model combining features of prototyping model and waterfall model.
• The spiral model is preferred for large, expensive and complex projects.
• This model uses the same stages as the waterfall model, in order, plan, risk assessment, etc.

Picture 1: Spiral Model

Advantages Disadvantages
Good for large scale software systems. Managers need good skills to manage projects,
assess risks promptly.
Easy to control risks at each evolutionary level. The cost is high and it takes a long time to
complete the project.
More realistic assessment as a workflow, because Complex and unsuitable for small and low-risk
important issues were discovered earlier. projects.
Additional functionality or changes can be done at Requiring frequent changes results in infinite
a later stage iterations.
Development is fast and features are added in a Not widely used yet.
systematic way
There is always a space for customer feedback Risk of not meeting the schedule or budget
Table1: Advantages and Disadvantages of Spiral model
- Agile:
• Agile is a flexible software development method to bring products to users as quickly as possible
and is considered an improvement over the old models such as the "waterfall" model or "CMMI".
Agile software development method is a set of iterative and incremental development methods
in which requirements and solutions are developed through collaborative links between
autonomous and inter-functional groups.
• Based on iterative and incremental model.
• The requirements and solutions evolve based on a combination of functions.
• In Agile, tasks are broken down into small time frames to provide specific features for the final
release.

Picture 2: Agile Model

Advantages Disadvantages
Strengthening teamwork spirit and effective work Transferring technology to new team members
exchange. can be difficult due to the lack of documentation.
The function is built quickly and clearly, cricket There are many risks of sustainability,
management. maintainability, and scalability.
Easy to add, change requests. Need an experienced team.
Minimal rules, easy to understand documents, Depends greatly on the clear interaction of
easy to use. customers.
Table2: Advantages and Disadvantages of Agile model
2. Sequential models
- Waterfall
• This is considered to be the first software development model used.
• This model sequentially applies the stages of software development.
• The output of the previous stage is the input of the later stage. The next phase can only be
performed when the previous stage has ended. In particular, do not go back to the previous stage
to handle the request when you want to change.

Picture 3: Waterfall Model

Advantages Disadvantages
Easy to use, accessible, easy to manage. Less flexible, limited adjustment range.
Products develop in clearly defined stages. It is difficult to measure growth in each stage.
Confirm at each stage, ensuring early detection of The model is not suitable for long, ongoing, or
errors. complex projects, with many changes in
requirements throughout the development life
cycle.
Suitable for projects in the direction of a timeline It's hard to come back when a period is over.
Table 3: Advantages and Disadvantages of Waterfall model
- V model:
• The V-model is an extension of the waterfall model and is based on a combination of a testing
phase for each respective development stage. This is a highly disciplined model and the next
phase begins only after completing the previous stage.
• With V models, the test work is involved from the beginning.

Picture 4: V Model

Advantages Disadvantages
The development process and management Not suitable for large and complex projects
process are organized and systematic
Works well for small and medium sized projects. Not suitable if requirements frequently change.
Testing starts from the beginning of development No working software is produced in the
so ambiguity is determined from the beginning. intermediate stage.
Easy to manage because each stage has clearly There is no provision for risk analysis so there is
defined goals and objectives. uncertainty and risk.
Table 4: Advantages and Disadvantages of V model
 CHAPTER P2 EXPLAIN HOW RISK IS MANAGED IN THE SPIRAL LIFECYCLE
MODEL.
I. EXPLAIN HOW RISK IS MANAGED IN THE SPIRAL LIFECYCLE MODEL.
1. What is the spiral model?
The spiral model is a software development process model developed by Barry W. Boehm in 1986. It is
based on the assumption that the development of applications is an iterative cycle that is repeated until
the set goal is reached. The spiral model minimizes the risk of failure in large software projects
considerably by regularly assessing risks and checking the intermediate product on a regular basis.

Picture 5: Spiral Model

2. Explain how risk is managed

• Planning phase:
Collect, analyze project requirements from customers. Including tasks: estimating cost, scheduling a
project (shedule-master), determining the number of human resources, identifying necessary resources
and work environment, finding out system requirements (requirements) from which the Bussiness
Requirement Specifications and System Requirement specifications to serve for the exchange between
customers and later system analysis.
• Identifying and resolving the risks:
An analysis will be carried out to identify risks and provide alternatives. A prototype will be created at
the end of the risk analysis phase. If any risks are found in this process, alternative solutions will be
proposed and implemented. In this phase of the spiral model cycle, areas of uncertainty should be
identified that pose a significant risk to the progress of the software project. This will be followed by the
development of the least risky and most cost-effective strategy, using methods such as prototyping,
simulations, benchmark tests, analytical models, and user surveys.
• Engineering phase:
This is the stage where the project is coded by developers, testers conduct testing and deploying
software on the customer's website.
• Evaluation phase:
Customers will participate in this stage to evaluate the work, the product and ensure that the product
meets all requirements set forth earlier. If there is any change request from the customer, the stages will
be repeated. This is an important stage because there is a need for customer feedback on the product
before it is released.
 CHAPTER P3 EXPLAIN THE PURPOSE OF A FEASIBILITY REPORT.

I. EXPLAIN THE PURPOSE OF A FEASIBILITY REPORT.

1. What is a Feasibility Study?
As the name implies, a feasibility analysis is used to determine the viability of an idea, such as ensuring a
project is legally and technically feasible as well as economically justifiable. It tells us whether a project is
worth the investment—in some cases, a project may not be doable. There can be many reasons for this,
including requiring too many resources, which not only prevents those resources from performing other
tasks but also may cost more than an organization would earn back by taking on a project that isn’t
profitable.

A well-designed study should offer a historical background of the business or project, such as a
description of the product or service, accounting statements, details of operations and management,
marketing research and policies, financial data, legal requirements, and tax obligations. Generally, such
studies precede technical development and project implementation.
2. the purpose of conducting a feasibility study for the project.
A feasibility report is a document that assesses potential solutions to the business problem or
opportunity and determines which of these are viable for further analysis.

The purpose of the feasibility report is to present the project parameters and define the potential
solutions to the defined problem, 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. Project constraints and limitations of expenditure are among the various factors that will
determine viability.
3. How to make a feasibility report that can help project managers in project selection, planning and
design
7 Steps for a Feasibility Study
Follow these steps when conducting a feasibility study:

1. Conduct a Preliminary Analysis

Begin by outlining your plan. You should focus on an unserved need, a market where the demand is
greater than the supply, and whether the product or service has a distinct advantage. Then you need to
determine if the hurdles are too high to clear (i.e. too expensive, unable to effectively market, etc.).
2. Prepare a Projected Income Statement
This step requires you to work backward. Start with what you expect the income from the project to be
and then what investment is needed to achieve that goal. This is the foundation of an income statement.
Things to take into account here include what services are required and how much they’ll cost, any
adjustments to revenues, such as reimbursements, etc.

3. Conduct a Market Survey, or Perform Market Research

This step is key to the success of your feasibility study, so make it as thorough as possible. It’s so
important that if your organization doesn’t have the resources to do a proper one, then it is
advantageous to hire an outside firm to do so. The market research is going to give you the clearest
picture of the revenues you can realistically expect from the project. Some things to consider are the
geographic influence on the market, demographics, analyzing competitors, the value of the market and
what your share will be and if the market is open to expansion (that is, response to your offer).

4. Plan Business Organization and Operations

Once the groundwork of the previous steps has been laid, it’s time to set up the organization and
operations of the planned business venture. This is not a superficial, broad stroke endeavor. It should be
thorough and include start-up costs, fixed investments, and operation costs. These costs address things
such as equipment, merchandising methods, real estate, personnel, supply availability, overhead, etc.

5. Prepare an Opening Day Balance Sheet

This includes an estimate of the assets and liabilities, one that should be as accurate as possible. To do
this, create a list that includes item, source, cost and available financing. Liabilities to consider are such
things as leasing or purchasing of land, buildings and equipment, financing for assets and accounts
receivables.

6. Review and Analyze All Data

All these steps are important, but the review and analysis are especially important to make sure that
everything is as it should be and nothing requires changing or tweaking. So, take a moment to look over
your work one last time. Reexamine your previous steps, such as the income statement, and compare it
with your expenses and liabilities. Is it still realistic? This is also the time to think about risk, analyzing
and managing, and come up with any contingency plans.
7. Make a Go/No-Go Decision
You’re now at the point to make a decision about whether the project is feasible or not. That sounds
simple, but all the previous steps we’re leading to this decision-making moment. A couple of other things
to consider before making that binary choice is whether the commitment is worth the time, effort and
money and is it aligned with the organization’s strategic goals and long-term aspirations.
 CHAPTER P4 DESCRIBE HOW TECHNICAL SOLUTIONS CAN BE COMPARED.

I. DESCRIBE HOW TECHNICAL SOLUTIONS CAN BE COMPARED.

1. Purpose
The purpose of Technical Solution (TS) is to design, develop, and implement solutions to requirements.
Solutions, designs, and implementations encompass products, product components, and product-related
lifecycle processes either singly or in combination as appropriate.
2. Technical feasibility
Technical feasibility is one of the most important criteria for selecting material for digitization. The
physical characteristics of source material and the project goals for capturing, presenting and storing the
digital surrogates dictate the technical requirements. Libraries must evaluate those requirements for
each project and determine whether they can be met with the resources available. If the existing staff,
hardware and software resources cannot meet the requirements, then the project will need funding to
upgrade equipment or hire an outside conversion agency. If these resources are not available, or if the
technology does not exist to meet the requirements, then it is not technically feasible to digitize that
material.
3. Economic feasibility
Economic feasibility is the cost and logistical outlook for a business project or endeavor. Prior to
embarking on a new venture, most businesses conduct an economic feasibility study, which is a study
that analyzes data to determine whether the cost of the prospective new venture will ultimately be
profitable to the company. Economic feasibility is sometimes determined within an organization, while
other times companies hire an external company that specializes in conducting economic feasibility
studies for them.
4. organizational feasibility
It is to define the legal and corporate structure of a business. An organizational feasibility study may also
include professional background information about the founders and principals of the business and what
skills they can contribute to the business. Your organizational feasibility study should include:

• Description of your business structure

• Description of your organizational structure
• Internal and external principles and practices of the business
• Professional skills and resumes
5. How To Evaluate Technical Solutions

Fitness: Does the technology address the problem at hand, or is it being used for an unintended
purpose?
Maturity: It's risky to use version 1.0 of anything. Both hardware and software companies are frequently
pressed to release products before they are ready.
Provenance: While small companies regularly come up with great ideas, it can be risky to rely on
technology from a company whose future is uncertain.
Support: If something goes wrong, who/how many people can help solve the problem? While
commercial (paid) support is appreciated, open-source products with large numbers of helpful users can
be even more valuable.
Reliability/availability/scalability: Does the technology support the required usage volume? Does it offer
fail-over mechanisms for high availability?
License and support costs: What are the one-time and annual costs of using a technology? While my
developers might have a fondness for certain proprietary software, is there an adequate free or low-cost
open-source alternative? Keep in mind that even open-source software can be expensive if the vendor
restricts commercial use or has inconvenient licensing terms.
 REFERENCE
Ha, N., 2020. MÔ HÌNH XOẮN ỐC LÀ GÌ? KHI NÀO NÊN SỬ DỤNG? ƯU VÀ NHƯỢC ĐIỂM CỦA MÔ HÌNH. [online]
Viblo. Available at: <https://viblo.asia/p/mo-hinh-xoan-oc-la-gi-khi-nao-nen-su-dung-uu-va-nhuoc-diem-cua-mo-
hinh-vyDZOWVxZwj> [Accessed 6 Apr. 2020].
Anon, 2020. Technical Feasibility. [online] Technical Feasibility - an overview | ScienceDirect Topics. Available at:
<https://www.sciencedirect.com/topics/computer-science/technical-feasibility> [Accessed 6 Apr. 2020].
Simplilearn, 2020. What is Feasibility Study and Its Importance in Project Management. [online] Simplilearn.com.
Available at: <https://www.simplilearn.com/feasibility-study-article> [Accessed 6 Apr. 2020].
Ha, N., 2020. MÔ HÌNH XOẮN ỐC LÀ GÌ? KHI NÀO NÊN SỬ DỤNG? ƯU VÀ NHƯỢC ĐIỂM CỦA MÔ HÌNH. [online]
Viblo. Available at: <https://viblo.asia/p/mo-hinh-xoan-oc-la-gi-khi-nao-nen-su-dung-uu-va-nhuoc-diem-cua-mo-
hinh-vyDZOWVxZwj> [Accessed 6 Apr. 2020].
Bridges, J., 2019. How to Conduct a Feasibility Study. [online] ProjectManager.com. Available at:
<https://www.projectmanager.com/training/how-to-conduct-a-feasibility-study> [Accessed 6 Apr. 2020].
Editors, F.T.C., 2017. Council Post: 12 Factors To Help You Evaluate Potential Technical Solutions. [online] Forbes.
Available at: <https://www.forbes.com/sites/forbestechcouncil/2017/02/09/12-factors-to-help-you-evaluate-
potential-technical-solutions/#1280f19a4f66> [Accessed 6 Apr. 2020].