CHAPTER III

Research Methodology
Research Methodology this chapter present the methods and procedures
to be followed by the researcher in conducting the investigations. It covers the
research design, research locale, research population, research instrument and
data gathering procedures that is used to present and interpret the data to be
collected.
Research Design
This study utilized the descriptive type of research. It describe the level of
awareness of software update on android phone by selected g11 students in
College of Sciences, Technology and Communications Inc.
Research Locale
The study was conducted through the participation of the Selected G11
Students of CSTC Located at Gen. Luna St. Maharlika Highway Arellano Subd.
Sariaya, Quezon. This institution was founded by Dr. Nelson D. Mendoza last
1991 and it is running for over 29 years. This research is mainly concerned with
widely known the Level of Awareness of Software Update on Android Phone in
College of Sciences, Technology and Communications Inc.

Figure 2. Map of CSTC Inc. Sariaya, Quezon

Respondent of the Study
Respondent of the study This study has fifty (50) selected g11 students in
College of Sciences, Technology and Communications Inc. as their respondent.
The respondent are the students from College of Sciences, Technology and
Communications Inc. the researchers looked for those willing or who are
available to be part of the study.

Strand Population Percentage Sample Size

GAS P1 S1
ABM P2 S2
HUMSS P3 S3
STEM P4 S4
IAA P5 S5
IAE P6 S6
ICT P7 S7
HE P8 S8

Sampling Technique Used

In this study, the researchers used stratified sampling in choosing their
sampling population. The stratified sampling is a process of subdividing the
population into subgroups or strata and drawing members at random from each
subgroup or stratum. The chosen respondents are 50 selected G11 students of
CSTC Inc. Sariaya, Quezon.

Research Instrument
This research used a sub structured questionnaire from the research
based on the topic of the study. The researchers read get different information
that gathered from the reliable sources that support the research study.

Data Gathering Procedures

The researchers got the data needed to the selected respondents in the
College of Sciences, Technology and Communications Inc. Before conducting a
survey, the researchers prepared a survey questionnaire and the researchers
asked permission of the Senior High School Principal. Followed by conducting a
survey. After getting all the data needed the researchers analyzed the results at
the research conducted and the conclusion of the study and recommendations
based on the results.

Validations of the Questionnaire

The researchers made 15 statements per variable to gather information for
the study. The researchers referred to different to different material such as
books and other unpublished thesis related to the chosen field of the study to be
able to gather information in support of the study. All the information that the
researchers gathered was presented to their research adviser for some
consultation, recommendation, and revision.
Statistical Treatment of Data
After the retrieval of the questionnaire, the researchers tabulated the
process and computed the data they gathered to have a desire results.
Variations of statistical tools were used by the researchers in the treatment of
data to determine demographic profile of the respondents the Frequency and
Percentage Distribution was used
The formula
P=f
× 100
n

Frequency Percentage
P – Percentage
F – Frequency
N – Total Respondents
2. Weighted Mean
The gathered data by the researchers were tabulated, analyzed and
interpreted. Using the Weighted Mean. The statistical tool was used for problem
number 2, to determine the significance of using motion feature sim creating
Power Point presentation by Selected G11 Students in College of Sciences,
Technology and Communications Inc.
 The formula weighted mean was :
WM = 4f + 3f + 2f + 1f

Where
F = frequency
N = total number of respondents

3. Genera
GWM = bk h

Where:
WM = weighted Mean
N= Number of Statements
Continuum Scale Value
Interval Interval Scale Verbal Interpretation
4 3.26 - 4 Highly Aware
3 2.51 – 3. 25 Aware
2 1.76 – 2.50 Less Aware
1 1 – 1.75 Not Aware
Table 2. Continuum Value of Rating
Level of Awareness of Software Update on Android Phone by Selected G11
Student in College of Sciences, Technology and Communications Inc.

RESEARCHER
Palino, Kathleen
Rodrigo, Angelika B.
Saron, Kyla Mae
Rosal, Ken

March 2020
 Chapter I
Introduction

This topic talks about the Level of awareness of Software Update on

Android Phone by Selected G11 Students in College of Sciences, Technology
and Communications Inc. and there are lot of reason here are 5 that show why
it’s important to update software regularly, Software updates do a lot of things
Software updates offer plenty of benefits. It’s all about revisions. These might
include repairing security holes that have been discovered and fixing or removing
computer bugs. Updates can add new features to your devices and remove
outdated ones. While you’re at it, it’s a good idea to make sure your operating
system is running the latest version.

Software updates help protect your data, you probably keep a lot of documents
and personal information on your devices. Your personally identifiable
information from emails to bank account information is valuable to
cybercriminals. They can use it to commit crimes in your name or sell it on the
dark web to enable others to commit crimes. If it’s a ransomware attack, they
might encrypt your data. You might have to pay a ransom for an encryption key
to get it back. Or, worse, you might pay a ransom and not get it back. Updating
your software and operating systems helps keep hackers out.

You deserve the latest and greatest, updates not only patch security holes, they
can also add new features and improve existing ones. You don’t want to fall
behind the times, right? In that way, software updates really are all about you.
Your software program may get a new shot of stability no more crashing. Or an
update might boost program performance more speed. You deserve no less. You
could ignore those reminders to update your software, but you might be missing
out on a lot, starting with your cyber security. Another option? If you’re still not
keen on clicking “Update now,” you may be able to configure your devices to
update automatically. If so, your problem is solved.
This study aims This study aims to determine the "Level of Awareness of
Software Update on Android Phone by Selected Student in College of Sciences,
Technology and Communications Inc." The researchers will determine the effects
of level of awareness of software update on android phone in performance and
compatibility.

Background of the Study

In 1946, software was not yet the programs stored in the memory of stored-
program digital computers, as we now understand it. The first electronic
computing devices were instead rewired in order to "reprogram" them. In 2000,
Fred Shapiro, a librarian at the Yale Law School, published a letter revealing that
John Wilder Tukey's 1958 paper "The Teaching of Concrete Mathematics"
contained the earliest known usage of the term "software" found in a search of
JSTOR's electronic archives, predating the OED's citation by two years. This led
many to credit Tukey with coining the term, particularly in obituaries published
that same year, although Tukey never claimed credit for any such coinage. In
1995, Paul Niquette claimed he had originally coined the term in October 1953,
although he could not find any documents supporting his claim. The earliest
known publication of the term "software" in an engineering context was in August
1953 by Richard R. Carhart, in a Rand Corporation Research Memorandum

In 2018, we saw a great deal of innovation in the software industry; and no doubt,
it will continue this year as well. Naturally, this presents numerous opportunities
for entrepreneurs: either in creating innovative tech or in pioneering its
implementation and stealing a march over the competition. However, it's not
necessary that all innovative technology becomes successful; therefore you need
to exercise caution about spends on R&D or investments in new technology and
equipment. Be that as may, it is critical to know about upcoming trends, as that
helps in planning finances, and operations as well. We asked experts what they
thought would be trending in 2019, and got some interesting answers.
 The researchers became interested with this kind of topic because
nowadays almost everyone has an Android phone that is used on a daily basis to
get communication where you need to update software to make this a new
version of your software.This topic is interested because they find it useful to
update software updates that help Android phones because software
development has many changes that can help a phone. Software updates
improve the performance of an Android Phone and the compatibility of your
cellphone

Statement of the Problem

This study aimed to determine the Level of Awareness of Software Update

on Android Phone by Selected Student in College of Sciences, Technology and
Communications Inc.

Specifically, this study sought to answer the following question;

1.What is the Demographic profile of the respondents in terms of;

1.1.Age

1.2.Sex

2. What is the Level of awareness of software update on android phone in terms

of;

2.1. Performance

2.2. Compatibility

3.What implication can be drawn based on the results of the studies?

Conceptual Framework

" Proactve Software-update transparency via collectively signed skipchains

and verified builds" Software-update mechanisms are critical to the security of
modern systems, but their typically centralized design presents a lucrative and
frequently attacked target. In this work, we propose CHAINIAC, a decentralized
software-update framework that eliminates single points of failure, enforces
transparency, and provides efficient verifiability of integrity and authenticity for
software-release processes. Independent witness servers collectively verify
conformance of software updates to release policies, build verifiers validate the
source-to-binary correspondence, and a tamper-proof release log stores
collectively signed updates, thus ensuring that no release is accepted by clients
before being widely disclosed and validated. The release log embodies a
skipchain, a novel data structure, enabling arbitrarily out-of-date clients to
efficiently validate updates and signing keys. Evaluation of our CHAINIAC
prototype on reproducible Debian packages shows that the automated update
process takes the average of 5 minutes per release for individual packages, and
only 20 seconds for the aggregate timeline. We further evaluate the framework
using real-world data from the PyPI package repository and show that it offers
clients security comparable to verifying every single update themselves while
consuming only one-fifth of the bandwidth and having a minimal computational
overhead.

Research Paradigm

Independent Variable Dependent Variable

Software Update

 Performance Level of Awareness

 Compatibility
Figure 1. The figure shows the independent and dependent variables that the
researchers acquired to complete this study. The level of Awareness in terms of
(1) Performance, (2) Compatibility that served as the independent variables while
the level of Awareness of Software Update on Android Phone served as the
dependent variable in the study.

Scope and Limitations

This study focuses of the level of awareness in selected students in

CSTC Sariaya Inc. They were selected as respondents because they are
individual who usually owns a cellphone that that the software can be updated.
So our most frequently overlooked are the selected student in CSTC Sariaya.

Significance of the Study

The study on Level of Awareness of Software Update on Android Phone

by Selected G11 Student in College of Sciences, Technology and
Communications Inc. was significant and beneficial to the following.

To the user

This study they will know how much effective the Updating the Software to
their android phone.

To the students

With this study they will knows what is Software Update and also know
how it work.

To the researcher
 With this study they will gain an in depth understanding and know
knowledge about the level of awareness of Software Update on Android Phone
to the selected students of CSTC.

To the future researcher

The result of study would serve as references for future researchers with
similar study.

Definition of terms

This includes the meaning of the unfamiliar words that were used in this
study. The meaning of each word is based on its uses in the research study and
defines operationally.

Android. A powerful, high-tech smartphone that runs on the Android operating

system (OS) developed by Google and is used by a variety of mobile phone
manufacturers. Pick an Android mobile phone and you can choose from
hundreds of great applications and multitask with ease.

Compatibility. The capacity for two systems to work together without having to

Operating System. An operating system, or "OS," is software that

communicates with the hardware and allows other programs to run.

Security. Means safety, as well as the measures taken to be safe or protected.

Software. is a collection of data or computer instructions that tell the computer

how to work. This is in contrast to physical hardware, from which the system is
built and actually performs the work. In computer science and software
engineering, computer software is all information processed by computer
systems, programs and data.

Software versioning. A way to categorize the unique states of computer

software as it is developed and released. The version identifier can be a word, or
a number, or both. For example, version 1.0 is commonly used to denote the
initial release of a program.

Update. A more recent, and usually improved, form of something, especially

something that is regularly changed: Each software update has a version
number.
 Chapter II

Related Review Literature

Foreign Literature

According to Fleischmann (2016), Although software updates are a

ubiquitous phenomenon in professional and private IT usage, they have to date
received little attention in the IS post-adoption literature. Drawing on expectation-
confirmation theory and the IS continuance literature, we investigate whether,
when and how software updates affect users' continuance intentions (CI). Based
on a controlled laboratory experiment, we find a positive effect of feature updates
on users' CI. According to this effect, software vendors can increase their users'
CI by delivering features through updates after a software has been released and
is already used by customers. We also find that users prefer frequent feature
updates over less frequent update packages that bundle several features in one
update. However, the positive effect from updates occurs only with functional
feature updates and not with technical non-feature updates, disclosing update
frequency and update type as crucial moderators to this effect. Furthermore, we
unveil that this beneficial effect of feature updates operates through positive
disconfirmation of expectations, resulting in increased perceived usefulness and
satisfaction. Implications for research and practice as well as directions for future
research are discussed. We investigate the effect of software updates on users'
continuance intentions. We find a positive effect of feature updates on users'
continuance intentions. Update frequency and update type are crucial
moderators to this effect. This effect operates through positive disconfirmation of
expectations.

According to Lund (2020), New software "streams" data and code

resources to an app from a cloud server when necessary, allowing the app to use
only the space it needs on a phone at any given time.
The software seamlessly shuffles data between an app and a cloud server
without stalling the game. Most study participants didn't notice any differences in
their gaming experience while the app used App Streamer.

Streams is a new software source of code and data from a server and only the
necessary phone is allowed to use the app and only if it needs a phone.

According to Mathur (2018), Software updates are critical to the

performance, compatibility, and security of software systems. However, users do
not always install updates, leaving their machines vulnerable to attackers'
exploits. While recent studies have highlighted numerous reasons why users
ignore updates, little is known about how prevalent each of these beliefs is.
Gaining a better understanding of the prevalence of each belief may help
software designers better target their efforts in understanding what specific user
concerns to address when developing and deploying software updates. In our
study, we performed a survey to quantify the prevalence of users' reasons for not
updating uncovered by previous studies. We used this data to derive three
factors underlying these beliefs: update costs, update necessity, and update
risks. Based on our results, we provide recommendations for how software
developers can better improve users' software updating experiences, thereby
increasing compliance and, with it, security.

For this reason, most people are not aware of software updates so they are not
discovering the latest or they are not experiencing the improved performance or
speed of their gadgets.

According to Shiba (2014), A vehicle-mounted software updating

apparatus for performing a software update by downloading software from
outside a vehicle includes a storage unit storing a past on/off status of an
accessory (ACC); a software update period determining unit determining a
software update period in which software update is to be performed based on
information in the storage unit such that the software update is performed in an
ACC-off period; and a software update performing unit performing the software
update in the software update period determined by the software update period
determining unit.

According to Schwiebert (2010), Mac OS X Server can also run as a

Software Update server and share updates with other Mac OS X clients. The
Software Update service mirrors updates from the Apple Software Update
service that you use by default when running Software Update. This helps keep
larger Apple updates for operating systems and Apple software packages from
taking up all of your Internet connection when 5 or 500 computers go to
download that update all at the same time.

Local Literature

According to Galibus (2020), We propose the secure procedure for the

automated railway update and maintenance. The proposed procedure is derived
from the Uptane update framework. Testing and validation phase, additional
manual approval procedure and update progress control are integrated into the
Uptane framework in order to conform to the railway safety requirements and
norms. The possible metadata and repository customization is proposed and
specific railway update attacks are discussed.

According to Ruopeng (2020), Software update is the process of updating

software running on computing devices. It allows computing devices to download
and to install software packages and patches in real time. This is an important
feature for managing the computing devices in a distributed network, as it saves
the trouble of having to either recall the devices back to the manufacturers or
send field engineers to remote locations to maintain the devices. Without
authentication, software update can be exploited to distribute trojan horses,
viruses, or other malicious programs. Previous approaches to software update
either use no authentication at all, or use conventional digital signatures that are
inefficient for authenticating partial updates such as patches. In our research, we
solve two problems, 1) how to distribute software updates to devices so that the
devices can efficiently authenticate the data that is received, and 2) how to
restrict devices to run only the authenticated software that is authorized for the
devices. We design and develop a client-server software update system, which
uses an on-the-fly signature generation scheme to provide data authentication to
a dynamic bundle of various software packages. With our scheme, each bundle
is authenticated by a single digital signature. Compared with conventional
software update systems where each software package within a bundle has to be
individually signed, our scheme reduces the computation for the server to
generate the signature and for the client to verify it. For client devices which has
an embedded trusted computing module (TCM), by using a single signature for a
bundle instead of one signature per software package inside the bundle, our data
authentication scheme can prevent the bundle from being modified by adding or
removing signed software packages. Using one signature for a bundle, with
conventional fingerprint algorithms this means any change to the bundle will incur
the whole bundle to go through the underlying hashing process of the fingerprint
algorithm. We devised two incremental fingerprint algorithms. When the bundle is
partially updated, by using our incremental fingerprint algorithms, the fingerprint
of the bundle can be quickly updated by incorporating to the fingerprint of the
original bundle with the fingerprints of those packages that are actually changed.
Experiments show that our fingerprint update cost is proportional to the size of
the data that is modified.

According to Tanaka (2017), Traceability is important knowledge for

improving the artifacts of software and systems and processes related to them.
Even in a single system, various kinds of artifacts exist. Various kinds of
processes also exist, and each of them relates to different kinds of artifacts.
Traceability over them has thus large diversity. In addition, developers in each
process have different types of purposes to improve their artifacts and process.
Research results in traceability have to be categorized and analyzed so that such
a developer can choose one of them to achieve his/her purposes. In this paper,
we report on the results of Systematic Literature Review (SLR) related to
software and systems traceability. Our SLR is preliminary one because we only
analyzed articles in ACM digital library and IEEE computer society digital library.
We found several interesting trends in traceability research. For example,
researches related to creating or maintaining traceability are larger than those
related to using it or thinking its strategy. Various kinds of traceability purposes
are addressed or assumed in many researches, but some researches do not
specify purposes. Purposes related to changes and updates are dominant.

Android is an open source software stack for a wide range of mobile

devices and a corresponding open source project led by Google (Google, 2015)
and has dominated the smartphone OS market with 78.0% market share
(International Data Corporation, 2015). It’s open-source nature and its large cut
of the market share translates to more potential users for app developers. On the
other hand, iOS is a mobile operating system developed for the solely for use by
iPhone and iPad devices by Apple Inc. Applications or Apps developed for the
Android Platform must are sent to Google through Google Play, the official app
store of the Android Platform owned and developed by Google.

According to Godwin (2011), Not long ago, phones are dumb. Their only
purpose is to receive and send texts messages also, to initiate and receive
phone calls. With the introduction of smartphones, these devices are now able to
increase user experience and productivity through apps. Phones are now
portable computers. This idea gained tremendous attention from developers,
companies, and even educators. “Mobile learning (often “m-learning”) is in itself
not new, but new devices with enhanced capabilities have dramatically increased
the interest level, including among language educators.”

Related Review Studies

Foreign Studies

According to Dektas (2019), New research from Lancaster University, the

University of Illinois and Texas Tech University shows new firms commonly
establish headquarters within a mile of existing software businesses. However,
while this makes recruitment easier, there is no evidence of increased profitability
as a result. The study, published in the Journal of Economic Behavior &
Organization, looks at software firms in Texas over a six-year period. There were
431 new establishments in this time, and software firms regularly set up close to
established businesses, with an average of 10 within one mile, employing 394
workers between them. Across the sample period, the number of establishments
dropped from a high of 648 in late 2002 to 581 at the end of 2006, but
employment rose from 16,600 to 21,000. The research found sustained
employment in the software sector in the areas of business clustering came not
from the growth of firms, but rather from new companies taking on employees
from those already in place. The study suggests that new firms setting up closer
to established businesses are instead negatively affected by the presence of
other firms in terms of the total jobs created. These companies do not grow faster
that those located in isolation, rather job losses at one business are more likely to
be compensated by other firms capturing the employees, explaining the
persistence of employment within the sector in certain areas.

"We found that clusters of software establishments within small geographic areas
are highly persistent, as is employment across the sector -- though not within
individual companies," said co-author Professor Dakshina De Silva, of Lancaster
University Management School.

The mobile arena is fought by numerous OS today namely, Microsoft’s

Windows Phone, Nokia’s Symbian OS, Blackberry’s Black BerryOS, but are
dominated by the two most popular

Operating Systems today, Android and iOS. Android is an open-source

operating system developed by Google, and iOS, the mobile operating system
developed by Apple Inc. for its iPadand iPhone devices. The study conducted by
Mark H. Goadrich and Michael P. Rogers entitled “Smart Smartphone
Development: iOS vs. Android” discusses the mobile space dominated by
Android and iOS . iOS development requires a Macintosh computers running
Mac OS. These computers are built solely by Apple and have relatively high cost
compared to Windows-powered and Linux-based computers. An iOS device also
costs relatively higher than their Android counterparts, for example, a no-
contract, 64GB iPhone 6S costs $749.00 USD or 34,221.06Philippine Peso
(10:30AM October 10, 2015 / USD 1 = PhP 45.69) if bought in the Apple US
Website. The development cost of iOS apps equates to be much higher given
that a beginning developer have to invest in an Apple product. On the other
hand, Android can be developed using any of the current major operating
systems such as Windows (XP or higher), Mac OSX (10.5.8 orhigher) and Linux
systems (running with kernel 2.6 or higher) (Goadrich & Rogers, 2011). With this,
almost 95.34% (Net Applications.com, 2015) or almost all of desktop users can
develop apps for Android. That said, the cost for developing Android apps is
lower as you can use your existing compatible computer to jumpstart your
Android career.

According to Nadi (2018), Many phone vendors use Android as their

underlying OS, but often extend it to add new functionality and to make it
compatible with their specific phones. When a new version of Android is
released, phone vendors need to merge or re-apply their customizations and
changes to the new release. This is a difficult and time-consuming process,
which often leads to late adoption of new versions. In this paper, we perform an
empirical study to understand the nature of changes that phone vendors make,
versus changes made in the original development of Android. By investigating
the overlap of different changes, we also determine the possibility of having
automated support for merging them. We develop a publicly available tool chain,
based on a combination of existing tools, to study such changes and their
overlap. As a proxy case study, we analyze the changes in the popular
community-based variant of Android, Lineage OS, and its corresponding Android
versions. We investigate and report the common types of changes that occur in
practice. Our findings show that 83% of subsystems modified by Lineage OS are
also modified in the next release of Android. By taking the nature of overlapping
changes into account, we assess the feasibility of having automated tool support
to help phone vendors with the Android update problem. Our results show that
56% of the changes in Lineage OS have the potential to be safely automated.
 According to Gamba (2020), The open-source nature of the Android OS
makes it possible for manufacturers to ship custom versions of the OS along with
a set of pre-installed apps, often for product differentiation. Some device vendors
have recently come under scrutiny for potentially invasive private data collection
practices and other potentially harmful or unwanted behavior of the preinstalled
apps on their devices. Yet, the landscape of preinstalled software in Android has
largely remained unexplored, particularly in terms of the security and privacy
implications of such customizations. In this paper, we present the first large scale
study of pre-installed software on Android devices from more than 200 vendors.
Our work relies on a large dataset of real-world Android firmware acquired
worldwide using crowd-sourcing methods. This allows us to answer questions
related to the stakeholders involved in the supply chain, from device
manufacturers and mobile network operators to third party organizations like
advertising and tracking services, and social network platforms. Our study allows
us to also uncover relationships between these actors, which seem to revolve
primarily around advertising and data-driven services. Overall, the supply chain
around Android’s open source model lacks transparency and has facilitated
potentially harmful behaviors and back doored access to sensitive data and
services without user consent or awareness. We conclude the paper with
recommendations to improve transparency, attribution, and accountability in the
Android ecosystem.

According to Malhotra (2015), Software maintenance is an expensive

activity that consumes a major portion of the cost of the total project. Various
activities carried out during maintenance include the addition of new features,
deletion of obsolete code, correction of errors, etc. Software maintainability
means the ease with which these operations can be carried out. If the
maintainability can be measured in early phases of the software development, it
helps in better planning and optimum resource utilization. Measurement of
design properties such as coupling, cohesion, etc. in early phases of
development often leads us to derive the corresponding maintainability with the
help of prediction models. In this paper, we performed a systematic review of the
existing studies related to software maintainability from January 1991 to October
2015. In total, 96 primary studies were identified out of which 47 studies were
from journals, 36 from conference proceedings and 13 from others. All studies
were compiled in structured form and analyzed through numerous perspectives
such as the use of design metrics, prediction model, tools, data sources,
prediction accuracy, etc. According to the review results, we found that the use of
machine learning algorithms in predicting maintainability has increased since
2005. The use of evolutionary algorithms has also begun in related sub-fields
since 2010. We have observed that design metrics is still the most favored option
to capture the characteristics of any given software before deploying it further in
prediction model for determining the corresponding software maintainability. A
significant increase in the use of public dataset for making the prediction models
has also been observed and in this regard two public datasets User Interface
Management System (UIMS) and Quality Evaluation System (QUES) proposed
by Li and Henry is quite popular among researchers. Although machine learning
algorithms are still the most popular methods, however, we suggest that
researchers working on software maintainability area should experiment on the
use of open source datasets with hybrid algorithms. In this regard, more
empirical studies are also required to be conducted on a large number of
datasets so that a generalized theory could be made. The current paper will be
beneficial for practitioners, researchers and developers as they can use these
models and metrics for creating benchmark and standards. Findings of this
extensive review would also be useful for novices in the field of software
maintainability as it not only provides explicit definitions, but also lays a
foundation for further research by providing a quick link to all important studies in
the said field. Finally, this study also compiles current trends, emerging sub-fields
and identifies various opportunities of future research in the field of software
maintainability.

Local Studies
 According to Rachel (2013), The usefulness of mobile devices has
increased greatly in recent years allowing users to perform more tasks in a
mobile context. This increase in usefulness has come at the expense of the
usability of these devices in some contexts. We conducted a small review of
mobile usability models and found that usability is usually measured in terms of
three attributes; effectiveness, efficiency and satisfaction. Other attributes, such
as cognitive load, tend to be overlooked in the usability models that are most
prominent despite their likely impact on the success or failure of an application.
To remedy this we introduces the PACMAD (People At the Centre of Mobile
Application Development) usability model which was designed to address the
limitations of existing usability models when applied to mobile devices. PACMAD
brings together significant attributes from different usability models in order to
create a more comprehensive model. None of the attributes that it includes are
new, but the existing prominent usability models ignore one or more of them.
This could lead to an incomplete usability evaluation. We performed a literature
search to compile a collection of studies that evaluate mobile applications and
then evaluated the studies using our model.

According to Fagan (2015), Prior studies report that computer users are
often confused by software update messages. This study complements prior
efforts by examining the relationship between self-reported ratings of specific
software types and users self-reported measure of confusion, annoyance, and
message noticeability for different software types using data gathered via two
surveys (N1 = 78, N2 = 172) from anonymous computer users. The survey
results showed that participants are commonly hesitant to apply updates, even
though they report caring a lot about computer security and privacy, a trend
which applies to many different software. Annoyance and confusion with
messages were common complaints from our participants. Also, the level of
reported annoyance and/or confusion with a software’s messages proved a
predictor of participants’ hesitation in applying the updates for some software we
tested. Finally, we use data gathered as participants viewed real-world update
messages to highlight and explain some “good” and “bad” update/warning
messages as well as draw connections between the emotions annoyance,
confusion, importance, and noticeability.

According to Blaze (2019), Subverting a software update system (a type

of “supply chain attack” in security parlance) is usually associated with
international espionage and intelligence operations — not with run-of-the-mill
attempts to steal credit card numbers or banking passwords — and for good
reason. It requires considerable resources and skill because the hardware and
software companies’ systems that have to be compromised are generally better
managed and more carefully secured than those of individual consumers. But
when they are successful, attacks against the supply chain are an especially
powerful threat: They rely not on repeatedly fooling each user into, say, opening
the wrong email attachment (a common way malware is spread), but on the trust
that users naturally and reasonably place in the suppliers that sold them their
hardware and software. It’s a dangerously effective way for the attacker to reach
many thousands of victims (or a few carefully selected targets).

According to Vaniea (2016), Updates alter the way software functions by

fixing bugs, changing features, and modifying the user interface. Sometimes
changes are welcome, even anticipated, and sometimes they are unwanted
leading to users avoiding potentially unwanted updates. If users delay or do not
install updates it can have serious security implications for their computer.
Updates are one of the primary mechanisms for correcting discovered
vulnerabilities, when a user does not update they remain vulnerable to an
increasing number of attacks. In this work we detail the process users go through
when updating their software, including both the positive and negative issues
they experience. We asked 307 survey respondents to provide two contrasting
software update stories. Using content analysis we analysed the stories and
found that users go through six stages while updating: awareness, deciding to
update, preparation, installation, troubleshooting, and post state. We further
detail the issues respondents experienced during each stage and the impact on
their willingness to update.
 According to Lazarus (2019), Update your software regularly, and as
soon as possible when a newer version comes out. What’s an even easier way?
Set the updates to happen automatically. Don’t ignore reminders to update.
Criminals look to exploit vulnerabilities before the software companies can fix it.
Delaying gives hackers time to access your information – even when a patch is
out there to lock them out.

Synthesis

By the following related studies and literature, the researcher can

determine the most effective way to stimulate ideas and understand the content
of an article or literature and reason why it happens. In the over all of this study
authors defend their statement about software update, they give their theory and
give some supporting details to prove their opinion. Some author say that update
regularly your software to update your security patch. New software improves
the ability to remain unchanged over time and different conditions.
References

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

https://www.flatworldsolutions.com/IT-
services/articles/ttps://www.sciencedirect.com/science/article/pii/S074756321500
3854

https://www.sciencedirect.com/science/article/pii/S1319157818306074

https://www.researchgate.net/publication/302794533_Vehicle-
mounted_software_updating_apparatus

https://www.researchgate.net/publication/45062918_Authenticated_software_upd
ate

https://www.sciencedaily.com/news/computers_math/software/58

https://www.sciencedaily.com/news/computers_math/software/

https://www.sciencedirect.com/science/article/pii/S0747563215003854