Higher Nationals in Computing

Software Development Life Cycle

ASSIGNMENT 1

Learner’sname: DoanThienAN
ID: GCS200176
Class: Software
Development
Subject code:
Assessor name: HO NGUYEN PHU BAO

Assignment due: Assignment submitted:

Page 1
 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

Issue date Submission date

Name and date

Submission 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
Format:
and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation
and references must follow the Harvard referencing style.
Word limit: 2000 words

You must submit the assignment by the due date and follow the submission method
Submission: specified by the Tutor. The submission form is soft copy, which is to be uploaded to the
following URL: http://cms.greenwich.edu.vn.

Your assignment must be your own work, and not copied by or from another student or from
other sources, such as book etc. If you use ideas, quotes or data (such as diagrams) from
Note: books, journals or other sources, you must reference the sources, using the Harvard style.
Make sure that you know how to reference properly and that you understand the plagiarism
guidelines. Plagiarism is a very serious offence, which will result in a failing grade.

Unit Learning Outcomes:

LO1 Describe different software development lifecycles.

LO2 Explain the importance of a feasibility study.

Page 2
Assignment Brief and Guidance:

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

Page 3
 • $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.

Page 4
 Learning Outcomes and Assessment Criteria

Pass Merit Distinction

LO1 Describe different software development lifecycles

P1 Describe two iterative and

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

LO2 Explain the importance of a feasibility study

P3 Explain the purpose of a D2 Assess the impact of different

feasibility report. feasibility criteria on a software
M2 Discuss the components of a investigation.
feasibility report.
P4 Describe how technical
solutions can be compared.

Page 5
 TABLE OF CONTENT

P1. Describe two iterative and two sequential software lifecycle models ....................................................7
1) What is Software Development Life Cycle? ...............................................................................................7
2) Suitable SDLC Model ...............................................................................................................................20

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

1) What is Risk Management Process?..........................................................................................................21
2) Risk management steps .............................................................................................................................21
3) Risk Management Plan ..............................................................................................................................25

P3. Discuss the purpose of conducting a feasibility study for the project. ................................................26
1) What is a Feasibility Study? ......................................................................................................................26
2) 7 steps in Feasibility Study........................................................................................................................26
3) Importance of Feasibility study .................................................................................................................29

P4 Describe how technical solutions can be compared. ..............................................................................32

1) Technical feasibility ..................................................................................................................................33
2) Organizational Feasibility .........................................................................................................................34
3) Economic Feasibility Study.......................................................................................................................36
4) Alternative Matrix .....................................................................................................................................37

Page 6
P1. Describe two iterative and two sequential software lifecycle models

1) What is Software Development Life Cycle?

In short, S.D.L.C is a series of different stages that illustrates how a software was
made. It also known as a framework that describes activities performed at each stage
of a software development project.

Software development experts and organizations have created different S.D.L.C

models to solve many issues. Each model follows series of unique steps in orders to
ensure a successful software development.

There are 5 common S.D.L.C model such as Waterfall, V-Shaped, Agile, Spiral and
Prototype.

Figure 1: S.D.L.C definition

Page 7
1.1) Waterfall Model
The Waterfall Model is a linear sequential flow. In which progress is seen as
flowing steadily downwards (like a waterfall) through the phases of software
implementation. This means that any phase in the development process begins
only if the previous phase is complete. The waterfall approach does not define
the process to go back to the previous phase to handle changes in requirement.

Figure 2: Waterfall Model

Page 8
 Advantages and Disadvantages

Advantages Disadvantages

• Assumes that the requirements of a

• Easy to explain to the users. system can be frozen.
• Structures approach. • Very difficult to go back to any stage
• Stages and activities are well defined. after it finished.
• Helps to plan and schedule the project. • A little flexibility and adjusting scope is
• Verification at each stage ensures early detection of difficult and expensive.
errors/misunderstanding. • Costly and required more time, in
• Each phase has specific deliverables. addition to the detailed plan.

Table 1: Waterfall Model Pros and Cons

The usage

• The requirements are precisely documented

• Product definition is stable
• The technologies stack is predefined which makes it not dynamic
• No ambiguous requirements
• The project is short

• Projects which not focus on changing the requirements, for example, projects initiated from a
request for proposals (RFPs), the customer has a very clear documented requirements.

Page 9
1.2) V-Shaped Model
It is an extension of the waterfall model, instead of moving down in a linear
way, the process steps are bent upwards after the implementation and coding
phase, to form the typical V shape. The major difference between the V-
shaped model and waterfall model is the early test planning in the V-shaped
model.

Figure 3: V-Shaped Model

Page 10
 The usage

• For the projects where an accurate product testing is required

• For the small and mid-sized projects, where requirements are strictly
predefined
• The engineers of the required qualification, especially testers, are within easy
reach.

Advantages and Disadvantages

Advantages Disadvantages

• Simple and easy to use
• Each phase has specific deliverables.
• Higher chance of success over the waterfall
model due to the development of test plans
early on during the life cycle.
• Works well for where requirements are easily
understood.
• Verification and validation of the product in
the early stages of product development.
• Very inflexible, like the waterfall model.
• Adjusting scope is difficult and expensive.
• The software is developed during the
implementation phase, so no early prototypes
of the software are produced.
• The model doesn’t provide a clear path for
problems found during testing phases.
• Costly and required more time, in addition to a
detailed plan

Table 2: V-Shaped Pros and Cons

Page 11
1.3) Prototyping Model
It refers to the activity of creating prototypes of software applications, for example,
incomplete versions of the software program being developed.

It is an activity that can occur in software development and It used to visualize some
component of the software to limit the gap of misunderstanding the customer
requirements by the development team.

This also will reduce the iterations may occur in the waterfall approach and hard to be
implemented due to the inflexibility of the waterfall approach. So, when the final
prototype is developed, the requirement is considered to be frozen.

There are several types of Prototyping Model include:

Throwaway prototyping
Prototypes that are eventually discarded rather than becoming a part of the
finally delivered software.

Page 12
Evolutionary prototyping
Prototypes that evolve into the final system through an iterative incorporation
of user feedback.

Figure 4: Prototyping models

Figure 5: Prototyping Modes

Page 13
Incremental prototyping
The final product is built as separate prototypes. In the end, the separate
prototypes are merged in an overall design.

Figure 6: Prototyping Modes

Page 14
 The usage
• This process can be used with any software developing life cycle model.
• While this shall be chosen when you are developing a system has user
interactions.
• So, if the system does not have user interactions, such as a system d oes some
calculations shall not have prototypes.

Advantages and Disadvantages

Advantages Disadvantages

• Insufficient analysis. User confusion of

• Reduced time and costs, but
this can be a disadvantage if
the developer loses time in
developing the prototypes.
• Improved and increased user
involvement.
prototype and finished system.
• Developer misunderstanding of user
objectives.
• Excessive development time of the
prototype.
• It is costly to implement the prototypes

Table 3: Prototyping Model Pros and Cons

Page 15
1.4) Spiral Model

It is combining elements of both design and prototyping-in-stages, in an effort to

combine advantages of top-down and bottom-up concepts.

This model of development combines the features of the prototyping model and the
waterfall model.

The spiral model is favored for large, expensive, and complicated projects.

This model uses many of the same phases as the waterfall model, in essentially the
same order, separated by planning, risk assessment, and the building of prototypes and
simulations.

Figure 7: Spiral Model

Page 16
 The usage
• Customer isn’t sure about the requirements

• Major edits are expected during the development cycle

• The projects with mid or high-level risk, where it is important to prevent these risks

• The new product that should be released in a few stages to have enough of clients
feedback

Advantages and Disadvantages

Advantages Disadvantages

• Estimates (i.e. budget, schedule, etc.) become • High cost and time to reach the final
more realistic as work progressed because product.
important issues are discovered earlier. • Needs special skills to evaluate the
• Early involvement of developers. risks and assumptions.
• Manages risks and develops the system into • Highly customized limiting re-
phases. usability

Table 4: Spiral Model Pros and Cons

Page 17
1.5) Agile Model

In the agile methodology after every development iteration, the customer is

able to see the result and understand if he is satisfied with it or he is not. This

is one of the advantages of the agile software development life cycle model.

One of its disadvantages is that with the absence of defined requirements it is

difficult to estimate the resources and development cost. Extreme

programming is one of the practical use of the agile model.

It is based on iterative and incremental development, where requirements and

solutions evolve through collaboration between cross-functional teams.

Used less formal and reduced scope.

Used for time-critical applications

Figure 8: Agile Model

Page 18
 The usage
• It can be used with any type of the project, but it needs more engagement from the
customer and to be interactive.

• It can also be used when the customer needs to have some functional requirement
ready in less than three weeks and the requirements are not clear enough. This will
enable more valuable and workable piece for software early which also increase the
customer satisfaction.

Advantages and Disadvantages

Advantages Disadvantages

• Decrease the time required to avail some system • Scalability.

features.
• Face to face communication and continuous inputs
from customer representative leaves no space for
guesswork.
• The end result is the high-quality software in the
least possible time duration and satisfied customer.
• The ability and collaboration of the
customer to express user needs.
• Documentation is done at later
stages.
• Reduce the usability of components.
• Needs special skills for the team.

Table 5: Agile Model Pros and Cons

Page 19
2) Suitable SDLC Model

For this project specifically, the Spiral model would be a fantastic choice.
Although there are many drawbacks such as Expensive setup fees, inefficient for
small projects, Risk-control demands the involvement of highly-skilled
professionals, the Spiral model is more reliable and reasonable among models.

These are reasons why spiral model is suitable for this project:

• The development process is precisely documented yet scalable to the

changes.
• The scalability allows to make changes and add new functionality even at
the relatively late stages

• The earlier working prototype is done - sooner users can point out the
flaws

• This model is divided into small phase, which is a good thing for this
specific project. Because if the risk concentration is higher, specific phase
can be finished earlier to address the treats.

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

1) What is Risk Management Process?

It's simply an ongoing process of identifying, treating, and then managing risks.
Taking the time to set up and implement a risk management process is like setting up
a fire alarm – You hope it never goes off, but you’re willing to deal with the minor
inconvenience upfront in exchange for protection down the road.
Benefits:
• More efficient resource planning by making previously unforeseen costs visible.
• Better tracking of project costs and more accurate estimates of return on investment.
• Increased awareness of legal requirements.
• Better prevention of physical injuries and illnesses.
• Flexibility, rather than panic, when changes or challenges do arise.

2) Risk management steps

2.1) Identify 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.

Page 21
 Figure 9: 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 high-level 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.

Page 22
2.2) 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.

2.3) 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.

Page 23
2.4) 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.

2.5) 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.

Page 24
 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

Not stable Insufficient care The house might collapse

1 Possible Major Extreme
foundation during preparation during heavy weather

Insufficient care Broken fence may ruin

2 Stiffed fence Possible Moderate Moderate
during preparation appearance of the house

Insufficient care Cause bad smell all around

3 Poor ventilation Possible Major Moderate
during preparation the house

Insufficient care May cause owner to be

4 Bad paint job Possible Moderate Moderate
during preparation unhappy

Not enough
Insufficient care Hard to identify the house
5 lighting around Possible Moderate Moderate
during preparation when dark
the house

Table 6: Risk Management Plan

Page 25
P3. Discuss the purpose of conducting a feasibility study for the project.

1) What is a Feasibility Study?

A feasibility study is designed to reveal whether a project/plan is feasible. It is an
assessment of the practicality of a proposed project/plan.

A feasibility study is part of the initial design stage of any project/plan. It is conducted
in order to objectively uncover the strengths and weaknesses of a proposed project or
an existing business. It can help to identify and assess the opportunities and threats
present in the natural environment, the resources required for the project, and the
prospects for success.

2) 7 steps in Feasibility Study

• 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 (too expensive,
unable to effectively market, etc.).

• Prepare a Projected Income Statement

This step requires you to work backwards. 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.

Page 26
Conduct a Market Survey

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.

• 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.).

• 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.

Page 27
• 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.

• Make a Go/No-Go Decision

You’re now at the point to make a decision about whether the project is
feasible or not.

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.

Page 28
3) Importance of Feasibility study

• Possible Constraint

When the project feasibility areas have all been examined, the study
helps identify any constraints the proposed project may face, including:

Internal Project Constraints:

✓ Technical, Technology. Budget, Resource, etc.

Internal Corporate Constraints:

✓ Financial Marketing, Export, etc.

External Constraints:

✓ Logistics, Environment Laws and Regulations, etc.

Benefit of Conducting a feasibility Study

The importance of a feasibility study is based on organizational desire

to "get it right before committing resources, time, or budget. Given
below are some key benefits of conducting a feasibility study:

• Improves project teams' focus

• Identifies new opportunities

• Provides valuable information for a go/no-go" decision

• Narrows the business alternatives

• Identifies a valid reason to undertake the project

• Enhances the success rate by evaluating multiple

parameters

• Aids decision-making on the project

Page 29
 • Identifies reasons not to proceed

Page 30
In conclusion, Feasibility studies are important to business development. They can
allow a business to address where and how it will operate. They can also identify
potential obstacles that may impede its operations and recognize the amount of
funding it will need to get the business up and running.

Feasibility studies aim for marketing strategies that could help convince investors or
banks that investing in a particular project or business is a wise choice.

Page 31
P4 Describe how technical solutions can be compared.

A feasibility study assesses the operational, technical and economic merits of the proposed
project. The feasibility study is intended to be a preliminary review of the facts to see if it is
worthy of proceeding to the analysis phase.

From the systems analyst perspective, the feasibility analysis is the primary tool for
recommending whether to proceed to the next phase or to discontinue the project.

The feasibility study is a management-oriented activity. The objective of a feasibility study is

to find out if an information system project can be done and to suggest possible alternative
solutions.

A feasibility study should provide management with enough information to decide:

• Whether the project can be done

• Whether the final product will benefit its intended users and organization
• What are the alternatives among which a solution will be chosen?
• Is there a preferred alternative?

Page 32
1) Technical feasibility
A large part of determining resources has to do with assessing technical feasibility. It
considers the technical requirements of the proposed project. The technical
requirements are then compared to the technical capability of the organization. The
systems project is considered technically feasible if the internal technical capability is
sufficient to support the project requirements.

The analyst must find out whether current technical resources can be upgraded or
added to in a manner that fulfills the request under consideration. This is where the
expertise of system analysts is beneficial, since using their own experience and their
contact with vendors they will be able to answer the question of technical feasibility.

The essential questions that help in testing the operational feasibility of a system
include the following:

• Is the project feasible within the limits of current technology?

• Does the technology exist at all?
• Is it available within given resource constraints?
• Is it a practical proposition?
• Manpower- programmers, testers & debuggers
• Software and hardware
• Are the current technical resources sufficient for the new system?
• Can they be upgraded to provide to provide the level of technology necessary
for the new system?
• Do we possess the necessary technical expertise, and is the schedule
reasonable?
• Can the technology be easily applied to current problems?
• Does the technology have the capacity to handle the solution?
• Do we currently possess the necessary technology?

Page 33
2) Organizational Feasibility

Operational feasibility is dependent on human resources available for the

project and involves projecting whether the system will be used if it is
developed and implemented.

Operational feasibility is a measure of how well a proposed system solves the

problems, and takes advantage of the opportunities identified during scope
definition and how it satisfies the requirements identified in the requirements
analysis phase of system development.

Operational feasibility reviews the willingness of the organization to support

the proposed system. This is probably the most difficult of the feasibilities to
gauge. In order to determine this feasibility, it is important to understand the
management commitment to the proposed project.

The essential questions that help in testing the operational feasibility of a

system include the following:

• Does current mode of operation provide adequate throughput and

response time?
• Does current mode provide end users and managers with timely,
pertinent, accurate and useful formatted information?
• Does current mode of operation provide cost-effective information
services to the business?
• Could there be a reduction in cost and or an increase in benefits?
• Does current mode of operation offer effective controls to protect
against fraud and to guarantee accuracy and security of data and
information?
• Does current mode of operation make maximum use of available
resources, including people, time, and flow of forms?

Page 34
• Does current mode of operation provide reliable services
• Are the services flexible and expandable?

Page 35
3) Economic Feasibility Study

Economic analysis could also be referred to as cost/benefit analysis. It is the

most frequently used method for evaluating the effectiveness of a new system.
In economic analysis the procedure is to determine the benefits and savings
that are expected from a candidate system and compare them with costs.

If benefits outweigh costs, then the decision is made to design and implement
the system. An entrepreneur must accurately weigh the cost versus benefits
before taking an action.
Possible questions raised in economic analysis are:
• Is the system cost effective?
• Do benefits outweigh costs?
• The cost of doing full system study
• The cost of business employee time
• Estimated cost of hardware
• Estimated cost of software/software development
• Is the project possible, given the resource constraints?
• What are the savings that will result from the system?
• Cost of employees' time for study
• Cost of packaged software/software development
• Selection among alternative financing arrangements
(rent/lease/purchase)

The economic feasibility will review the expected costs to see if they are in-
line with the projected budget or if the project has an acceptable return on
investment.

At this point, the projected costs will only be a rough estimate. The exact costs
are not required to determine economic feasibility. It is only required to
determine if it is feasible that the project costs will fall within the target budget
or return on investment.

Page 36
 4) Alternative Matrix
In simple words, the Alternative matrix is mainly used to point out the advantages and
disadvantages of many alternatives to find out the best choices.

An alternative matrix contains all the pros and cons of a design (Technical, economical,
legal, operational feasibility, etc.), which then can be compared with other designs to
choose the most efficient design among alternatives.

For instance, your boss has put you in charge of taking on a new outsourced IT supplier.
You've already identified several different suppliers, and you now need to decide which
one is the best ones.

You could decide to go with the low-cost option. But you don't want to make your
decision on cost alone – Factors such as contract length, underlying technology, and
service levels need to be taken into consideration. So how can you make sure you make
the best decision, while taking all of these different factors into account?

Factors Shipment Reliability Efficiency Area Quality Final

Distributor A 3 6 2 9 5 25

Distributor B 1 5 2 7 9 24

Distributor C 3 2 6 8 3 22

Distributor D 5 9 2 9 5 30

Table 7: Alternative Matrix Example

REFERENCES
Page 37
• W3Computing Official Website. [online] Available at:

https://www.w3computing.com/systemsanalysis/feasibility-study

• MindTools Official Website. [online] Available at:

https://www.mindtools.com/pages/article/newTED_02.htm

• Stackify Official Website. [online] Available at:

ttps://stackify.com/sdlc-models-in-2019-how-theyve-aged-and-whats-current

• phoenixNap Official Website. [online] Available at:

https://phoenixnap.com/blog/software-development-life-
cycle#:~:text=Software%20Development%20Life%20Cycle%20is,%2C%20Test%2C%2
0Deploy%2C%20Maintain.

• wikipedia Official Website. [online] Available at:

https://en.wikipedia.org/wiki/Systems_development_life_cycle

• SoftwareTestingHelp Official Website. [online] Available at:

https://www.softwaretestinghelp.com/software-development-life-cycle-sdlc/

• ProductPlan Official Website. [online] Available at:

https://www.productplan.com/learn/software-development-lifecycle/

• JavaTpoint Official Website. [online] Available at:

https://www.javatpoint.com/software-engineering-software-development-life-cycle

• RobertHalf Official Website. [online] Available at:

https://www.roberthalf.com.au/blog/employers/6-basic-sdlc-methodologies-which-
one-best
• AgileTech Official Website. [online] Available at:

https://agiletech.vn/top-software-development-life-cycle-models/

Page 38
Page 39
Page 40
Page 41
Page 42
Page 43