Managing Non-Technical Requirements in COTS Components Selection

Carvallo, Juan Pablo; Franch, Xavier; Quer, Carme

doi:10.1109/re.2006.40

Cited by 36 publications

(35 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Nevertheless, since they represent an important aspect when evaluating web services for their prospective use, we have also considered them. We have taken as the basis for comparison the extension of ISO-9126 with non-technical quality characteristics presented in [81]. We adapted the subcharacteristics to the context of web services, therefore the non-technical subcharacteristics we propose are regulatory (i.e.…”

Section: Which Quality Factors Are the Most Addressed In The Quality mentioning

confidence: 99%

Quality models for web services: A systematic mapping

Oriol

Marco

Franch

2014

Information and Software Technology

View full text Add to dashboard Cite

Context: Quality of Service (QoS) is a major issue in various web service related activities. Quality models have been proposed as the engineering artefact to provide a common framework of understanding for QoS, by defining the quality factors that apply to web service usage. Objective: The goal of this study is to evaluate the current state of the art of the proposed quality models for web services, specifically: (1) which are these proposals and how are they related; (2) what are their structural characteristics; (3) what quality factors are the most and least addressed; and (4) what are their most consolidated definitions. Method: We have conducted a systematic mapping by defining a robust protocol that combines automatic and manual searches from different sources. We used a rigorous method to elicitate the keywords from the research questions and a selection criteria to retrieve the final papers to evaluate. We have adopted the ISO/IEC 25010 standard to articulate our analysis. Results: We have evaluated 47 different quality models from 65 papers that fulfilled the selection criteria. By analyzing in depth these quality models, we have: 1) distributed the proposals along the time dimension and identified their relationships; 2) analysed their size (visualizing the number of nodes and levels) and definition coverage (as indicator of quality of the proposals); 3) quantified the coverage of the different ISO/IEC 25010 quality factors by the proposals; 4) identified the quality factors that appeared in at least 30% of the surveyed proposals and provided the most consolidated definitions for them. Conclusions: We believe that this panoramic view on the anatomy of the quality models for web services may be a good reference for prospective researchers and practitioners in the field and especially may help avoiding the definition of new proposals that do not align with current research.

show abstract

Section: Which Quality Factors Are the Most Addressed In The Quality mentioning

confidence: 99%

Quality models for web services: A systematic mapping

Oriol

Marco

Franch

2014

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Although this situation could be thought as a kind of incompleteness, in fact we are allowing having dedicated classification schemas for particular categories of patterns, e.g. a performance classification schema, a classification schema just for the non-technical criteria [16] and then allowing to compound them for having a multi-source global classification schema. Also we remark that the PABRE method [15] benefits from this existence of multiple classification schemas since nothing prevents changing from one schema to another during catalogue browsing.…”

Section: Templatementioning

confidence: 99%

A Metamodel for Software Requirement Patterns

Franch

Palomares

Quer

et al. 2010

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context and motivation]Software Requirement Patterns (SRP) are a type of artifact that may be used during requirements elicitation that also impact positively in other activities like documentation and validation. In our experiences, SRP show a great percentage of reuse for the non-functional requirements needed in call-for-tender requirement specifications. [Question / problem] We are facing the need of formulating the accurate definition of SRP for their use in call-for-tender processes to allow reasoning rigorously and know more about their semantics and applicability. [Principal ideas / results] In this paper we present a metamodel for SRP around three main concepts: 1) the structure of SRP themselves; 2) the relationships among them; 3) the classification criteria for grouping them.[Contribution] We provide a rigorous definition that shows the concepts that are of interest when defining and applying SRP.

show abstract

“…Supplier experience and economical health, warranties, services provided, and hidden costs are some of these issues. For more details regarding them, we refer to [8,9].…”

Section: L4: Don't Let Over-specification Run Your Project Out Of Timmentioning

confidence: 99%