The document presents a method called SaaSQuality for evaluating the quality of Software as a Service (SaaS) products. SaaSQuality includes a quality model based on ISO 9126, ITIL, and COBIT standards. The method was validated through a case study that showed it offers suitable practices for assessing SaaS quality. The document also reviews related work on SaaS quality evaluation and discusses the research methodology used to develop the SaaSQuality method.
An interactive approach to requirements prioritization using quality factorsijfcstjournal
As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...IRJET Journal
1) The document discusses conflicts that can arise during the software requirement engineering process. It focuses on conflicts between requirement analysts and stakeholders.
2) Some common causes of conflicts are misunderstandings, changing requirements, complex systems, and different interests among stakeholders. Conflicts can increase costs and lead to unsatisfactory software.
3) The author reviews literature on identifying and resolving conflicts. Various techniques are discussed like using tools, formal frameworks, and strategies to remove or prioritize conflicting requirements.
Service-oriented computing has created new requirements for information systems development processes
and methods. The adoption of service-oriented development requires service identification methods
matching the challenge in enterprises. A wide variety of service identification methods (SIM) have been
proposed, but less attention has been paid to the actual requirements of the methods. This paper provides
an ethnographical look at challenges in service identification based on data from 14 service identification
sessions, providing insight into the practice of service identification. The findings identified two types of
service identification sessions and the results can be used for selecting the appropriate SIM based on the
type of the session.
AN OVERVIEW OF EXISTING FRAMEWORKS FOR INTEGRATING FRAGMENTED INFORMATION SYS...ijistjournal
Literatures show that there are several structured integration frameworks which emerged with the aim of facilitating pplication integration. But weakness and strength of these frameworks are not known. This
paper aimed at reviewing these frameworks with the focus on identifying their weakness and strength. Toaccomplish this, recommended comparison factors were identified and used to compare these frameworks.Findings shows that most of these structure frameworks are custom based on their motives. They focus onintegrating applications from different sectors within an organization for the purpose of eliminating communication inefficiencies. There is no framework which guides pplication’s integrators on goals of integrations, outcomes of integration, outputs of integration and skills which will be required for
types of applications expected to be integrated. The study recommended further study on integration
framework especial on designing unstructured framework which will support and guide application’s
integrators with consideration on consumer’s surrounding environment.
Our study shows that users can even be very important a part of data system development in its varied
stages. supported a paper we have a tendency to gift our hypothesis that data provided by users by
information, past experiences and learning will cause higher project management. Establishing a relationship
between user and knowledge system will improve the look stage development of the project and as a result
higher project performance are often obtained.Project management data, system analysis skills, programming
data, information administration data square measure a number of the areas within which users will
contribute.In the development stage, users ought to participate within the review method to confirm that the
integrated data (system design) is meted out effectively by the developers. Users will facilitate to find or
expose inappropriate styles as early as doable to scale back supererogatory prices.This paper additionally
focuses on establishing understanding between users and developers.
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMSijseajournal
With the massive growth of the organizations files, the needs for archiving system become a must. A lot of
time is consumed in collecting requirements from the organization to build an archiving system. Sometimes
the system does not meet the organization needs. This paper proposes a domain-based requirement
engineering system that efficiently and effectively develops different archiving systems based on new
suggested technique that merges the two best used agile methodologies: extreme programming (XP) and
SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed
during analyzing and designing the archiving systems decreased significantly. The proposed methodology
also reduces the system errors that may happen at the early stages of the development of the system.
The document discusses the experience and qualifications of an individual for a technical specialist role supporting an enterprise learning management system. They have 10 years of experience in eLearning/IT roles, including managing applications and systems for over 10,000 staff and 40,000 students. They are ITIL certified and have extensive experience in application support, project management, and working with third-party vendors.
Jayamoorthy Arulmani is seeking a role as a Business Analyst. He has a Master's degree in Business Administration and a Bachelor's degree in Computer Application. He has over 5 years of experience in roles such as Business System Analyst, working on projects in the healthcare industry involving systems development, testing, and implementation. He is proficient in various technologies, methodologies, and processes related to business analysis and systems development.
An interactive approach to requirements prioritization using quality factorsijfcstjournal
As the prevalence of software increases, so does the complexity and the number of requirements assoc
iated
to the software project. This presents a dilemma for the developers to clearly identify and prioriti
ze the
most important requirements in order to del
iver the project in given amount of resources and time.
A
number of prioritization methods have been proposed which provide consistent results, but they are v
ery
difficult and complex to implement in practical scenarios as well as lack proper structure to
analyze the
requirements properly. In this study, the users can provide their requirements in two forms: text ba
sed
story form and use case form.
Moreover, the existing prioritization techniques have a very little or no
interaction with the users. So, in t
his paper an attempt has been made to make the prioritization process
user interactive by adding a second level of prioritization where after the developer has properly a
nalyzed
and ranked the requirements on the basis of quality attributes in the first le
vel, takes the opinion of distinct
user’s about the requirements priority sequence. The developer then calculates the disagreement valu
e
associated with each user sequence in order to find out the final priority sequence.
IRJET- Identifying the Conflicts in the Software Requirement Engineering:...IRJET Journal
1) The document discusses conflicts that can arise during the software requirement engineering process. It focuses on conflicts between requirement analysts and stakeholders.
2) Some common causes of conflicts are misunderstandings, changing requirements, complex systems, and different interests among stakeholders. Conflicts can increase costs and lead to unsatisfactory software.
3) The author reviews literature on identifying and resolving conflicts. Various techniques are discussed like using tools, formal frameworks, and strategies to remove or prioritize conflicting requirements.
Service-oriented computing has created new requirements for information systems development processes
and methods. The adoption of service-oriented development requires service identification methods
matching the challenge in enterprises. A wide variety of service identification methods (SIM) have been
proposed, but less attention has been paid to the actual requirements of the methods. This paper provides
an ethnographical look at challenges in service identification based on data from 14 service identification
sessions, providing insight into the practice of service identification. The findings identified two types of
service identification sessions and the results can be used for selecting the appropriate SIM based on the
type of the session.
AN OVERVIEW OF EXISTING FRAMEWORKS FOR INTEGRATING FRAGMENTED INFORMATION SYS...ijistjournal
Literatures show that there are several structured integration frameworks which emerged with the aim of facilitating pplication integration. But weakness and strength of these frameworks are not known. This
paper aimed at reviewing these frameworks with the focus on identifying their weakness and strength. Toaccomplish this, recommended comparison factors were identified and used to compare these frameworks.Findings shows that most of these structure frameworks are custom based on their motives. They focus onintegrating applications from different sectors within an organization for the purpose of eliminating communication inefficiencies. There is no framework which guides pplication’s integrators on goals of integrations, outcomes of integration, outputs of integration and skills which will be required for
types of applications expected to be integrated. The study recommended further study on integration
framework especial on designing unstructured framework which will support and guide application’s
integrators with consideration on consumer’s surrounding environment.
Our study shows that users can even be very important a part of data system development in its varied
stages. supported a paper we have a tendency to gift our hypothesis that data provided by users by
information, past experiences and learning will cause higher project management. Establishing a relationship
between user and knowledge system will improve the look stage development of the project and as a result
higher project performance are often obtained.Project management data, system analysis skills, programming
data, information administration data square measure a number of the areas within which users will
contribute.In the development stage, users ought to participate within the review method to confirm that the
integrated data (system design) is meted out effectively by the developers. Users will facilitate to find or
expose inappropriate styles as early as doable to scale back supererogatory prices.This paper additionally
focuses on establishing understanding between users and developers.
AN ITERATIVE HYBRID AGILE METHODOLOGY FOR DEVELOPING ARCHIVING SYSTEMSijseajournal
With the massive growth of the organizations files, the needs for archiving system become a must. A lot of
time is consumed in collecting requirements from the organization to build an archiving system. Sometimes
the system does not meet the organization needs. This paper proposes a domain-based requirement
engineering system that efficiently and effectively develops different archiving systems based on new
suggested technique that merges the two best used agile methodologies: extreme programming (XP) and
SCRUM. The technique is tested on a real case study. The results shows that the time and effort consumed
during analyzing and designing the archiving systems decreased significantly. The proposed methodology
also reduces the system errors that may happen at the early stages of the development of the system.
The document discusses the experience and qualifications of an individual for a technical specialist role supporting an enterprise learning management system. They have 10 years of experience in eLearning/IT roles, including managing applications and systems for over 10,000 staff and 40,000 students. They are ITIL certified and have extensive experience in application support, project management, and working with third-party vendors.
Jayamoorthy Arulmani is seeking a role as a Business Analyst. He has a Master's degree in Business Administration and a Bachelor's degree in Computer Application. He has over 5 years of experience in roles such as Business System Analyst, working on projects in the healthcare industry involving systems development, testing, and implementation. He is proficient in various technologies, methodologies, and processes related to business analysis and systems development.
Streamlining IT Application Selection and Integration with a Standard Modelin...Iver Band
IT customers, application providers, and system integrators generally do not use standard representations to describe
either application requirements or proposals to satisfy them. The resulting ambiguity exposes application selection and
integration processes, however well-structured and executed, to error and delay. Adoption of the ArchiMate® visual
modeling language, an Open Group standard, would therefore increase the efficiency and effectiveness of the business
application marketplace.
Software requirements prioritization is a
recognized practice in requirements engineering (RE)
that facilitates the management of stakeholders’
subjective views as specified in their requirements
listing. Since RE process is naturally collaborative in
nature, the intensiveness from both knowledge and
human perspectives opens up the problem of decision
making on requirements, which can be facilitated by
requirements prioritization. However, due to the large
volume of requirements elicited when considering an
ultra-large-scale system, existing prioritization
techniques proposed so far suffer some setbacks in
terms of efficiency, effectiveness and scalability. This
paper employed the use of a more efficient ranking
algorithm for requirements prioritization based on the
limitations of existing techniques. The major objective
is to provide a well-defined ranking procedure through
analysis, suitable for prioritizing software requirements.
An empirical evaluation of the proposed technique was
made using a typical scenario of the Pharmacy
Information System at the Obafemi Awolowo
University Teaching Hospital Complex (OAUTHC) as a
case study. The results showed the computation of the
positive ideal solution (PIS) and negative ideal solution
(NIS), as well as the closeness coefficient (CC) for 4
requirements across 3 stakeholders. The CC showed the
final ranks of requirements, where R4 with 2.09 point is
the most valued requirements, while R1 and R2 with
CC of 1.37 and 1.05 were next in the order of priority
respectively. The CC provides the medium through
which problems of multiple criteria decision making
can be handled, so as to determine the order of priority
of the available alternatives. The paper conveyed
encouraging evidence for the software engineering
community that is capable of resolving redundant
specified requirements, thereby providing the potential
that will facilitate effective and efficient decision
making in handling the differences amongst
requirements that have been prioritized. Thus,
prioritizing software requirements with the
recommended ranking procedure during software
development is crucial and vital in order to reduce
development cost.
Improving the Quality of Requirements in Middleware Requirements SpecificationsManigandan AJ
The document discusses improving the quality of requirements in middleware requirements specifications. It outlines several challenges to requirements elicitation for middleware projects, including a lack of transaction data storage, proprietary platform formats, and limited availability of stakeholders. The authors describe developing a structured methodology based on their experience to effectively elicit and document high-quality requirements. This includes defining the nature and content of interface requirements documents, best practices like different elicitation interventions, and future work automating aspects of requirements elicitation.
Identification, Analysis & Empirical Validation (IAV) of Object Oriented Desi...rahulmonikasharma
Metrics and Measure are closely inter-related to each other. Measure is defined as way of defining amount, dimension, capacity or size of some attribute of a product in quantitative manner while Metric is unit used for measuring attribute. Software quality is one of the major concerns that need to be addressed and measured. Object oriented (OO) systems require effective metrics to assess quality of software. The paper is designed to identify attributes and measures that can help in determining and affecting quality attributes. The paper conducts empirical study by taking public dataset KC1 from NASA project database. It is validated by applying statistical techniques like correlation analysis and regression analysis. After analysis of data, it is found that metrics SLOC, RFC, WMC and CBO are significant and treated as quality indicators while metrics DIT and NOC are not significant. The results produced from them throws significant impact on improving software quality.
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
ITERATIVE AND INCREMENTAL DEVELOPMENT ANALYSIS STUDY OF VOCATIONAL CAREER INF...ijseajournal
Software development process presents various types of models with their corresponding phases required to be accordingly followed in delivery of quality products and projects. Despite the various expertise and skills of systems analysts, designers, and programmers, systems failure is inevitable when a suitable development process model is not followed. This paper focuses on the Iterative and Incremental Development (IID)model and justified its role in the analysis and design software systems. The paper adopted the qualitative research approach that justified and harnessed the relevance of IID in the context of systems analysis and design using the Vocational
Career Information System (VCIS) as a case study. The paper viewed the IID as a change-driven software development process model. The results showed some system specification, functional specification of system and design specifications that can be used in implementing the VCIS using the IID model. Thus, the paper concluded that in systems analysis and design, it is imperative to consider a suitable development process that reflects the engineering mind-set, with heavy emphasis on good analysis and design for quality assurance.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
METRIC-BASED FRAMEWORK FOR TESTING & EVALUATION OF SERVICE-ORIENTED SYSTEMijseajournal
The increase in the significance of service orientation in system development is accelerating with an increase in demand for qualitative and cost-effective systems. Service-Oriented Architecture (SOA) is one of the established structural designs used for developing and implementing flexible, reusable, rapid and low-cost service-oriented systems. The established testing and evaluation methods don’t work well for systems that are made-up of services (service-oriented system). As a result, several testing and evaluation metrics for service-oriented systems were proposed. However, these metrics were created based on preceding software development approaches that offer insufficient focus to service-oriented systems thereby lacking the efficiency to evaluate these systems. Furthermore, Lack of access to source code also frustrates classical mutation-testing approaches, which require seeding the code with errors. This paper discusses different testing and evaluation metrics available for SOS and proposed a theory-grounded framework for testing and evaluation of service-oriented systems with the aim of decreasing cost and increasing the quality of the SOS. Then, the proposed framework is validated theoretically to check its usability and applicability for testing and evaluation of SOS. The results show that the proposed framework is able to decrease cost and increasing the quality of the SOS.
International Journal of Engineering Research and Applications (IJERA) aims to cover the latest outstanding developments in the field of all Engineering Technologies & science.
International Journal of Engineering Research and Applications (IJERA) is a team of researchers not publication services or private publications running the journals for monetary benefits, we are association of scientists and academia who focus only on supporting authors who want to publish their work. The articles published in our journal can be accessed online, all the articles will be archived for real time access.
Our journal system primarily aims to bring out the research talent and the works done by sciaentists, academia, engineers, practitioners, scholars, post graduate students of engineering and science. This journal aims to cover the scientific research in a broader sense and not publishing a niche area of research facilitating researchers from various verticals to publish their papers. It is also aimed to provide a platform for the researchers to publish in a shorter of time, enabling them to continue further All articles published are freely available to scientific researchers in the Government agencies,educators and the general public. We are taking serious efforts to promote our journal across the globe in various ways, we are sure that our journal will act as a scientific platform for all researchers to publish their works online.
An Elite Model for COTS Component Selection ProcessIJEACS
This document presents a multi-agent approach for selecting commercial off-the-shelf (COTS) software components. It proposes a semi-automated model called ABCS that uses multiple agents to identify suitable candidate components based on requirements. The agents each handle sub-tasks like matching requirements, evaluating security, cost-benefit analysis, and integration testing. They coordinate to produce a weighted list of candidates from which experts can select the most suitable component. The model aims to reduce the time and improve the knowledge involved in COTS component selection.
SIZE METRICS FOR SERVICE-ORIENTED ARCHITECTUREmathsjournal
Determining the size, effort and cost of Service-oriented Architecture (SOA) systems is important to
facilitate project planning and eventually successful implementation of a software project. SOA approach is
one of the recent software architectures that allow integration of applications within and outside the
organization regardless of heterogeneous technology over a distributed network. A number of research
studies have been done to measure SOA size.However, these studies are not based on software metrics
rendering them to be ineffective in their estimation. This study defined a set of SOA size metrics based on
Unified Modelling Language (UML). The study employed Briand’s theoretical validation to test the validity
of the designed SOA size metrics. Findings from this study will provide metrics to measure SOA size more
accurately and form a basis for future software engineering researchers to develop more effective and more
accurate size metrics and effort estimation methods.
Size Metrics for Service-Oriented Architecture ijseajournal
Determining the size, effort and cost of Service-oriented Architecture (SOA) systems is important to facilitate project planning and eventually successful implementation of a software project. SOA approach is one of the recent software architectures that allow integration of applications within and outside the organization regardless of heterogeneous technology over a distributed network. A number of research
studies have been done to measure SOA size.However, these studies are not based on software metrics rendering them to be ineffective in their estimation. This study defined a set of SOA size metrics based on Unified Modelling Language (UML). The study employed Briand’s theoretical validation to test the validity
of the designed SOA size metrics. Findings from this study will provide metrics to measure SOA size more accurately and form a basis for future software engineering researchers to develop more effective and more accurate size metrics and effort estimation methods.
EuroSPI O'Donnell Richardson Agile Methods in a Very Small CompanyMichael O'Donnell
This document discusses a case study of implementing agile methods at a small Irish software company called Sporting Software Ltd. The company tried implementing Extreme Programming (XP), an agile method, but ultimately declared it a failure. Some of the key problems encountered were lack of management support for agile methods and pre-existing employment contracts that did not align with agile values. The case study highlights that implementing agile methods can be challenging for small, remotely located companies.
Software Quality Engineering is a broad area that is concerned with various approaches to improve software quality. A quality model would prove successful when it suffices the requirements of the developers and the consumers. This research focuses on establishing semantics between the existing techniques related to the software quality engineering and thereby designing a framework for rating software quality.
Department of Homeland Security (DHS) Chief Information Officer (CIO) Luke McCormack recently
submitted testimony to a US Senate Subcommittee [1]. This case study, which is based on CIO
McCormack’s testimony, demonstrates how enterprise architects using the ArchiMate® language [2] can
quickly capture business situations using viewpoints defined in the ArchiMate specification. These
viewpoints are templates for views that address particular sets of stakeholder concerns. This case study
contains views based on and named after standard templates.
Analyzing the solutions of DEA through information visualization and data min...ertekg
Download Link > https://ertekprojects.com/gurdal-ertek-publications/blog/analyzing-the-solutions-of-dea-through-information-visualization-and-data-mining-techniques-smartdea-framework/
Data envelopment analysis (DEA) has proven to be a useful tool for assessing efficiency or productivity of organizations, which is of vital practical importance in managerial decision making. DEA provides a significant amount of information from which analysts and managers derive insights and guidelines to promote their existing performances. Regarding to this fact, effective and methodologic analysis and interpretation of DEA solutions are very critical. The main objective of this study is then to develop a general decision support system (DSS) framework to analyze the solutions of basic DEA models. The paper formally shows how the solutions of DEA models should be structured so that these solutions can be examined and interpreted by analysts through information visualization and data mining techniques effectively. An innovative and convenient DEA solver, SmartDEA, is designed and developed in accordance with the pro-posed analysis framework. The developed software provides a DEA solution which is consistent with the framework and is ready-to-analyze with data mining tools, through a table-based structure. The developed framework is tested and applied in a real world project for benchmarking the vendors of a leading Turkish automotive company. The results show the effectiveness and the efficacy of the proposed framework.
The document provides instructions for answering 31 essay questions related to business process change and information systems projects. Students are advised to write essay answers that are a few paragraphs long, fully address each part of the question, and demonstrate knowledge through examples and citations. The questions cover topics like reasons for outsourcing IT solutions, strengths of service-oriented architectures, analyzing business strategy and processes, and planning and managing information systems projects and changes.
MIDAS: A Design Quality Assessment Method for Industrial SoftwareGanesh Samarthyam
Siemens Corporate Development Center Asia Australia (CT DC AA) develops and maintains software applications for the Industry, Energy, Healthcare, and Infrastructure & Cities sectors of Siemens. The critical nature of these applications necessitates a high level of software design quality. A survey of software architects indicated a low level of satisfaction with existing design assessment practices in CT DC AA and highlighted several shortcomings of existing practices. To address this, we have developed a design assessment method called MIDAS (Method for Intensive Design ASsessments).
MIDAS is an expert-based method wherein manual assessment of
design quality by experts is directed by the systematic application
of design analysis tools through the use of a three view-model
consisting of design principles, project-specific constraints, and
an “ility”-based quality model. In this paper, we describe the
motivation for MIDAS, its design, and its application to three
projects in CT DC AA. We believe that the insights from our
MIDAS experience not only provide useful pointers to other
organizations and practitioners looking to assess and improve
software design quality but also suggest research questions for
the software engineering community to explore.
This document discusses SaaS readiness evaluation (SRE) services. SRE is a brief consulting engagement to help companies transition existing software to a software-as-a-service model. It evaluates technical requirements, business implications, and provides a roadmap. Key deliverables include a business case, financial projections, and functional prototype. SRE helps answer questions around competitive positioning, technology architecture, pricing, financial impact, and customer support in a SaaS model. Typical engagements last 2-3 weeks and cost $5,000-$20,000.
The document outlines the initial planning process for a vintage-themed project in Nottingham, England. It begins with mind mapping around interests in vintage clothes, shopping, and items. Wallpaper textures and floral patterns were an initial inspiration. Sketches and mood boards were created showing vintage photos, clothes, and fonts. Research looked at vintage colors, shopping trends, and competitors. The aim was to create a map and leaflet highlighting vintage shops in Nottingham, though a postcard idea was abandoned. Prototypes were made before determining the final outcome.
Streamlining IT Application Selection and Integration with a Standard Modelin...Iver Band
IT customers, application providers, and system integrators generally do not use standard representations to describe
either application requirements or proposals to satisfy them. The resulting ambiguity exposes application selection and
integration processes, however well-structured and executed, to error and delay. Adoption of the ArchiMate® visual
modeling language, an Open Group standard, would therefore increase the efficiency and effectiveness of the business
application marketplace.
Software requirements prioritization is a
recognized practice in requirements engineering (RE)
that facilitates the management of stakeholders’
subjective views as specified in their requirements
listing. Since RE process is naturally collaborative in
nature, the intensiveness from both knowledge and
human perspectives opens up the problem of decision
making on requirements, which can be facilitated by
requirements prioritization. However, due to the large
volume of requirements elicited when considering an
ultra-large-scale system, existing prioritization
techniques proposed so far suffer some setbacks in
terms of efficiency, effectiveness and scalability. This
paper employed the use of a more efficient ranking
algorithm for requirements prioritization based on the
limitations of existing techniques. The major objective
is to provide a well-defined ranking procedure through
analysis, suitable for prioritizing software requirements.
An empirical evaluation of the proposed technique was
made using a typical scenario of the Pharmacy
Information System at the Obafemi Awolowo
University Teaching Hospital Complex (OAUTHC) as a
case study. The results showed the computation of the
positive ideal solution (PIS) and negative ideal solution
(NIS), as well as the closeness coefficient (CC) for 4
requirements across 3 stakeholders. The CC showed the
final ranks of requirements, where R4 with 2.09 point is
the most valued requirements, while R1 and R2 with
CC of 1.37 and 1.05 were next in the order of priority
respectively. The CC provides the medium through
which problems of multiple criteria decision making
can be handled, so as to determine the order of priority
of the available alternatives. The paper conveyed
encouraging evidence for the software engineering
community that is capable of resolving redundant
specified requirements, thereby providing the potential
that will facilitate effective and efficient decision
making in handling the differences amongst
requirements that have been prioritized. Thus,
prioritizing software requirements with the
recommended ranking procedure during software
development is crucial and vital in order to reduce
development cost.
Improving the Quality of Requirements in Middleware Requirements SpecificationsManigandan AJ
The document discusses improving the quality of requirements in middleware requirements specifications. It outlines several challenges to requirements elicitation for middleware projects, including a lack of transaction data storage, proprietary platform formats, and limited availability of stakeholders. The authors describe developing a structured methodology based on their experience to effectively elicit and document high-quality requirements. This includes defining the nature and content of interface requirements documents, best practices like different elicitation interventions, and future work automating aspects of requirements elicitation.
Identification, Analysis & Empirical Validation (IAV) of Object Oriented Desi...rahulmonikasharma
Metrics and Measure are closely inter-related to each other. Measure is defined as way of defining amount, dimension, capacity or size of some attribute of a product in quantitative manner while Metric is unit used for measuring attribute. Software quality is one of the major concerns that need to be addressed and measured. Object oriented (OO) systems require effective metrics to assess quality of software. The paper is designed to identify attributes and measures that can help in determining and affecting quality attributes. The paper conducts empirical study by taking public dataset KC1 from NASA project database. It is validated by applying statistical techniques like correlation analysis and regression analysis. After analysis of data, it is found that metrics SLOC, RFC, WMC and CBO are significant and treated as quality indicators while metrics DIT and NOC are not significant. The results produced from them throws significant impact on improving software quality.
A methodology to evaluate object oriented software systems using change requi...ijseajournal
It is a well known fact that software maintenance plays a major role and finds importance in software
development life cycle. As object
-
oriented programming has become the standard, it is very important to
understand th
e problems of maintaining object
-
oriented software systems. This paper aims at evaluating
object
-
oriented software system through change requirement traceability
–
based impact analysis
methodology
for non functional requirements using functional requirem
ents
. The major issues have been
related to change impact algorithms and inheritance of functionality.
ITERATIVE AND INCREMENTAL DEVELOPMENT ANALYSIS STUDY OF VOCATIONAL CAREER INF...ijseajournal
Software development process presents various types of models with their corresponding phases required to be accordingly followed in delivery of quality products and projects. Despite the various expertise and skills of systems analysts, designers, and programmers, systems failure is inevitable when a suitable development process model is not followed. This paper focuses on the Iterative and Incremental Development (IID)model and justified its role in the analysis and design software systems. The paper adopted the qualitative research approach that justified and harnessed the relevance of IID in the context of systems analysis and design using the Vocational
Career Information System (VCIS) as a case study. The paper viewed the IID as a change-driven software development process model. The results showed some system specification, functional specification of system and design specifications that can be used in implementing the VCIS using the IID model. Thus, the paper concluded that in systems analysis and design, it is imperative to consider a suitable development process that reflects the engineering mind-set, with heavy emphasis on good analysis and design for quality assurance.
Performance Evaluation of Software Quality ModelEditor IJMTER
With the advent of Internet revolution and the emergence of knowledge based systems, Quality acquires a wider
and more challenging dimension. Quality has evolved and undergone transformation from the inspection era to
the quality control regime and then to quality management and finally to the present TQM approach. At every
stage of the transformation “Quality” has been attaining wider dimension with respect to Customer focus,
continual improvement and has been evolving for addressing increasing demands of customers with respect to
delivery of products and services.
METRIC-BASED FRAMEWORK FOR TESTING & EVALUATION OF SERVICE-ORIENTED SYSTEMijseajournal
The increase in the significance of service orientation in system development is accelerating with an increase in demand for qualitative and cost-effective systems. Service-Oriented Architecture (SOA) is one of the established structural designs used for developing and implementing flexible, reusable, rapid and low-cost service-oriented systems. The established testing and evaluation methods don’t work well for systems that are made-up of services (service-oriented system). As a result, several testing and evaluation metrics for service-oriented systems were proposed. However, these metrics were created based on preceding software development approaches that offer insufficient focus to service-oriented systems thereby lacking the efficiency to evaluate these systems. Furthermore, Lack of access to source code also frustrates classical mutation-testing approaches, which require seeding the code with errors. This paper discusses different testing and evaluation metrics available for SOS and proposed a theory-grounded framework for testing and evaluation of service-oriented systems with the aim of decreasing cost and increasing the quality of the SOS. Then, the proposed framework is validated theoretically to check its usability and applicability for testing and evaluation of SOS. The results show that the proposed framework is able to decrease cost and increasing the quality of the SOS.
International Journal of Engineering Research and Applications (IJERA) aims to cover the latest outstanding developments in the field of all Engineering Technologies & science.
International Journal of Engineering Research and Applications (IJERA) is a team of researchers not publication services or private publications running the journals for monetary benefits, we are association of scientists and academia who focus only on supporting authors who want to publish their work. The articles published in our journal can be accessed online, all the articles will be archived for real time access.
Our journal system primarily aims to bring out the research talent and the works done by sciaentists, academia, engineers, practitioners, scholars, post graduate students of engineering and science. This journal aims to cover the scientific research in a broader sense and not publishing a niche area of research facilitating researchers from various verticals to publish their papers. It is also aimed to provide a platform for the researchers to publish in a shorter of time, enabling them to continue further All articles published are freely available to scientific researchers in the Government agencies,educators and the general public. We are taking serious efforts to promote our journal across the globe in various ways, we are sure that our journal will act as a scientific platform for all researchers to publish their works online.
An Elite Model for COTS Component Selection ProcessIJEACS
This document presents a multi-agent approach for selecting commercial off-the-shelf (COTS) software components. It proposes a semi-automated model called ABCS that uses multiple agents to identify suitable candidate components based on requirements. The agents each handle sub-tasks like matching requirements, evaluating security, cost-benefit analysis, and integration testing. They coordinate to produce a weighted list of candidates from which experts can select the most suitable component. The model aims to reduce the time and improve the knowledge involved in COTS component selection.
SIZE METRICS FOR SERVICE-ORIENTED ARCHITECTUREmathsjournal
Determining the size, effort and cost of Service-oriented Architecture (SOA) systems is important to
facilitate project planning and eventually successful implementation of a software project. SOA approach is
one of the recent software architectures that allow integration of applications within and outside the
organization regardless of heterogeneous technology over a distributed network. A number of research
studies have been done to measure SOA size.However, these studies are not based on software metrics
rendering them to be ineffective in their estimation. This study defined a set of SOA size metrics based on
Unified Modelling Language (UML). The study employed Briand’s theoretical validation to test the validity
of the designed SOA size metrics. Findings from this study will provide metrics to measure SOA size more
accurately and form a basis for future software engineering researchers to develop more effective and more
accurate size metrics and effort estimation methods.
Size Metrics for Service-Oriented Architecture ijseajournal
Determining the size, effort and cost of Service-oriented Architecture (SOA) systems is important to facilitate project planning and eventually successful implementation of a software project. SOA approach is one of the recent software architectures that allow integration of applications within and outside the organization regardless of heterogeneous technology over a distributed network. A number of research
studies have been done to measure SOA size.However, these studies are not based on software metrics rendering them to be ineffective in their estimation. This study defined a set of SOA size metrics based on Unified Modelling Language (UML). The study employed Briand’s theoretical validation to test the validity
of the designed SOA size metrics. Findings from this study will provide metrics to measure SOA size more accurately and form a basis for future software engineering researchers to develop more effective and more accurate size metrics and effort estimation methods.
EuroSPI O'Donnell Richardson Agile Methods in a Very Small CompanyMichael O'Donnell
This document discusses a case study of implementing agile methods at a small Irish software company called Sporting Software Ltd. The company tried implementing Extreme Programming (XP), an agile method, but ultimately declared it a failure. Some of the key problems encountered were lack of management support for agile methods and pre-existing employment contracts that did not align with agile values. The case study highlights that implementing agile methods can be challenging for small, remotely located companies.
Software Quality Engineering is a broad area that is concerned with various approaches to improve software quality. A quality model would prove successful when it suffices the requirements of the developers and the consumers. This research focuses on establishing semantics between the existing techniques related to the software quality engineering and thereby designing a framework for rating software quality.
Department of Homeland Security (DHS) Chief Information Officer (CIO) Luke McCormack recently
submitted testimony to a US Senate Subcommittee [1]. This case study, which is based on CIO
McCormack’s testimony, demonstrates how enterprise architects using the ArchiMate® language [2] can
quickly capture business situations using viewpoints defined in the ArchiMate specification. These
viewpoints are templates for views that address particular sets of stakeholder concerns. This case study
contains views based on and named after standard templates.
Analyzing the solutions of DEA through information visualization and data min...ertekg
Download Link > https://ertekprojects.com/gurdal-ertek-publications/blog/analyzing-the-solutions-of-dea-through-information-visualization-and-data-mining-techniques-smartdea-framework/
Data envelopment analysis (DEA) has proven to be a useful tool for assessing efficiency or productivity of organizations, which is of vital practical importance in managerial decision making. DEA provides a significant amount of information from which analysts and managers derive insights and guidelines to promote their existing performances. Regarding to this fact, effective and methodologic analysis and interpretation of DEA solutions are very critical. The main objective of this study is then to develop a general decision support system (DSS) framework to analyze the solutions of basic DEA models. The paper formally shows how the solutions of DEA models should be structured so that these solutions can be examined and interpreted by analysts through information visualization and data mining techniques effectively. An innovative and convenient DEA solver, SmartDEA, is designed and developed in accordance with the pro-posed analysis framework. The developed software provides a DEA solution which is consistent with the framework and is ready-to-analyze with data mining tools, through a table-based structure. The developed framework is tested and applied in a real world project for benchmarking the vendors of a leading Turkish automotive company. The results show the effectiveness and the efficacy of the proposed framework.
The document provides instructions for answering 31 essay questions related to business process change and information systems projects. Students are advised to write essay answers that are a few paragraphs long, fully address each part of the question, and demonstrate knowledge through examples and citations. The questions cover topics like reasons for outsourcing IT solutions, strengths of service-oriented architectures, analyzing business strategy and processes, and planning and managing information systems projects and changes.
MIDAS: A Design Quality Assessment Method for Industrial SoftwareGanesh Samarthyam
Siemens Corporate Development Center Asia Australia (CT DC AA) develops and maintains software applications for the Industry, Energy, Healthcare, and Infrastructure & Cities sectors of Siemens. The critical nature of these applications necessitates a high level of software design quality. A survey of software architects indicated a low level of satisfaction with existing design assessment practices in CT DC AA and highlighted several shortcomings of existing practices. To address this, we have developed a design assessment method called MIDAS (Method for Intensive Design ASsessments).
MIDAS is an expert-based method wherein manual assessment of
design quality by experts is directed by the systematic application
of design analysis tools through the use of a three view-model
consisting of design principles, project-specific constraints, and
an “ility”-based quality model. In this paper, we describe the
motivation for MIDAS, its design, and its application to three
projects in CT DC AA. We believe that the insights from our
MIDAS experience not only provide useful pointers to other
organizations and practitioners looking to assess and improve
software design quality but also suggest research questions for
the software engineering community to explore.
This document discusses SaaS readiness evaluation (SRE) services. SRE is a brief consulting engagement to help companies transition existing software to a software-as-a-service model. It evaluates technical requirements, business implications, and provides a roadmap. Key deliverables include a business case, financial projections, and functional prototype. SRE helps answer questions around competitive positioning, technology architecture, pricing, financial impact, and customer support in a SaaS model. Typical engagements last 2-3 weeks and cost $5,000-$20,000.
The document outlines the initial planning process for a vintage-themed project in Nottingham, England. It begins with mind mapping around interests in vintage clothes, shopping, and items. Wallpaper textures and floral patterns were an initial inspiration. Sketches and mood boards were created showing vintage photos, clothes, and fonts. Research looked at vintage colors, shopping trends, and competitors. The aim was to create a map and leaflet highlighting vintage shops in Nottingham, though a postcard idea was abandoned. Prototypes were made before determining the final outcome.
Median Landscape in Indonesia
A 5-minute presentation material of Indonesian Contingent in Media and Information Discussion Group (DG-8) at the 41st Ship for Southeast Asian and Japanese Youth Programme (SSEAYP) 2014
Sumerian named as the rising saas star in capacity management globallySumerian
In February 2016, Independent research house Research in Action named Sumerian as the rising SaaS star in Capacity Management globally. Sumerian were ranked highest for customer satisfaction and price versus value across the industry and a the top vendor for Capacity Management strategy. Sumerian also ranked highest for customer satisfaction and price versus value across the capacity management and IT capacity planning industry.
Building A Web Observatory Extension: Schema.orggloriakt
The document discusses a presentation about extending the Schema.org vocabulary to facilitate web science collaboration through semantic markup. The presentation covers building a Web Observatory, the Schema.org vocabulary, and recommendations for extending the Schema.org vocabulary for a Web Observatory project. It also mentions that a team from Rensselaer Polytechnic Institute won first place in a developer challenge by using semantic technologies and software they developed.
http://inarocket.com
Learn BEM fundamentals as fast as possible. What is BEM (Block, element, modifier), BEM syntax, how it works with a real example, etc.
The document discusses how personalization and dynamic content are becoming increasingly important on websites. It notes that 52% of marketers see content personalization as critical and 75% of consumers like it when brands personalize their content. However, personalization can create issues for search engine optimization as dynamic URLs and content are more difficult for search engines to index than static pages. The document provides tips for SEOs to help address these personalization and SEO challenges, such as using static URLs when possible and submitting accurate sitemaps.
An Empirical Study of SQA Function Effectiveness in CMMI Certified Companies ...zillesubhan
The most vital component for any software development process is, “quality”, as it ensures the reliability and effectiveness of new software. Software Quality Assurance (SQA) techniques as well as a standardized qualitative metric known as Capability Maturity Model Integration (CMMI) are used to ensure this quality. The purposes of both the practices are same as both make efforts for end product’s quality. In spite of this, CMMI certified organizations have SQA function, but face a lot of issues, which resulted in lowering the quality of the products. Standards usually provide documentation, but SQA consider testing as a chief element and also documentation only for authentication and appraisals. The relationship of the SQA function with CMMI has not attended much in common literatures. This paper is centered on investigation conducted through data collection from diverse CMMI certified software development firm to check the practice of SQA function.
Nowadays the technological progress allows us to have highly flexible solutions, easily accessible with
lower levels of investment, which leads to many companies adopting SaaS (Software-as-a-Service) to
support their business processes. Associated with this movement and considering the advantages of SaaS, it
is important to understand whether work is being developed that is underutilized because companies are
not taking advantage of it, and in this case it is necessary to understand the reasons thereof. This
knowledge is important even for people who do not use or do not develop/provide SaaS, since sooner or
later it will be unavoidable due to current trends. In the near future, nearly all decision-makers of IT
strategies will be forced to consider adopting SaaS as an IT solution for the convenience benefits
associated with technology or market competition. At that time they will have to know how to evaluate
impacts and decide. What are the real needs in the Portuguese market? What fears and what is being done
to mitigate them? What are the implications of the adoption of SaaS? Where should we focus attention on
SaaS offerings in order to create greater value? These are questions we must answer to actually be able to
assess and decide. Often, decision-makers of business strategies consider only the attractive incentives of
using SaaS ignoring the impacts associated with new technologies. The need for tools and processes to
assess these impacts before adopting a SaaS solution is crucial to ensure the sustainability of the
information system, reduce uncertainty and facilitate decision making. This article presents a framework
for evaluating impacts of SaaS called SIE (SaaS Impact Evaluation) which in addition to guidance for the
present research, aims to provide guidelines for the collection, data analysis, impact assessment and
decision making about including SaaS on the organizations strategic plans.
Business and technical requirements of software as-a-service implications in ...ijfcstjournal
Software
-
as
-
a
-
Service (SaaS) is a viable option for some companies bearing their business processes.
There is a considerable adoption rate, with companies already using more than two services for over
two
years. However, while some companies have plans to put more bu
siness processes supported by these
services in the near future, others do not know if they will. They have several concerns regarding t
he
software providers’ service level. These concerns are
mainly technical and functional issues, service
availability an
d payment models.
There are major changes compared to the traditional software that have
implications on how the software is developed and made
available to the users. The existing research
addresses specific aspects and few studies give a broader view of the implications of SaaS for anyon
e who
develops and provides software, and also for those who consumes it as an end user. What are the real
n
eeds of the Portuguese market? What fears and what is being done to mitigate them? Where should we
focus our attention related to the SaaS offering in order to create more value? Thus, to analyze the
se
questions four exploratory case studiesare used to ass
ess the possible implications of SaaS on software
developers or software providers based in Portugal and also on end
-
users.
This article appears in the context of a realistic and deep research that includes the involvement o
f
managers, leaders and decisio
n makers of Portuguese companies, to realize what actually constitutes a
problem in SaaS and what effectively companies would like to have available in this offer. The resul
ts of
this study reveal that SaaS effectively constitutes a very interesting and so
lid solution for the development
of Portuguese companies, however there is a lack for greater efforts particularly in terms of custom
ization
for each customer (tenant) and integration with the back
-
end on
-
premise applications
STATISTICAL ANALYSIS OF METRICS FOR SOFTWARE QUALITY IMPROVEMENT ijseajournal
Software product quality can be defined as the features and characteristics of the product that meet the user needs. The quality of any software can be achieved by following a well defined software process. These software process results into various metrics like Project metrics, Product metrics and Process metrics. Software quality depends on the process which is carried out to design and develop software. Even though the process can be carried out with utmost care, still it can introduce some error and defects. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response
time.
This paper describes the importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature of error captured. To reduce such errors and defects found, steps for corrective actions are recommended.
IT PROJECT SHOWSTOPPER FRAMEWORK: THE VIEW OF PRACTITIONERSijseajournal
This document summarizes a study that investigated factors affecting requirements adherence to business processes in agile projects. The study conducted a cross-case analysis of seven companies, collecting data through interviews, observations, and document analysis. The analysis identified that customer business knowledge by the development team and customer availability during requirements elicitation and validation are essential for requirements to align with business needs in agile projects. This allows developed systems to better meet the needs of an organization's business processes.
AN IMPROVED REPOSITORY STRUCTURE TO IDENTIFY, SELECT AND INTEGRATE COMPONENTS...ijseajournal
An ultimate goal of software development is to build high quality products. The customers of software
industry always demand for high-quality products quickly and cost effectively. The component-based
development (CBD) is the most suitable methodology for the software companies to meet the demands of
target market. To opt CBD, the software development teams have to customize generic components that are
available in the market and it is very difficult for the development teams to choose the suitable components
from the millions of third party and commercial off the shelf (COTS) components. On the other hand, the
development of in-house repository is tedious and time consuming. In this paper, we propose an easy and
understandable repository structure to provide helpful information about stored components like how to
identify, select, retrieve and integrate components. The proposed repository will also provide previous
assessments of developers and end-users about the selected component. The proposed repository will help
the software companies by reducing the customization effort, improving the quality of developed software
and preventing integrating unfamiliar components.
LEAN LEVEL OF AN ORGANIZATION ASSESSED BASED ON FUZZY LOGIC csandit
To determine the lean level of an organization a methodology was developed. It was based on a
qualitative assessment approach, including quantitative basis, whose development was
supported using fuzzy logic. Recourse to the use of fuzzy logic is justified by its ability to cope
with uncertainty and imprecision on the input data, as well as, could be applied to the analysis
of qualitative variables of a system, turning them into quantitative values. A major advantage of
the developed approach is that it can be adjusted to any organization regardless of their nature,
size, strategy and market positioning. Furthermore, the proposed methodology allows the
systematically identification of constraint factors existing in an organization and, thus, provide
the necessary information to the manager to develop a holistic plan for continuous
improvement. To assess the robustness of the proposed approach, the methodology was applied
to a maintenance and manufacturing aeronautical organization.
Software quality model based on development team characteristicsIJECEIAES
Many factors have a significant impact on producing high-quality software products. Development team members are among the most important factors. Paying attention to the quality from this perspective will be a good innovation in the software development industry. Given that team members play a very important role in software products, this study tries to focus specifically on team characteristics in software product quality and provide a qualitative model based on this. The required data were collected through observations and interviews with project managers and development team members in several companies under study. Then, data were analyzed through hierarchical analysis. According to the results, the use of this model led to the improvement of the software development process so that the team members were satisfied with it. Also, time management was improved, and the customer expressed his satisfaction with the use of this model. Finally, data analysis showed that this model may lead to faster product delivery.
FROM THE ART OF SOFTWARE TESTING TO TEST-AS-A-SERVICE IN CLOUD COMPUTINGijseajournal
Researchers consider that the first edition of the book "The Art of Software Testing" by Myers (1979)
initiated research in Software Testing. Since then, software testing has gone through evolutions that have
driven standards and tools. This evolution has accompanied the complexity and variety of software
deployment platforms. The migration to the cloud allowed benefits such as scalability, agility, and better
return on investment. Cloud computing requires more significant involvement in software testing to ensure
that services work as expected. In addition to testing cloud applications, cloud computing has paved the
way for testing in the Test-as-a-Service model. This review aims to understand software testing in the
context of cloud computing. Based on the knowledge explained here, we sought to linearize the evolution of
software testing, characterizing fundamental points and allowing us to compose a synthesis of the body of
knowledge in software testing, expanded by the cloud computing paradigm.
From the Art of Software Testing to Test-as-a-Service in Cloud Computingijseajournal
Researchers consider that the first edition of the book "The Art of Software Testing" by Myers (1979)
initiated research in Software Testing. Since then, software testing has gone through evolutions that have
driven standards and tools. This evolution has accompanied the complexity and variety of software
deployment platforms. The migration to the cloud allowed benefits such as scalability, agility, and better
return on investment. Cloud computing requires more significant involvement in software testing to ensure
that services work as expected. In addition to testing cloud applications, cloud computing has paved the
way for testing in the Test-as-a-Service model. This review aims to understand software testing in the
context of cloud computing. Based on the knowledge explained here, we sought to linearize the evolution of
software testing, characterizing fundamental points and allowing us to compose a synthesis of the body of
knowledge in software testing, expanded by the cloud computing paradigm.
Effectiveness of software product metrics for mobile application tanveer ahmad
This document discusses the effectiveness of software product metrics for mobile applications. It defines effectiveness and explores how metrics can be used to measure the quality, performance, and efficacy of mobile apps. The document reviews literature on software metrics and their importance. It also examines different types of product metrics like size, complexity, and defect metrics. Finally, it proposes using a statistical simulation approach and developing a new measurement tool called the Effectiveness Calculation Model for Mobile Applications to quantify mobile app performance using computational mathematics.
Agile Customer Engagement A Longitudinal Qualitative Case StudyJackie Taylor
This document presents a longitudinal case study of a small software product company that transitioned from a waterfall development process to an agile process called Evolutionary Project Management (Evo). The study followed the company over two years and four product releases. It investigated the practicalities, costs, gains, and prerequisites of implementing close customer engagement as the prominent feature of the new Evo process. Through interviews with customers, product management, and developers, the findings indicate that close customer engagement can provide benefits but also comes with costs and requires disciplined management.
Software testing is a key part of software engineering used to evaluate software quality and identify errors. There are various software testing techniques and methods, but thoroughly investigating a complex software is more important than following a specific procedure. Testing complex software cannot discover all errors, but can help improve quality. Software engineering involves defining requirements, design, development, testing, and maintenance of software using methodologies like agile development.
MAKE THE QUALITY OF SOFTWARE PRODUCT IN THE VIEW OF POOR PRACTICES BY USING S...Journal For Research
In the Software Engineering, One of the most important factors to impact national and international business is quality of software and its assurance. Integral part of software development cycle is SQA, evaluation of software Quality product when compared to other industrial projects and it is very highly difficult. For developing, performance, speed, maintaining the quality, cost and efficiency of the software, SQA activities, principles and its methods are implemented in the early stages of the software engineering development phases. Where in this paper there is little visibility of lack of software Quality product in the view of poor practices. Hence we proposed a new system with best practices in software quality management to make the best quality product. This System works on Gain Better Visibility into Supplier Quality with Technology.
DESQA a Software Quality Assurance FrameworkIJERA Editor
In current software development lifecycles of heterogeneous environments, the pitfalls businesses have to face are that software defect tracking, measurements and quality assurance do not start early enough in the development process. In fact the cost of fixing a defect in a production environment is much higher than in the initial phases of the Software Development Life Cycle (SDLC) which is particularly true for Service Oriented Architecture (SOA). Thus the aim of this study is to develop a new framework for defect tracking and detection and quality estimation for early stages particularly for the design stage of the SDLC. Part of the objectives of this work is to conceptualize, borrow and customize from known frameworks, such as object-oriented programming to build a solid framework using automated rule based intelligent mechanisms to detect and classify defects in software design of SOA. The implementation part demonstrated how the framework can predict the quality level of the designed software. The results showed a good level of quality estimation can be achieved based on the number of design attributes, the number of quality attributes and the number of SOA Design Defects. Assessment shows that metrics provide guidelines to indicate the progress that a software system has made and the quality of design. Using these guidelines, we can develop more usable and maintainable software systems to fulfill the demand of efficient systems for software applications. Another valuable result coming from this study is that developers are trying to keep backwards compatibility when they introduce new functionality. Sometimes, in the same newly-introduced elements developers perform necessary breaking changes in future versions. In that way they give time to their clients to adapt their systems. This is a very valuable practice for the developers because they have more time to assess the quality of their software before releasing it. Other improvements in this research include investigation of other design attributes and SOA Design Defects which can be computed in extending the tests we performed.
This document proposes a method for identifying candidate services from business process models in a service-oriented architecture (SOA) approach. The method involves two main phases: 1) identifying and classifying candidate services based on heuristics applied to business process activities, and 2) consolidating candidate services based on existing business requirements. The heuristics examine both the structural and semantic elements of process models. The overall goal is to provide systematic guidance to service designers in mapping business processes to appropriate software services. The method was applied successfully in a case study with a large Brazilian oil company.
Business Talk: Harnessing Generative AI with Data Analytics MaturityIJCI JOURNAL
Generative AI applications offer transformative potential for business operations, yet their adoption introduces substantial challenges. This paper utilizes the CBDAS data maturity model to pinpoint pivotal success factors for seamless generative AI integration in businesses. Through a comprehensive analysis of these factors, we underscore the essentials of generative AI deployment: cohesive architecture, robust data governance, and a data-centric corporate ethos. The study also highlights the hurdles and facilitators influencing its implementation. Key findings suggest that fostering a data-friendly culture, combined with structured governance, optimizes generative AI adoption. The paper culminates in presenting the practical implications of these insights, urging further exploration into the real-world efficacy of the proposed recommendations.
The document presents a changeability evaluation model for object-oriented software. It begins with an introduction to changeability and its importance. It then reviews existing literature on measuring changeability. A relationship is established between changeability and object-oriented design properties like coupling, inheritance, and polymorphism. The paper then develops a changeability evaluation model using multiple linear regression. The model relates changeability as the dependent variable to design properties as independent variables. The model is validated using experimental tests on data from class diagrams, which show the model is highly significant.
The document presents a changeability evaluation model for object-oriented software. It begins with an introduction to changeability and its importance. It then reviews existing literature on measuring changeability. A relationship is established between changeability and object-oriented design properties like coupling, inheritance, and polymorphism. The paper then develops a changeability evaluation model using multiple linear regression. The model relates changeability as the dependent variable to object-oriented design metrics as independent variables. The model is validated experimentally using data from class diagrams, showing it is highly significant.
The document is the 2016-17 Turkey Software Quality Report published by the Turkish Testing Board. It focuses on test data management. The report aims to help organizations shift their mindsets and set standards for future IT projects in Turkey. It provides a survey of test data practices in Turkish organizations. The survey found that most test data is currently generated manually by testers, but automation is expected to increase. It also found that a significant amount (30% on average) of testing effort is spent on test data management. The top challenges in test data management are having up-to-date and consistent data that resembles real data.
Similar to Saasquality - A Method For Quality Evaluation Of Software As A Service (Saas) (20)
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
Demystifying Knowledge Management through Storytelling
Saasquality - A Method For Quality Evaluation Of Software As A Service (Saas)
1. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
DOI : 10.5121/ijcsit.2013.5308 101
SAASQUALITY - A METHOD FOR QUALITY
EVALUATION OF SOFTWARE AS A SERVICE (SAAS)
Nemésio Freitas Duarte Filho1
, Clarindo Isaias Pereira da Silva e Pádua1
, Paulo
Henrique de Souza Bermejo2
, Andre Luiz Zambalde2
, Urlan Salgado de Barros3
1
Institute of Mathematical Sciences/Federal University of Minas Gerais
nemesiofreitas@gmail.com, clarindo@dcc.ufmg.br
2
Department of Computer Science/Federal University of Lavras.
bermejo@dcc.ufla.br, zamba@dcc.ufla.br
3
Department of Information/Federal University of Paraná.
urlancomp@gmail.com
ABSTRACT
The market for software products offered as a service (SaaS) is growing steadily and has attracted
suppliers from different segments of the global IT market. However, the use of the SaaS products brings a
range of challenges, both in the organizational, cultural and technological areas. A difficulty that exists
today is the lack of methods and models for assessing the quality of these products. This document presents
a method to assess the quality of a software product offered as a service, named SaaSQuality. The
proposed method has a quality model appropriate to the SaaS context, based on standards and models of
software quality (ISO 9126) and models for IT management (ITIL and COBIT). The experimental results
obtained through a case study show that the method offers suitable assessment practices for Software as a
Service.
KEYWORDS
Software Quality. Software as a Service. Quality Management Services. Methods of Evaluation. Models for
IT Management.
1. INTRODUCTION
Software quality has the objective to ensure conformity with software requirements. It means that
a software product needs to attend to both explicit and implicit specifications, which this product
is offered as a package or a service (SaaS - Software as a Service). Therefore, the final goal is
ensure a product that satisfies all client's expectations [1].
Software development companies are worried about the quality excellence of their products, due
to growth of organizations exigency. Nowadays, software product is a critical tool, and its quality
requirements become key criteria’s in software acquisition [2, 3]. It reflects directly on the
mission and objectives of organizations business.
In this context, Software as a Service has been gaining popularity in organizations. The success of
those products depends on functional and non-functional requirements [4]. These attributes help
define the quality in a software product. However, the difficulty to establish and use quality
criteria is linked with the complication on associate measurable requirements of physical products
for software product [5].
2. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
102
SaaS is a new paradigm based on software delivery, which client organizations pay not for the
ownership, but for the use of software. Therefore, software companies have to maintain and to
evolve software, and they also need to assist problems related to technical support. Due to
market's concurrence, many software companies are already applying this new paradigm.
However, those companies have troubles mainly in ensure the quality of their final products,
considering that SaaS is a new and incipient paradigm [6].
Only a few works approach definitions and impacts of quality attributes related to Software as
Service product. In consequence, there's no evidence in scientific research about methods, models
and metrics which provide a practical and efficient assessment of quality in SaaS products.
Many assessment methods of quality in software products are ineffective in relation to paradigm
SaaS, mainly to not provide a correct set of quality attributes. An efficient attribute set may
possess features and sub-features showing its scope and applicability. Moreover, it needs to show
its positive and negative impacts in front of applications [6, 7].
2. RELATED WORK
Dubey & Wagle [8] show the main problems and concerns encountered on SaaS systems which
have been found by organizations. Many of those problems can directly affect the quality of
products and impact on other factors, such as functional and commercial aspects, conformity, and
so on. Even analyzing the main concerns about this new paradigm, Dubey & Wagle [8] do not
present metrics and criteria’s to auxiliary and to contribute in a practical evaluation of those
problems. However, the analysis made in Dubey & Wagle [8] with the definition of main
problems contributes to this work, mainly in elaboration of a specific quality model to SaaS.
Another work linked to quality of SaaS systems is O’Brien et al. [9]. In that work, the authors
make an analysis between a service oriented architecture (SOA) and quality of software
attributes. That work is motivated by software architecture, due to SOA be an important factor in
business compliance of organizations and computational systems. Furthermore, one of the
objectives of O’Brien et al. [9] is to examine how a SOA supports quality attributes, such as
availability, security, confiability, portability and interface, analyzing questions and problems
related to them. The authors do not approach the creation of a method or model that could turn
possible the practical application of these quality attributes. However, they identify features
linked to software products and TI services, integrating perfectly to SaaS paradigm.
Following the same reasoning of previously researches, in Havelka et al. [10] is proposed an
empirical study involving users of IT area. The aim of this study is to identify critical factors
which can cause impact on both positive and negative manner on SaaS. The factors identified by
the users were integrated in a questionnaire instrument to raise up evidences about the true impact
of aspects approached. The study also identified others impelling factors, however, without
relevance guarantee due to the research has been made considering only the user's opinion and
knowledge.
Jureta et al. [11] follows the same reasoning of previously researches, but enters in aspects linked
on a method that helps the quantification of quality in SaaS systems. In that work, the authors
perform analysis on ISO 9126 and ISO 20000, proposing a new quality method entitled QVDP
(Quality-Value-Dependency-Priority). The Research takes in consideration that SaaS products
have different perspectives in relation to the conventional software's quality. For example,
features of portability, support, personalization, and so on.
In the work by Cancian [12] was proposed a development process of SaaS systems. Development
process is one of the main factors that can cause impact directly on final quality of those systems.
Based on a few requirements of quality, Cancian [12] proposes a reference guide to evaluate
3. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
103
development process of SaaS system. Furthermore, the author also performed a synthesis and
analyze of requirements, mapping them in relation to standards and models of reference existed in
literature. The research made by Cancian [12] has neither a practical application nor a real case
study, but it shows a fundamental complete guide in reference to process evaluation of
development in SaaS systems.
Cancian et al. [13] proposes a generic structure of SLA (Service Level Agreement) which defines
quality items more adequate to SaaS. The author observed the necessity of a clear understandment
associated to appointments firmed between a supplier and a client of SaaS solutions. Beyond the
generic structure, Cancian et al. [13] also identifies important quality requirements that must be
observed on SaaS model, mainly in SLAs. SLAs are important to guarantee the quality due to
have a higher security on a service agreement.
In The work of Rosenberg et al. [14], it was found that the development of products SaaS is a
difficult task and that is prone to errors, is difficult even ensure a good quality in its final product.
For this reason it has been proposed in the work an automated composition of services called
CaaS (Composition as a Service), in which facilitates the rapid development in small applications
geared to services, guaranteeing greater efficiency during the development and greater internal
quality of the software, generating an standardization in its architecture and in its source code.
In another context, linked with the quality of services of IT, Silva et al. [15] drawn up a proposal
in order to analyze the administration of the services Information technology (IT) in companies
where the strategic function it is vital for the competitiveness of business.
Miguel & Salomi [16] in their research, showed a review in the literature on the main models and
concepts that are proposed for the measurement of the quality of external services. The review
has had an analytical basis, thematic, historical and bibliographic. After making presentations of
the models more efficient and used, a comparison between them has been carried out by showing
its main features.
According to results, Miguel & Salomi [16] concluded that do not exist a consensus in literature
about which model is more appropriated to measure the quality of IT service. Furthermore, there
are question even not answered, such as, the causality relation between quality of IT services and
customers satisfaction.
The Table 1 shows a summary of related work, identifying the relationship with quality aspects in
relation to paradigm SaaS, for example, Method Evaluation; Quality Model; Evaluation Process;
Requirements Analysis; and Systematic Review.
Table 1. Summary of related work
Related Work Method
Evaluation
Quality
Model
Evaluation
Process
Requirements
Analysis
Systematic
Review
Dubey & Wagle
[8]
x
O’Brien et al.
[9]
x x x
Havelka et al.
[10]
x x
Jureta et al. [11] x x x
Cancian [12] x x
Cancian et al.
[13]
x x
Rosenberg et al.
[14]
x x x
4. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
104
Silva et al. [15] x x x
Miguel &
Salomi [16]
x x
3. RESEARCH METHODOLOGY
This research is classified as qualitative and technology nature, focusing on objective exploratory,
using case study procedures and basing your materials and methods on documental and
bibliography researches [17, 18]. The methodology process followed by this work possesses four
phases.
1-Conception and preparation of research: The first phase includes the conception and initial
aspects to realization of research. The problem's definition takes in consideration necessities of
research environment, verifying if efforts are valid and relevant in relation to the lack of a
practical and efficient method which assesses the quality of a SaaS product.
2-Preliminar results and analyses: In this phase, are realized analyses and studies relative to
characteristics and quality requisites turned to paradigm SaaS, enabling the construction of a
specific quality model to SaaS. The first phase was carried out the analysis of requirements in
relation to the quality of software, covering studies of norms and standards of quality, providing
analysis of quality criteria had been expected in a product of conventional software. This analysis
made possible to identify which characteristics have applicability and purpose within systems
SaaS.
At the same time has been carried out an analysis of requirements in relation to the quality of IT
services. Frameworks and guides to good practice of management of service for IT where used
with purpose to raise and analyze at quality criteria which can be found also in Software as a
Service, remembering that SaaS have similar characteristics of a conventional system and IT
services [4].
After the analysis, it was carried out a survey of quality requirements to the context SaaS, having
as objective raise and integrate in a single set criteria and requirements of quality for a product
SaaS, enabling their use in a method of evaluation. The integration was made using comparisons
and definitions of applicability on the basis of the standard ISO/IEC 9126 [19], ITIL v3 [20] and
COBIT 4.1 [21], in order to identify the characteristics of quality more relevant to the context
SaaS. After the identification and integration of the criteria, there has been a complementation
and prioritization of these characteristics, by means of a search of 85 people related to the SaaS
paradigm (entrepreneurs, experts and researchers), offering greater complementation and
reliability the characteristics that have been raised.
3-Validation and improvements in the method: This stage makes reference to the beginning of the
study of the case, where it has for objective the validation of the method proposed, together with
the model of quality. Still at this stage a process of evaluation has been defined, and also a stage
of continued improvement for the SaaSQuality. After the definition of the characteristics of
quality to be used by the SaaSQuality, there was the need to mapping all the characteristics in
attributes measurable, enabling its measurement and scoring. This mapping has enabled the
preparation on a list of verification (checklist), enabling a practical assessment of the quality
requirements.
For the practical application of the method, there was the need to set up an evaluation process that
can be repeatable, reproducible, impartial and objective. The process of evaluation of the
SaaSQuality was based on the standard ISO/IEC 14598 [22], but some changes and adjustments
5. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
105
have been made order to better match to the products SaaS, together with the roles played by the
actors in the process.
On end of this phase has been carried out the validation and improvements in SaaSQuality by
means of a study of the case. The study of the case is important, because it shows in a real
environment the objective achieved, limitations and possible improvements, seeking validate the
work performed. For the conduct of the study of the case, were performed evaluations on the
product "SalesForce CRM Sales" on the basis of guidelines e metric of the SaaSQuality method.
4-Checks and Final Results: at this stage results have been achieved by means of a comparison,
together with checks on the partial results obtained and published in the scientific community
[23], specifically in the area of "Quality of Software". The method SaaSQuality was submitted to
a comparison with a method of evaluation the quality conventional, in the case the MEDE-Pros,
to complement its validation. This comparison showed several points which are not discussed or
assessed by conventional methods, together with some limitations.
4. QUALITY MODEL FOR SAASQUALITY
In accordance with the authors [10, 11, 24, 25], so that the application of a method of evaluation
will be efficient it is necessary that he it is based or contains a model of quality specific to the
context of their applications.
The authors of this work neither found in the literature nor in the international standards, models
of quality that envisage properly the characteristics of quality in a system SaaS. In the face of this
particular characteristic was necessary the proposal and definition of a model which contemplate
criteria and quality requirements specific to the SaaS.
The model is proposed based on various characteristics of the ISO 9126 standard along with the
ITIL v3 and the framework COBIT 4.1, offering characteristics relating to a product of
conventional software and a service of IT. The standard ISO 9126 has provided to the set well-
defined characteristics of a software product, stating aspects of functionality, reliability, usability,
efficiency, maintainability and portability. For its part, the ITIL v3 and the COBIT 4.1 were
important elements for the identification of characteristics turned to the improvement of the
management and quality of services for TI, in order to provide greater quality, particularly in
relation to legal issues, performance and security in a SaaS product.
In addition of the support of those methodologies, the authors also were based on other work [8,
9, 10], containing the vision of different authors, all in relation to the quality of SaaS systems. In
order to give greater support and justification to this model, because of the lack of practical
application, there was the need to give priority and complement the characteristics that have been
raised.
The support were been done by means of a search online with various expert in the area, having
as participants, managers, consultants, all of the area of SaaS. The search online was based on the
sending of a checklist for the experts, where they have were able to analyze and indicate the
relevance of each requirement raised. The relevance of the requirements of quality has indicated
which characteristics are really important based on the knowledge and practical experience of the
specialists. The relevance could be defined based on some criteria of trial [26]:
• Very Relevant: important features and of extreme importance to guarantee of their
quality, interfering directly in quality internal and external of the SaaS products;
6. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
106
• Relevant: important features mainly in to external quality of the system, impacting the
final quality of the product;
• Little Relevant: characteristics desirable, but not essential for the success and operation of
the application;
• Not applicable: characteristics that do not apply to the context SaaS. There are aspects of
quality that are applicable and measurable in conventional software’s, but not in the
context SaaS, such as for example installation.
To help in the implementation and maintenance of the model proposed, while facilitating their
understanding, has been defined a hierarchical structure in relation to the characteristics that have
been raised. The hierarchical structure defined in this work resembles the proposed structure in
the work of Hoffman et al. [27], in order to facilitate the verification of quality requirements that
must be observed in the construction of a SaaS product. For the current work have been used
three levels of hierarchy, each having a specific purpose. The three levels of this structure are
submitted to follow:
• Level 1 - Criteria for Evaluation: Have been defined criteria to be observed during the
evaluation of the quality in a SaaS system;
• Level 2 - Requirements (Guidelines): Formed by requirements of quality, representing
guidelines specific for each criterion defined in the first level;
• Level 3 - Attributes of Verification: The third level is formed by the attributes of
verification, in other words, measurable attributes that can be measured and punctuated.
In this way, the graphical representation of the model of quality proposed for the method
"SaasQuality" was determined in accordance with the Figure 1.
Figure 1 - Set of criteria and quality requirements specific to SaaS.
The following is presented with a summary of the main impact that the proposed requirements
present in relation to SaaS systems.
Functionality: Through the use of architectures and technologies, a system SaaS provides a high-
interoperability between systems, together with an efficient adequacy of their functions.
7. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
107
Usability: The good quality in usability of a system can reduce the services within the support of
the organization, thus allowing a good human interaction with the system, while avoiding
problems of performance with the services.
Security: The need for cryptography, integrity and confidence in a SaaS approach requires
attention detailed in its architecture. Many standards of the architecture SOA are being developed
to give support to the safety, but the majorities are still immature [28].
Performance: a SaaS approach may have a negative impact on the performance of an application
due to delays in the network and the burden of users in the same system. The contracting
organization must design and assess the quantity of users that they will use the system. The
supplier must design and carefully to assess their services by making sure that the performance
requirements needed will be met.
Support: The ability to support in SaaS systems can provide a negative effect on the contracting
company and provider. The testability can be affected negatively when using a large number of
outsourced services.
Service Level: the contracting parties of SaaS systems can negotiate a SLA with his supplier, by
providing agreements of levels of availability and sanctions for non-compliance of the agreement.
The auditability can be negatively affected if the skills necessary to audit are not incorporated into
the system.
Portability: the use of an approach SaaS must have a positive impact on the adaptability and
portability when the adaptations are managed in an appropriate way, observing that the greater
concern is associated with the portability of web browsers, not to operational systems.
5. PRESENTATION OF SAASQUALITY
The SaaSQuality was proposed and modelled following the logic of other evaluation methods
[29, 30, 31]. All referenced work follow a generic structure, generally relying on a specific model
of quality, along with a well-structured evaluation process. Figure 2 shows the overview of
SaaSQuality.
Figure 2 - Overview of SaaSQuality.
8. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
108
For the subjectivity of the evaluation is minimal, ensuring greater efficiency, the process of
SaaSQuality was developed following certain characteristics [4]:
• Repeatable: the process should enable the method to be applied several times in different
instances and still have results that can be accepted as identical or similar;
• Reproducible: the process should contain specifications and steps, allowing the method to
be applied by different evaluators (different entities) providing acceptable results to the
context of evaluation;
• Impartial: the process should avoid that the results are influenced by internal or external
factors in relation practical evaluation;
• Objective: the process should ensure clear results, avoiding ambiguities and different
interpretations.
In the context of the current work, the actors represent roles that a human being plays in relation
to the activities of the evaluation process. Basically there are four actors who participate in this
process:
• Requester: Person/entity that calls for the assessment of a given product SaaS, specifying
what are your goals and objectives;
• Evaluator: Person in which dominates all the guidelines for the application of the method
SaaSQuality, serving as a guide and contact between the process and its participants.
• Users Interviewed: Participants that have the purpose to give critical views (positive and
negative) in relation to quality aspects evaluated within the SaaS product;
• Specialist: Person who holds total knowledge in relation to the context of the application
of system evaluated, in the case in question, the SaaS.
The actors performed activities present in stages of the evaluation process. The steps described
below (Figure 3) are specific to the SaaSQuality, which were based on best practices and
expertise required in the process of evaluation ISO/IEC 14598, but they have a simplification and
a definition itself focused on systems SaaS, below a brief summary for each stage of the process.
Figure 3 - Stages of the evaluation process.
1. Define Objectives and Contextualization of the Evaluation: The objective of this phase is
clarify the purpose of the evaluation that will be held. The Requestor will specify the
software to be evaluated together with the version and other necessary requirements.
2. Define and Configure the Model of Quality: After the definition of model of quality that
will be used in practical assessments, at this stage must be performed to configuration of
the same, specifying which criteria and quality requirements will be used;
9. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
109
3. Identify Measurable Metric: This stage is based in the mapping of the characteristics of
quality in measurable attributes, allowing their score and evaluation;
4. Define Score and Criteria for Judgment: In this stage will be set the numerical values for
the attributes measurable, establishing criteria for judgment for the comparisons of the
results obtained;
5. Project the Evaluation: In this stage should be defined the evaluation plan to be followed
during the practical assessments, containing guidelines and procedures allowing an
application structured and repeatable;
6. Execute the Evaluation: In the last stage of the process of evaluation, the Evaluator must
use everything that was presented in previous stages, effecting the following activities:
Obtaining Measures; Comparison with Criteria; and Judgment the Results.
Some of the stages presented may experience minor changes as a result of evaluations more
specific, such changes will be made by the Evaluator and Specialist.
6. RESULTS OF VALIDATION AND EVALUATION
The validation of the research was carried out in two moments. It was initially applied a case
study in relation to a SaaS product, providing a validation regarding the proposed method; and a
comparative between the SaaSQuality and the MEDE-Pros was subsequently carried out with the
purpose to identify similarities, differences and limitations between both methods.
6.1. Case Study ("Salesforce CRM Sales")
The case study was carried out by applying the SaaSQuality in relation to the product "Salesforce
CRM Sales", a Customer Relationship Management (CRM) system that has the purpose facilitate
and improve the relationship of the organizations and their respective customers. The following
will be done the detailing of each step of the process of evaluation, relating them with the case
study, identifying what was done at each stage of the process:
1-Define Objectives and Contextualization of the Evaluation: In the context of this work, the
objective of the application of the method for the study of the case was to evaluate the
SaaSQuality, in relation to your model of quality, process of evaluation and the techniques used.
The expectation of the study is also assess the product “Salesforce CRM Sales”, noting their
compliances with requirements of quality.
2-Define and Configure the Model of Quality: The model of quality adopted in the practical
assessments was the model proposed in the section "Quality Model for SaaSQuality" (Figure 1).
This model has been chosen and used, because in addition to include a number of criteria relating
to the evaluation of the quality of a system SaaS, it also presents a division of requirements
(guidelines) and attributes of evaluation, by facilitating their use in practical assessments.
3-Identify Measurable Metric: At this stage there was the splitting of the requirements of quality
in attributes that can be measured and punctuated. To realize this task, techniques and
methodologies auxiliary staffs have been used to support and facilitate the identification of metric
measurable. The technique used in this evaluation was the use of list of verification, in order to
allow an efficient mapping of the requirements of the model of quality in attributes and
measurable items.
The attributes measurable contained in the model of quality were raised by means of the
knowledge of the Specialist, creating simple and objective questions allowing its evaluation and
10. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
110
punctuation in the form of a checklist. On totals have been proposed 70 issues to be evaluated, the
questions were decomposed in 7 (seven) different groups, related to the criteria of quality model,
they are: functionality, usability, security, performance, support, service level, and portability.
The list of verification proposal for the evaluations added additional information in order to allow
its use by the Evaluator in the form of a template for application. The additional information have
been related and added to the list of verification, indicating, i.e., the average time elapsed in the
evaluations, objectivity of the evaluation, definition of the local and the data collected, among
other information, by facilitating the implementation and the control of the evaluations.
4-Define Score and Criteria for Judgment: The list of verification sets out for each criterion of
quality 10 attributes in the form of questions, totalling a list of verification with 70 items. This
number has been defined, as it makes it possible to build a full list the verification and at the same
time is not exhaustive, because would damage the time in the implementation of the evaluations.
The weighting given for each issue has been defined in the following way:
• Maximum value: "1" (highest score);
• Minimum value: "0" (lowest score).
•
For each criteria of quality have been carried out 15 assessments with different people, that is to
say, different instances of assessments were performed, and obtained different notes in relation to
the final quality of the criterion assessed.
At the end of all the 15 evaluations, thereby achieving 15 different values in relation to the quality
of each criterion assessed, has been carried out the arithmetic mean of these values, to enable a
better comparison of the results.
This process of obtaining the average of the quality, it was accomplished for 7 (seven) evaluation
criteria, thus allowing the separation of the specific note of each criterion of the final note of the
evaluated product, because it is interesting for the Requester of assessment identify the notes
separately, checking which quality criteria are below the required level of quality, by making it
possible to conduct a trial efficient together with adjustments and improvements.
For this judgment the authors were based on a lifting done at approximately 300 products of
software’s [32]. The criteria are based essentially on three levels: Superior, Medium and Lower,
and can be viewed in Figure 4.
Figure 4 - Levels of quality of a product of software.
These criteria have been incorporated into the SaaSQuality, taking the following definitions and
prospects of conclusion:
11. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
111
• Superior level, the product of software should be in accordance with at least 80% of the
quality requirements specified. This means that the note can vary from 100 to 80, on a
scale of 0 to 100;
• Medium level, the product of software should be in accordance with at least 50% of the
quality requirements specified. This means that the note can vary from 80 to 50;
• Lower level, the product of software can have a note of 50 to 0, by presenting a low level
of quality.
5-Project the Evaluation: The projection of the practice evaluations were followed specific
guidelines. The users interviewed during the evaluations were students with advanced knowledge
in information technology, having to a certain way familiarity with the SaaS product assessed.
The time of each evaluation has been estimated and implemented between 40 to 50 minutes,
trying not to overcome this time, to ensure a rapid assessment and practice. All the information
and data raised by Users Interviewed were kept of possession only of the authors, thus ensuring
confidentiality on the part of those interviewed. Information obtained does not have commercial
value, only add value to the research and development of this work.
In total have been carried out 15 assessments with 15 different people. This number of
assessments had objective improves it of the proposed method, together with the convergence of
the data obtained. This is because initial assessments showed errors and details to be improved,
both on the part of the model of quality and on the part of the process of evaluation.
6- Execute the Evaluation: Basically at this stage of the case study the Evaluator has executed
three tasks:
• Collection of the measures;
• Comparison of the measures with criteria pre-defined, and finally;
• The judgment of the data obtained in the course of the evaluations.
In accordance with activities of obtaining of measures, all have been collected through the
evaluations made by the Users Interviewed, making clear the impersonality of evaluator that was
present only to doubts and perform the evaluation in a repeatable manner.
At the end of the evaluations, and early of activity de comparison of criteria, the numerical data
have been treated and compared with the criteria, enabling a final judgment. The activity de
judgment of the data has been made together with the development of a final report of evaluation.
O objective to draw up a final report it is indicate the positive and negative points relating them to
the quality criteria judged.
The report in addition to identify relevant aspects on the quality of the SaaS product, also
identifies problematic aspects that occurred during the implementation of the evaluations, such as,
for example, unavailability of the product, errors generated in the course of the evaluation, lack of
information the product, among others.
7- Considerations and Results: On end of all the evaluations, the product has had a average note
76,6 in relation to the final quality, falls within the level "medium" of quality (Figure 6).
12. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
112
Figure 6 - The quality achieved by the "SalesForce CRM Sales"
Even by presenting a level "medium" of quality, not all the criteria of the evaluated product had
notes unsatisfactory within the context SaaS (Figure 7).
Figure 7 - Note assigned in relation to each criteria of quality.
One can conclude that, the requirements "Functionality" and "Usability" had the highest score in
the evaluation performed, contemplating satisfactory levels of quality. Note also that these
requirements are similar to that of a product of conventional software, not considering intrinsic
characteristics of a system SaaS.
On the other hand, by examining the criteria “Support” and “Level of Service”, it emerges that
both have had the worst notes within the criteria evaluated, noting that they are characteristics
aimed directly to a SaaS product. This result has a negative impact on the quality of the product,
because both the criteria represent an important and great impact to the SaaS context, requiring
studies and improvements in relation to your requirements, for example, aspects linked to SLA's,
management of data, auditability, customization, stability, among others.
6.2. Comparison with the method mede-pros
This comparison has been drawn up with the aim of responding to some questions that can be
raised the end of the case study.
13. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
113
• What need for the development of a specific method for assessment of products SaaS?
• The conventional methods are not ready, and appropriate to assess a product SaaS?
• Which the similarities and differences of the SaaSQuality in comparison with
conventional methods?
Trying to answer the questions above with good reason, adding additional information to the
study of the case, it was carried out a comparative between methods SaaSQuality and MEDE-
Pros. In order to achieve this comparative some steps have been followed, allowing the
comparison between the data and results of both methods.
• Step 1: The first activity of comparative was the choice of a conventional method that
will provide a practical assessment of the quality of a product of software, in the case of
this research the MEDE-pros;
• Step 2: The second stage, was the study and the detail of the model of quality in which
the MEDE-pros is based, based on requirements and quality attributes;
• Step 3: For the completion of the third stage, it was necessary to use a set of questions
and checks (checklist) present in the book: "Quality of Product of Software" (Colombo &
Guerra, 2009). This checklist was drawn up in order to be applied to the directly MEDE-
pros;
• Step 4: The fourth stage makes reference to the application of the method MEDE-pros on
the product "Salesforce CRM Sales”;
• Step 5: At this stage, the data obtained in the evaluations with the MEDE-pros were
compared with the data obtained in the study of the case by the SaaSQuality.
At the end of the comparative, with the data analyzed and interpreted, a graphic of the type
"radar" was mounted (Figure 8), was plotted the values of each criteria of quality in the course of
the axes, represented by the two methods (SaaSQuality and MEDE-pros).
Figure 8 - The result of the comparative of quality criteria (SaaSQuality vs MEDE-pros)
In accordance with the Figure 8, what is observed is the convergence and the divergence of the
data in relation to the criteria of quality. Functionality, Usability and Security, have had a great
convergence of data in relation to methods. This is due to the fact of that both in conventional
14. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
114
systems such as the SaaS those quality criteria are similar. Below follows a small description of
these similarities.
Functionality: If it seems mainly in the aspects of interoperability, access, and accuracy, thus
enabling the guarantee of functions that follow the needs of customers, correctly and accurately,
together with the possibility of integration with other systems legacies of the organization.
Usability: The requirements operability and attractiveness are necessary in computing systems, it
is extremely importance to a greater user satisfaction.
Security: Even having a greater impact on the paradigm SaaS, security aspects are very important
in systems conventional, especially systems that work with critical data of business organizations,
requiring greater reliability, integrity and availability for these data.
The Portability criterion also had a convergence the data in both methods, however, this feature
presents an application context quite different in both cases. On SaaS, the portability criterion is
more focused for browsers and the doors of communication. Already in the conventional systems
to portability is more related to operating systems and distributions. In other words, the data
obtained even if they are converging, cannot be considered to be similar, because, the coexistence
requirements and adaptability have applicability well different in both the paradigm.
The criterion Performance has had a small difference in the data, but it was something already
expected, because the SaaS systems due to their way of access, by means of tenants and multi-
tenants have distinct characteristics in scalability of their users and in expansibility of new
services to the system [33, 34].
The Service of Level and Support have had the greatest divergences in the results. The reason is
due to the fact that the quality requisites are influenced directly by features of the IT service
management, not covered by standard ISO 9126, such as, for example, customizations;
management of incidents and problems; SLA; plans of continuity; management of data; and
auditability. Below, the main points of the analysis of these requirements.
The Service of Level can’t be measured by the method MEDE-pros, because for conventional
systems (different of the SaaS), features such as SLA's, management of data, plans of continuity,
among others, are not included in model of quality the method MEDE-pros;
The Support had a good relationship between the characteristics of testability and stability,
however, when it comes to incidents and personalization, the characteristics of the SaaS and
conventional systems are quite different, thus causing differences between the evaluations of both
methods.
At the end of comparisons is concluded that, from the comparisons made, it is clear that a
conventional method is not entirely appropriate for evaluations of products SaaS. Some of the
characteristics were been well evaluated by the method MEDE-pros, but others have had their
assessment impaired, because of the context in which they were being employed. This is due to
the fact, among other factors, the use of the model of quality.
7. CONCLUSIONS
This paper has put forward a proposal for the development of a method for assessing the quality
of a product of Software as a Service (SaaS), known as SaaSQuality. The proposed method was
15. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
115
based on a model of specific quality to the SaaS paradigm, by proposing a process of evaluation
own, simple and effective.
For the construction of the specific model to the SaaS paradigm, allowing its use in practice by
the SaaSQuality, there has been an integration between criteria and principles of methods of
assessment of the quality of the product of software, with criteria of methods of management de
services de TI.
The criteria defined has enabled the lifting and the impact of quality criteria specific to the SaaS
context, dividing them into groups of characteristics and sub-characteristics, in order to show its
impact both positive and negative to this new paradigm.
The model of quality is a compilation of the main features present in a product of software and a
service of IT. The evaluations performed by the method in question were carried out by means of
a list of verification (checklist), contemplating through measurable attributes the score and
measurement of quality requirements.
At the end of the research the authors highlight aspects important allowing the extension of
studies on future work. The first point with regard to the proposal of a method to assess and assist
the guarantee of quality in relation to process of development of a product SaaS.
The second approach with regard to the measurement of the SaaSQuality as to the quality in use.
During the definition of the problem has been given a greater emphasis on the internal quality and
foreign.
Finally, the third refers to supplement and deepening of the list of verification (checklist). In the
present paper, emphasis was given in attributes that provide a general assessment of the quality of
a SaaS product; all these attributes have been assessed with the same weight and punctuations.
ACKNOWLEDGEMENTS
The authors thank The Coordination for the Improvement of Higher Level or Education (CAPES)
and The National Council of Technological and Scientific Development (CNPq) for their
financial support.
REFERENCES
[1] Kan, S. H. (2002). Metrics and Models in Software Quality Engineering. Addison-Wesley.
[2] Akella, P. S.; Rao, K. N. (2011) Effective Independent Quality Assessment Using IV&V.
International Journal of Computer Science and Information Technology (IJCSIT), Vol 3 (3), 320-332.
[3] Krishna, P.; Rao, R. (2011) Software Quality Assurance in CMM and XPA Comparative Study.
International Journal of Computer Science and Information Technologies (IJCSIT), Vol. 2 (6) , 2915-
2919.
[4] Lew, P.; Zhang, L.; Wang, S.; Jiang, W. (2008). Guidelines to Determine Quality for Web-Based
Software Applications. In: Computational Intelligence for Modelling Control & Automation,p 709,
IEEE Publications, Vienna, Austria.
[5] Colombo, R. M. T.; Guerra A. C. (2009). Information technology: Quality of Product of Software,
MCT/SEPIN.
[6] Barney, S.; Wohlin, C. (2009). Software Product Quality: Ensuring a Common Goal. Lecture Notes in
Computer Science 3(5), 256-267.
[7] Auer, T. (1998). Quality of IS use. European Journal of Information Systems 7(9), 192-201.
[8] Dubey, A.; Wagle, D. (2006). Delivering software as a service. The McKinsey Quarterly 3(5),1-12.
16. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
116
[9] O’Brien, L.; Bass, L.; Merson, P. (2005). Quality attributes and service-oriented architectures.
Technical report, Carnegie Mellon University.
[10] Havelka, D.; Sutton, S. G.; Arnold, V. (1998). A methodology for developing measurement criteria
for assurance services: An application in information systems assurance. Journal of Practice and
Theory 8(5),80-87.
[11] Jureta, I. J.; Herssens, C.; Faulkner, S. (2009). A comprehensive quality model for service-oriented
systems. Software Quality Control 7(4), 65-98.
[12] Cancian, M. H. (2009). A proposal of reference guide for providers of software as a service.
Dissertation in Automation and Systems Engineering, University Santa Catarina.
[13] Cancian, M. H.; Rabelo, R.J.; Wangenheim, C. G. V. (2009). A proposal for drawing up of the
contract for Level of Service to Software as a Service (SaaS). In 8th International Information and
Telecommunication Technologies Symposium, p 410, IEEE Publications, Florianópolis, Brasil.
[14] Rosenberg, F.; Leitner, P.; Michlmayr, A. P. C.; Dustdar, S. (2008). Towards composition as a
service-a quality of service driven approach. Dstributed Systems Group.
[15] Silva, E. M.; Yue, G. K.; Rotondaro, R. G.; Laurindo, F. J. B. (2006). Management of the quality of
services for IT:in search of competitiveness. Magazine Production 2(6), 329-340.
[16] Miguel, P. A. C.; Salomi, G. E. (2004). A review of the models for measurement of the quality of
services. Magazine Production 10(1), 12-30.
[17] Jung, C. F. (2004). Methodology for research and development: applied to new technologies. Axcel
Books Publishing House.
[18] Wohlin, C.; Runeson, P.; Host, M.; Ohlsson, M. C.; Regneel, B.; Wesslén, A. (2000).
Experimentation in software engineering: An introduction. Kluwer Academic Plublishers.
[19] ISO/IEC 9126. (1991). The international organization for standardization. Software engineering
Product quality.
[20] ITIL v3. (2008). Information technology infrastructure library. Publications Service Management.
[21] TGI. (2007). Information technology governance institute. COBIT 4.1: Control objectives,
Management guidelines, Maturity models. Rolling Meadows: ITGI.
[22] ISO/IEC 14598-5. (1997). International standard. information technology - software product
evaluation - part 5: Process for evaluators.
[23] Duarte Filho, N. F.; Padua, C. I. P. S.; Zambalde, A. L.; Bermejo, P. H. S. (2010). Quality attributes
for SaaS´s products. In: 5th Iberian Conference on Information Systems and Technology, p 80, IEEE
Publications, Santiago de Compostela, Spain.
[24] Boehm, B. W. (1981). Software engineering economics. Prentice-Hall.
[25] Gatti, M. A. C.; Werneck, V. B. (2004). Quality requirements of web applications. Available at:
http://www.ime.uerj.br/cadernos/cadinf/, Accessed in 2 September, 2011.
[26] Farbey, B. (1991). Exploring Requirements: Quality Before Design. European Journal of Information
Systems 1(3), 145-147.
[27] Hoffman, M.; Kuhn, N.; Weber, M.; Bittner, M. (2004). Requirements for requirements management
tools. In: 12th IEEE International Requirements Engineering Conference, p 165, IEEE Publications,
Kyoto, Japan.
[28] Ma, D. (2007). The business model of ’software-as-a-service’. In: International Conference on
Services Computing, p 701, IEEE Publications, Hawaii, USA.
[29] Colombo, R.; Guerra, A. (2002). The evaluation method for software product. In 19th International
Conference on Software and Systems Engineering and their Applications, p 143, IEEE Publications,
Paris, França.
[30] Guerra, A. C.; Colombo, R. T.; Aguayo, M. T. V.; Peres, R. D. (2007). Model of quality of
components of software. In: Conference IADIS Ibero-Americana, p 231, Vila Real, Portugal.
[31] MEDE-PROS. (1996). Method for assessing the quality of software product. Center for Information
Technology Renato Archer-CTI/MCT.
[32] Martinez, M. R. M. (1999). The software product evaluation data base -supporting mede-pros. In:
International Software Engineering Standards Symposium, IEEE Publications, Curitiba, Brazil.
[33] Chong, F.; Carraro, G.; Wolter, R. (2009). Multi-tenant data architecture. Available at:
http://msdn2.microsoft.com/, Accessed in 15 December, 2011.
[34] Choudhary, V. (2007). Softwares as a services: Implications for investment in software development.
In 40th Annual Hawaii International Conference on System Sciencies, p 58, IEEE Publications,
Hawaii.
17. International Journal of Computer Science & Information Technology (IJCSIT) Vol 5, No 3, June 2013
117
Authors
Nemésio Freitas Duarte Filho: Graduation in Computer Science from the Federal University of Lavras,
and master's degree at the Federal University of Minas Gerais. Has experience in Software Engineering,
Governance, and IT Management. Has certification in the areas of IT governance and business process
modelling (ITIL v2, COBIT 4.1and OCEB Fundamental-OMG)
Clarindo Isaias Pereira da Silva e Pádua:
Graduation in Electrical Engineering from the Federal
University of Minas Gerais, master's in Computer Science from the Federal University of Minas Gerais
and doctorate in Computer Science - University of Southampton. Has experience in Computing Systems,
working mainly in the areas of Software Engineering and Usability Engineering.
Paulo Henrique de Souza Bermejo: Adjunct Professor of the Department of Computer Science of the
Federal University of Lavras. Doctorate in Knowledge Engineering and Management by the Federal
University of Santa Catarina. Is certified in IT Governance framework (Cobit) and representative
(advocate member) of ISACA.
Andre Luiz Zambalde:
Graduation in Electrical Engineering Telecommunications from the National
Institute of Telecommunications in Santa Rita do Sapucaí, master's at Electric Engineering from
University Federal de Itajubá and doctorate in Computer Science from University Federal do Rio de
Janeiro. Has experience in information technology in education, distance learning and information
systems.
Urlan Salgado de Barros: Master's Degree in Computer Science from the University Federal do Paraná.
Graduation in Computer Science from the Federal University of Lavras. Has experience in the area of
Computer Science, with emphasis in Computer Networks and Computer Security.