See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/322072677

An Overview of Software Functionality Service: A Systematic Literature

Review

Article  in  Procedia Computer Science · January 2017

DOI: 10.1016/j.procs.2017.12.163

CITATIONS READS

9 751

3 authors, including:

Mahadi Bahari Nor Hidayati Zakaria

Universiti Teknologi Malaysia Universiti Teknologi Malaysia
55 PUBLICATIONS   160 CITATIONS    54 PUBLICATIONS   327 CITATIONS   

SEE PROFILE SEE PROFILE

Some of the authors of this publication are also working on these related projects:

E-Government View project

E-Commerce Implementation Process Framework for B2C Malaysian Small and Medium Enterprise View project

All content following this page was uploaded by Mahadi Bahari on 27 January 2019.

The user has requested enhancement of the downloaded file.

 Available online at www.sciencedirect.com

ScienceDirect
Procedia Computer Science 00 (2017) 000–000
www.elsevier.com/locate/procedia

The 4th Information Systems International Conference (ISICO 2017)

An Overview of Software Functionality Service: A Systematic

Literature Review
Masrina A. Salleh*, Mahadi Bahari, Nor Hidayati Zakaria†
Department of Information Systems, Faculty of Computing, Universiti Teknologi Malaysia, Malaysia.

Abstract

This study focuses in contributing a literature on software functionality service area. We aim to provide an overview of software
functionality service related to its research activity, investigated the major themes and identified the focus on its sub-
characteristics addressed. In doing this, we employed a Systematic Literature Review (SLR) approach by reviewing all relevant
articles from four online databases (i.e., IEEE, Springer, ScienceDirect and EmaraldInsight) and finally identified only 79
relevant articles to our research questions. We categorized the articles into its major themes discussed and its sub-characteristics
addressed. It is found that there are increased of researched related to software functionality service for the last five years mainly
in functionality service development while there is still lack of research coverage on functional compliance sub-characteristics.
Future work should be included of reviewing a greater number of articles from more various types of journal and workshop.
© 2017 The Authors.Published by Elsevier B.V.
Peer-review under responsibility of the Conference Program Chairs.

Keywords:functionality service; software functionality quality; systematic literature review; Okoli guideline

1. Introduction

The existence of software has shifted the way of company, manufacturing, firms and individual people perform
and coordinate their job. Its impact on the worldwide economy, environment and society in the context of
innovations increase, enhanced productivity and improved social knowledge cannot be denied 6,8,15,20. Furthermore,
the machine, computer hardware and any electronic equipment depends on software to be functioned, they require

*
Corresponding author.
E-mail address:nikakmalsalleh@yahoo.com.my (M.A. Salleh)

1877-0509© 2017 The Authors. Published by Elsevier B.V.

Peer-review under responsibility of the Conference Program Chairs.
2 M.A. Salleh,M. Bahari,N.H. Zakaria/ Procedia Computer Science 00 (2017) 000–000

each other and neither can be realistically used on its own. This make the quality of the software has become one of
the important factor in determining the success of technical or commercial systems performance 28,34.
Software functionality service quality reflects how well it complies with or conforms to a given design, based on
functional requirements or specification. It can also be described as the fitness for purpose of a piece of software 4,26
or how it compares to competitors in the marketplace as a worthwhile product 4. Even though the software
functionality service is one of the importance attributes towards software quality, there is still lack of review in
software functionality service research and practice33,34,50. Thus, this paper provides a report on our finding of the
basic knowledge on the software functionality service through systematic literature review approach as a guide to
the researches who are motivated to investigate further into this topic. The research questions of this study are as
follows:
RQ1: What is the trend on software functionality service research for the last 5 years (2013 until 2017)?
RQ2: What are the major themes on software functionality service research are being addressed?
RQ3: What are the software functionality service sub-characteristics are being addressed?
Our research aim is to support the software functionality service awareness in the context of the current major
theme discussed and focus on software functionality service sub-characteristics addressed. In achieving this aim, we
need to enhance on existing knowledge in software functionality service as well as in any related field to it. The
remainder of this study is organized as follows: Section 2 provides the background of software functionality service
and its historical development; Section 3 explains the research method used to conduct this review; Section 4 reveals
the research questions results; and finally, Section 5 presents the discussion and conclusion.

2. Related Work

This section summarizes the core definition of software functionality service and provides an overview of this
area.

2.1. Definition of software functionality service

In most discussion of software quality, the term of software functionality service is applied almost specifically to
the functionality suitability with major focus on functional correctness in performing the tasks it’s intended to do for
its users4,8,33. Functionality is one of the attributes for software quality. An international standard (ISO 25062:
2011)5, generally defines functionality as what the system does and the purpose of the system. In information
technology, software functionality is any aspect of software application or any computing device can perform for a
user15,19,25. While in the context of software architecture, the term “service” refers to software functionality or a set
of software functionalities with the purpose of reusable by different clients for different purposes 2. In another
studies, the software functionality service is defined as an instrument which enables to perform various tasks, where
the interface and functions provided are consistent with rules and regulation by the service description 7,18,32,44. Thus
for the purpose of this study, we define our understanding of software functionality service as "a set of functions and
their specified properties with satisfy stated or implied needs."

2.2. Diversify on software functionality service studies

There are few studies done on software functionality service previously. For instance, Miguel4 performed a
review on overall software product performance including its functionality service by using the software quality
model while Zhang55 reviewed on functions related to big data and Nair 3 was specifically focus on functional
security. To enrich our understanding, it is needs to review articles that specifically discussed on any software
functionality service from diversify scientifically venues and journals in various software functionality service from
other domains.
 M.A. Salleh, M. Bahari, N. H. Zakaria/ Procedia Computer Science 00 (2017) 000–000 3

3. Review Method

To answer the research questions, this study uses the eight-step Guide for SLR by Okoli1. The steps are: 1)
purpose of the review, 2) protocol and training, 3) searching for the literature, 4) practical screen, 5) quality
appraisal, 6) data extraction, 7) synthesis of the studies, and 8) writing the review. The Okoli guideline1 was
constructed based on the SLR guide from social sciences, management, and software engineering fields which are
pertinent to information systems researchers. The details of each step will be described below.

3.1 Review protocol

The goal of review protocol is to reduce research bias. It describes all procedures in conducting this SLR which
includes formulating the research questions and background of software functionality service (as explained in the
previous sections). Figure 1 illustrates the review protocol of this study.

Figure1: Review protocol on software functionality service

Review protocol
Phase 3: Quality
Phase 1: Identify RQ Phase 2: Search strategy and practical screen Phase 4: Results and reporting
appraisal

Automatic search online

databases using keywords:
Read abstract,
IEEE, ScienceDirect, Applied Inclusion & section title, Apply quality
Identify research SpringerLink, Emarald Exclusion criteria Data extraction Synthesis & results
discussion / assessment
questions Insight
conclusion
Process

RQ1: How much activities were there in

last 5 years?
RQ2: What are the research major Result Result Result Result
paper count= n Primary study Primary study Primary study Reporting
themes are being addressed?
Input / Output

RQ3: What are the software

functionality service sub-
characteristics are being
addressed?

3.2 Search strategy and practical screen

The articles retrieved for this study is based on an automated search of the following online database: IEEE
Explorer, Springer, ScienceDirect and EmaraldInsight. These databases are considered relevant and provide high
impact factor publication. To capture all results related to software functionality service, we used the following
keywords “software service functionality”, “software functionality service”and“software functionality”. Using
these keywords, we retrieved more than 2,000 articles. Following this automatic search strategy is
inclusion/exclusion criteria. Here, we apply relevant criteria (see Table 1) to give a sufficient number of articles that
can answer the research questions1.
Table 1: Inclusion and exclusion criteria.
Inclusion criteria Exclusion criteria
 Publication date: from “January 2013” until “December 2017  “Functionality service” used in the sense of
or present” other than software or computing environment
 English articles only
 Conference publications and journals only
 Sort of articles through “the most relevant” or “by relevance”
 Only full access articles

All results were sorted “by relevance” as displayed in the database. From these results, we only considered the
first 25 articles of every database. In this step, we read titles, abstract, section title, discussion as well as conclusion
for every relevant article of the primary studies. In total we reviewed 100 articles and only 79 articles were meeting
the inclusion and exclusion criteria. These 79 articles were then being further reviewed and were categorized
4 M.A. Salleh,M. Bahari,N.H. Zakaria/ Procedia Computer Science 00 (2017) 000–000

accordingly to the type of articles such as journal article or conference paper, major theme discussed and its sub-
characteristics are being addressed.

3.3 Quality appraisal

To ensure high quality and relevant primary studies, we used a number of validation actions as part of planning
and search phases. Here, we employed Kitchenham et al.58 criteria which consists of four assessment questions as
follows: QA 1: Are the review’s inclusion and exclusion criteria described and appropriate?; QA 2: Is the literature
search likely to have covered all relevant studies?; QA 3: Did the reviewers assess the quality/validity of the
included studies?; and QA 4: Were the basic data/studies adequately described? For QA 1, the inclusion criterion
used in the SLR is aligned with the inclusion criterion suggested by Kitchenhamet et al.58. For QA 2, we used the
online institution database, which is linked to a well-known vendor databases (e.g., IEEE Explorer, Springer,
ScienceDirect and EmaraldInsight). For QA 3, we limited the search to the peer-reviewed papers to enhance the
quality of included papers. For QA 4, papers with full text only were included. Additionally, these included papers
were further reviewed and filtered out papers based on the discussed exclusion criterion.

4. Results and Discussion

This section discusses the SLR findings based on the research questions.

4.1. RQ1: What is the trend on software functionality service research for the last 5 years (2013 until 2017)?

The period of time selected for this review is 5 years (2013-2017). The distribution of the studies through the
years is shown in Figure 2. Since majority of the studies were published in reliable and impact factor journals as
well as leading conference on information systems, the importance of this review increases. It depicted that for the
last five years, there was a significant increase of researches in the field of software functionality service with 3
publications in 2013, 5 publications in 2014, 14 publications in 2015 and the highest number of publication was
recorded in 2016 with 39 studies.
Figure 2: Summarized of articles accordingly to the years and type of publications.

4.2. RQ2: What are the major themes on software functionality service research are being addressed?

All 79 related articles were reviewed and categorized accordingly to the major theme discussed. We employed
the text analysis with repetition method59 to identify the themes by reading the abstract, section and conclusion of
each article. The more the same concept occurs in a text, the more likely it is a theme 59. Five major themes were
identified; 1) wireless network: grouped all articles that studied on functionality service in all type network
technologies such as 5G, 4G, 3G and others; 2) software application: consists of all articles that studied on
functionality service in a specific application such as ERP, EHR and others; 3) approach for evaluation: grouped all
articles that focus on methods used to evaluate the functionality service; 4) quality of service: grouped all the
studied on functionality service measurement performance of a service, such as in computer network, cloud
computing service or telephony service; 5) software functionality development: grouped all articles that specifically
 M.A. Salleh, M. Bahari, N. H. Zakaria/ Procedia Computer Science 00 (2017) 000–000 5

studied on the enhancement of either existing or new service functionality features in any software applications.
Table 2 depicted the number of articles accordingly to the major theme discussed per year. From all five major
themes, software functionality development was the main focus of the last five years researched with the total of 55
articles followed by 15 articles studied on quality of service, 4 articles studied on software application, 3 articles
studied on wireless network and only 2 article studied on approach for evaluation.

Table 2: Number of articles accordingly to the major theme discussed

Year / Wireless network Software application Approach for Quality Software functionality
themes (3G, 4G, 5G) (ERP, EHR) evaluation of service development

2013 0 0 0 2 1
2014 0 1 0 1 3
2015 0 1 1 3 9
2016 2 2 1 9 25
2017 1 0 0 0 17
TOTAL 3 4 2 15 55

4.3. RQ3: What were the software functional criteria sub-characteristics are being addressed?

Due to unsatisfied with the existing software applications such as enterprise resource system, electronic health
record, many companies were investing a huge amount of money and time in functional testing22,51. Among the
factors that contribute towards software application failure are response times21,38,46, infrastructure stability24,
component functionality issues between application layers25,36,41 and according to Klimov33 the major factor comes
from the software functionality service. This system application failures will result in lost revenue8, customer
dissatisfaction31,43,53, data inconsistencies11,17,39, and much more. In today complex infrastructure, companies should
take serious actions to properly handle these software risk factors. The costs or maintenance times spent due to this
unpredictable issue could be greatly hindering productivity35, performance54, or security of the systems22,30,36. Thus
in today’s trend of complex integrated technology environment, it is not a proper approach to deal with problems as
they become apparent. As software functionality service is one of software quality attributes, we need always to
monitor its performance and getting the most out of systems and applications. Table 3 depicted the focus of the
previous studies in the context of software functionality service sub characteristics for all five themes.

Table 3: Type of functional sub characteristics discussed in each themes.

Functionality service Wireless network Software application Approach for Quality of Software functionality
sub characteristics / (3G, 4G, 5G) (ERP, EHR) evaluation service development
themes

Suitability nil √ √ √ √
Accuracy nil √ √ √ √
Interoperability √ √ nil √ √
Compliance √ nil nil nil nil
Security √ √ √ √ √

4.3.1 Functional suitability

Functional suitability is the degree to which the functions carry out its basic functions or it does not5. It is
specially focuses on three types of functional suitability. First is functional completeness which is a degree to which
the set of functions covers all the specified tasks and user objectives5. Many users experience the unexpected
malfunction, unfriendly interface25, and confusing steps to perform even a simple task54. Most of the case was the
not well modifications towards the ease of use as well as usefulness of the functionality 49. For example, in the cloud
6 M.A. Salleh,M. Bahari,N.H. Zakaria/ Procedia Computer Science 00 (2017) 000–000

service environment due to its basic offered of functionality service resulted many of users requirement cannot be
full filled11,14,12. Second is functional correctness that is a degree to which a system provides the correct results with
the needed degree of precision5. The common issue is incorrect and ineffective data retrieval. For example, in
metadata management for a scientific data where the data is heterogeneous and subject to frequent change 39 that is
required for flexible data model which is currently does not yet exist 11,14,20. An ineffective data edit47 is another issue
where the edited data are failed to protect the incorrect data from being entered into the system. For example, in the
case of an alphanumeric55 field that still allows spaces to be entered before any numbers or letters in the address.
Therefore the result may not produce the correct data52 when searches are performed. Finally, functional
appropriateness which is a degree to which the functions facilitate the accomplishment of specified tasks and
objectives5. The issues are the software that is inflexible to meet business requirements and only part of software
functionality service are really utilized40. For example, a system that is difficult to modify in meeting organization's
needs or may lack of functionalities to allow the users to customize their business rules27,37.

4.3.2. Functional accuracy

Functional accuracy is defined by correspondence of the outcome with the slightest error5. With the trend of big
data, web environment and cloud computing, the issues in data process performance and accuracy become one of
major issues in software functionality service19,54. This issue occurred when the software fail to consistently deliver
correct results or the system is not performed the work correctly every time it is used. For example, Alfaries56
addressed on unreliable result and performance in the web environment and Evangelidis 29 found that higher
frequency of the incorrect data produced in geospatial data. The same scenario occurred in the cloud environment,
where the retrieved data were analysed and shared seems to be in a correct format, unfortunately it is not
accordingly to the search criteria when tracing back to the original source documents or data 17,20.

4.3.3 Functional interoperability

Functional interoperability is the ability of a system interacts with other systems without demanding additional
actions from the user5. Some of the issues in functional interoperability arise due to its interdisciplinary nature 42,
software engineering aspects7,10 and knowledge management supporting48 which resulted in huge system
complexity. As customer requirements become more diversified and unpredictable, it is challenging for service
providers to satisfy their various expectations and maintain a moderate network operation cost at the same time50.
Many software products were designed and developed for only one particular environment. It is become an issue
whenever the software is failed to integrate with a new technical requirement environment57. Mayer13 reported that
the e-government in the developed countries has been stagnating since 2005 due to the lack of software functionality
service integration specifically in the web services. It is a challenging task to integrate multiple systems that are
developed independently from each other with its own different design and software technology9,23,45.

4.3.4 Functional compliance

Functional compliance is the capability of the software product to adhere to standards, conventions or regulations
in laws and similar prescriptions relating to functionality5. Many businesses and government entities are struggling
to manage compliance requirements4. Some of the issues arise due to the using of older compliance software
products that are just not designed to deal with constant change 33. So, they become increasingly expensive to
upgrade, unfriendly to use and difficult to maintain. Even though functional compliance is one of software quality
attributes, unfortunately it has not been given much focus in the previous researches.

4.3.5 Functionality security

Functional security is the capability of the software to prevent unauthorized intrusions5. It was a range of
technical and operational requirements design to protect the resources and services from unauthorized actions
including destruction of data, information theft and network disruption30. Common issues in functional security are
an inadequate security controls6 such as lack of controlled in an authorization access levels as well as poor
 M.A. Salleh, M. Bahari, N. H. Zakaria/ Procedia Computer Science 00 (2017) 000–000 7

configured logging36 to sensitive data that will lead to a huge challenge in discovering what has happened if a breach
occurs6,30. According to the survey done by Business Horizon30 thirty five per cent of the databases assessed were
lack of security due to either missing security updates or were running on an old version of the software.

5. Conclusion

In this paper, we are aiming to create a foundation for the software functionality service research by exploring the
previous articles with the focus on the major theme discussed and the software functionality service sub-
characteristics were being addressed. The study employed SLR as a main approach to answer the research questions
by following the eight-step SLR guidelines from Okoli1. We considered 79 of 100 reviewed articles relevant with
respect to our research questions.
In conclusion, there are increased in number of researches done for the last five years with the focus on software
functionality service development. All five major themes focus on different functional sub characteristics and it is
clearly showed that the functional compliance sub characteristic is still lack of research. We considered this effort
could be valuable for both academic and practitioners. As the researches in this field continuously increase, these
findings can help the motivated researchers to get an overview where to position their own work. Future work
should extend the study by providing more various online databases with various dedicated journal searches.
Thereby, we can establish stable body of knowledge in the software functionality service field.

References

1. Okoli C, Schabram K. A Guide to Conducting a Systematic Literature Review of Information Systems Research. 2010.
2. Fitzgerald B. Continuous Software Engineering and Beyond: Trends and Challenges Categories and Subject Descriptors. 1-9.
3. Nair S, Luis J, Vara D, Sabetzadeh M, Briand L. An extended systematic literature review on provision of evidence for safety certification.
InfSoftw Technol,56(7), 2014, 689-717.
4. Miguel JP, Mauricio D, Rodríguez G. A Review of Software Quality Models for the Evaluation of Software Products. 5(6), 2014, 31-53.
5. Moumane K, Idri A, Abran A. Usability evaluation of mobile applications using ISO 9241 and ISO 25062 standards. Springerplus, 2016.
6. Penzenstadler B, Raturi A, Richardson D. Safety, Security, Now Sustainability: for the 21st Century. 2014.
7. Han B, Gopalakrishnan V, Ji L., Lee S. Network Functions Virtualization: Challenges and Opportunities for Innovations.
8. Zhi J, Garousi-yusifo V, Shahnewaz S, Ruhe G. The Journal of Systems and Software Cost, benefits and quality of software development
documentation: A systematic mapping. 99, 2015, 175-198.
9. Song BWL. SaaS-based enterprise application integration approach and case study. J Supercomput. (7), 2016, 2833-2847.
10. Kandl S, Chandrashekar S. Reasonability of MC/DC for safety-relevant software implemented in programming languages with short-circuit
evaluation. 16th IEEE IntSymp Object/Component/Service-Oriented Real-Time DistribComput ISORC 2013,2014, 261-279.
11. Karimi MB, Isazadeh A, Rahmani AM. QoS-aware service composition in cloud computing using data mining techniques and genetic
algorithm. J Supercomput, 73(4), 2016, 1-29.
12. Faschang M, Cejka S, Stefan M. Provisioning, deployment, and operation of smart grid applications on substation level. ComputSci - Res
Dev, 32(1), 2016, 1-14.
13. Mayer P, Kirsch M, Le MA. On Multi-Language Software Development, Cross-Language Links and Accompanying Tools: A Survey of
Professional Software Developers. Journal of Software Engineering Research and Development, 2017.
14. Yang CT, Shih WC, Huang CL, Jiang FC, Chu WCC. On construction of a distributed data storage system in cloud. Computing, 98(1-2),
2016, 93-118.
15. Jagroep E, Van Der Werf JM, Brinkkemper S, Blom L, Van Vliet R. Extending software architecture views with an energy consumption
perspective: A case study on resource consumption of enterprise software. Computing, 2016, 1-21.
16. Rodríguez RJ. Evolution and characterization of point-of-sale RAM scraping malware. J ComputVirol Hacking Tech, 2016, 1-14.
17. Weib A, Karastoyanova D. Enabling coupled multi-scale, multi-field experiments through choreographies of data-driven scientific
simulations. Computing, 98(4), 2016, 439-467.
18. Zhao J, Tao J, Streit A. Enabling collaborative MapReduce on the Cloud with a single-sign-on mechanism. Computing, 98(1-2), 2016, 55-72.
19. Chang S-H, Mao-Sheng H. A novel software-defined wireless network architecture to improve ship area network performance. 2016.
20. Ranjan R, Georgakopoulos D, Wang L. A note on software tools and technologies for delivering smart media-optimized big data applications
in the cloud. Computing, 98(1-2), 2016, 1-5.
21. Qi L, Dou W, Chen J. Weighted principal component analysis-based service selection method for multimedia services in cloud. Computing,
98(1-2), 2016, 195-214.
22. Kao CH. Testing and evaluation framework for virtualization technologies. Computing, 2016, 1-21.
23. Ihle N, Runge S, Meyer-Barlag C, Grundmeyer N, Appelrath HJ. Software components for demand side integration at a container terminal.
ComputSci - Res Dev, 31(1-2), 2016, 25-31.
8 M.A. Salleh,M. Bahari,N.H. Zakaria/ Procedia Computer Science 00 (2017) 000–000

24. Rochas C, Kuzņecova T, Romagnoli F. The concept of the system resilience within the infrastructure dimension: Application to a Latvian
case. J Clean Prod, 88, 2015, 358-368.
25. Kannisto P, Hästbacka D, Vilkko M, Kuikka S. Service Architecture and Interface Design for Mobile Machine Parameter Optimization
System. 15th IFAC SympInf Control Manuf, 2015.
26. Using information and mobile technology improved elderly home care services. Health Policy and Technology, 2016.
27. Herterich MM, Uebernickel F, Brenner W. The Impact of Cyber-physical Systems on Industrial Services in Manufacturing. Procedia CIRP,
30, 2015, 323-328.
28. Dogether M Al, Muallem Y Al, Househ M, Saddik B, Khalifa M. The impact of automating laboratory request forms on the quality of
healthcare services. J Infect Public Health, 9(6), 2016, 749-756.
29. Evangelidis K, Ntouros K, Makridis S, Papatheodorou C. Geospatial services in the Cloud. ComputGeosci, 63, 2014,116-122.
30. Evaluating single sign on security failure in cloud services. Business Horizons, 2016.
31. Jain M, Bhagat A, Shekhar C. Double orbit finite retrial queues with priority customers and service interruptions. Appl Math Comput, 253,
2015, 324-344.
32. Del Val E, Rebollo M, Botti V. Combination of self-organization mechanisms to enhance service discovery in open systems. InfSci (Ny), 279,
2014, 138-162.
33. Estrada A, Romero D. A System Quality Attributes Ontology for Product-Service Systems Functional Measurement Based on a Holistic
Approach. Procedia CIRP, 47, 2016, 78-83.
34. Hsu PF, Yen HR, Chung JC. Assessing ERP post-implementation success at the individual level: Revisiting the role of service quality.
InfManag, 52(8), 2015, 925-942.
35. Joore P, Brezet H. A Multilevel Design Model: The mutual relationship between product-service system development and societal change
processes. J Clean Prod, 97, 2015, 92-105.
36. A cyber resilient architecture for critical security services. Journal of Network and Computer Applications, 2016.
37. Rubbia G, Franco C, Pellizzon D, Nannipieri L. Research support services in Higher Education and Research Institutions: Approaches, tools
and trends. ProcediaComput Sci, 33, 2014, 309-314.
38. Klimov V. Peculiarities of Semantic Web-services Cloud Runtime. ProcediaComput Sci, 71(1), 2015, 208-214.
39. Prabhune A, Ansari H, Keshav A, Stotzka R, Gertz M. MetaStore: A Metadata Framework for Scientific Data Repositories. 2016, 3026-3035.
40. Stadler H, Großmann M, Krieger UR. Design of a Secure Mobile Business Communication Platform Utilizing Next Generation Web
Technologies. 2016, 257-263.
41. Paikan A, Domenichelli DE, Natale L. Communication channel prioritization in a publish-subscribe architecture. SoftwEngArchitRealt
Interact Syst Work Gr SEARIS 2015, 2015, 41-45.
42. Sousa G, Rudametkin W, Duchien L. Automated Setup of Multi-Cloud Environments for Microservices-Based Applications. 9th IEEE
IntConf Cloud Comput, 2016.
43. Belmokhtar O, Chiadmi D. A cloud services composition approach based on customer’s models and cloud services vendor’s rules and
specifications. 2017, 633-637.
44. Tseng F-H, Chang K-D, Liao S-C, Chao H-C, Leung VCM. sPing: a user-centred debugging mechanism for software defined networks. IET
Networks, 6(2), 2017, 39-46.
45. Sojeva B, Augustin S, Augustin S. Spatial-aware Iterative Integration of Crisis Management Information Systems. 2-4.
46. Aguado A, Hugues-Salas E, Haigh PA. First Experimental Demonstration of Secure NFV Orchestration over an SDN-Controlled Optical
Network with Time-Shared Quantum Key Distribution Resources. 35(8), 2016, 512-514.
47. Khabbaz M. Reliability-Aware Service Provisioning in NFV-enabled Enterprise Datacenter Networks. 2016, 153-159.
48. Richter A, Stocker A, Müller S, Avram G. Knowledge management goals revisited. Vine, 43(2), 2013, :132-148.
49. Moon YB, Phatak D. Enhancing ERP system’s functionality with discrete event simulation. IndManag Data Syst, 105(9), 2005, 1206-1224.
50. Ho C-T, Wei C-L. Effects of outsourced service providers’ experiences on perceived service quality. IndManag Data Syst, 116(8), 2016,
1656-1677.
51. Usener CA, Majchrzak TA, Kuchen H. E‐ assessment and software testing. Interact Technol Smart Educ, 9(1), 2012, 46-56.
52. Sahay BS, Gupta AK. Development of software selection criteria for supply chain solutions. IndManag Data Syst, 103, 2003, 97-110.
53. Leem CS, Yoon Y. A maturity model and an evaluation system of software customer satisfaction: The case of software companies in Korea.
IndManag Data Syst, 104(4), 2004, 347-354.
54. Norzaidi MD, Chong SC, Salwani MI, Lin B. The indirect effects of intranet functionalities on middle managers’ performance: Evidence
from the maritime industry. Kybernetes, 40(1-2), 2011, 166-181.
55. Zhang Q, Segall RS. Review of data, text and web mining software. Kybernetes, 39(4), 2010, 625-655.
56. Alfaries A, Bell D, Lycett M. Motivating service re-use with a web service ontology learning. Int J Web Inf Syst, 9(3), 2013, 219-241.
57. Elliott MS & Scacchi W. Mobilization of Software Developers: The Free Software Movement. 2008, 21.
58. Kitchenham, B., Brereton, O. P., Budgen, D., Turner, M., Bailey, J., Linkman, S. Systematic literature reviews in software engineering–a
systematic literature review.Information and software technology, 51(1), 2009, 7-15.
59. Ryan, G.W & Bernard, H. R. Techniques to Identify Themes. Field Methods, 15(1), 2003, 85–109.

View publication stats