Experience Report on the Construction of Quality Models for Some Content Management Software Domains

Franch, Xavier; Quer, Carme; Cantón, Jordi; Salietti, R.

doi:10.1109/iccbss.2008.32

Cited by 3 publications

(6 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the one hand, subcharacteristics that correspond to functionality and are not identified in [12]. These subcharacteristics are Contents Verifiabiliness, Media Management and Agenda Management.…”

Section: Form Textmentioning

confidence: 95%

See 1 more Smart Citation

A catalogue of functional software requirement patterns for the domain of content management systems

Palomares

Quer

Franch

et al. 2013

Proceedings of the 28th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Software requirement patterns have been proposed as an artifact for fostering requirements reuse. When we define these patterns for the functional part of a software system, we realize that most of patterns are specific of a software domain. This paper presents and analyzes a catalogue of functional software requirement patterns for the domain of content management, and gives an overview of how this catalogue has been constructed from the systematic analysis of 6 existing software specification documents with the support of expert assessment.

show abstract

Section: Form Textmentioning

confidence: 95%

“…Therefore, this is the natural place to group the classifiers for CMS functionality. As starting point for the decomposition of Suitability, we used the ISO/IEC-9126-1-based quality model for the CMS domain that we proposed in [12].…”

Section: The Cataloguementioning

confidence: 99%

A catalogue of functional software requirement patterns for the domain of content management systems

Palomares

Quer

Franch

et al. 2013

Proceedings of the 28th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

show abstract

“…In addition, they provided guidelines to customize the ISO for software components. Additionally, some experiences on establishing and adapting software QMs can be found in Calero et al (2007), Franch et al (2008, Behkamal, Kahani and Akbari (2009), Villalba, Fernández-Sanz and Martínez (2010), Kläs, Lampasona and Münch (2011).…”

Section: Quality Model Establishmentmentioning

confidence: 99%

“…For instance, it can be useful to specify requirements of CES, to serve as baseline for the establishment and application of metrics, to support evaluation of software products of CES, and as an initial reference for constructing specific QMs for organizations, projects, and phases of projects. As we do not expect to cover specific applications domains in which CES have been employed, the level of abstraction of our QM lies between general QMs, such as the proposed by ISO/IEC 25010 (2011), Dromey (1995), Boehm, Brown andLipow (1976), McCall, Richards andWalters (1977), Lochmann and Goeb (2011)) and domain-oriented QMs (e.g., the proposed by Franch et al (2008), Behkamal, Kahani and Akbari (2009), Villalba, Fernández-Sanz and Martínez (2010), Kim and Lee (2009). Hence, our QM is composed of a subset quality characteristics of ISO/IEC 25010 (2011), as QMs must be reduced to eliminate redundancy and increase its efficiency (VILLALBA; FERNÁNDEZ-SANZ; MARTÍNEZ, 2010).…”

Section: Quality Model For Critical Embedded Systems (Qm4ces)mentioning

confidence: 99%

A quality model for critical embedded systems

Oliveira¹

View full text Add to dashboard Cite

Dedico este trabalho em memória de meu pai, Braulino Mendonça de Oliveira, e minha irmã, Flávia Roberto do Nascimento Oliveira, que com tão pouco tempo vivendo ao meu lado, me fazem amá-los eternamente em minha jornada. ACKNOWLEDGEMENTSAs pessoas são as coisas mais importantes deste mundo. Não importa se fazem o bem ou o mau. Cabe a nós, antes de mais nada, compreendê-las e compartilhar de nossas vidas com elas. Só assim é possível sonhar com um mundo repleto de amor e coisas boas. É deste modo que começo esta seção tão importante de meu trabalho, pois eternamente agradecido sou por cada uma das pessoas que estiveram e estarão presentes durante minha trajetória.O maior dos amores não pode ser escrito nem dito. Trata-se de um sentimento recíproco, verdadeiro e infinito que nos motiva em todos os momentos, sejam eles bons ou ruins. Não importa a distância e nem mesmo o tempo. Por esse amor, serei eternamente grato à minha mãe, Osania Roberto do Nascimento Oliveira, que me fez chegar até aqui.Agradeço imensamente a Prof. Elisa Yumi Nakagawa por me orientar na condução deste trabalho. Sua dedicação e envolvimento foram fundamentais para meu desenvolvimento pessoal e profissional.À Lina Maria Garcés-Rodriguez, minha eterna gratidão pelo apoio e incentivo ao longo dos últimos três anos.À minha família, pelo respeito, consideração e confiança depositados em mim. À Profa. Silvia Maria do Espírito Santo, pela confiança e incentivo para ingressar na pós-graduação. Ao Prof. Dr. Adenilso da Silva Simão, pelo respeito à minha atuação enquanto representante discente e consideração pelos alunos do PPG-CCMC.À todos os professores que tive a oportunidade de encontrar desde o ensino básico, pois me fizeram admirar essa profissão de mudar o mundo.Aos amigos da PuraTI, Diego e André, pela oportunidade de trabalhar juntos por um objetivo e pelo exemplo de perseverança.À todos (e são muitos) colegas e amigos do LabES, pelas inúmeras experiências, aprendizados e lições.Ao serviço de pós-graduação do ICMC, em especial à Carol Murata, Leonardo Miyake e Lycaena Couvre.Ao CNPq, CAPES e FAPESP pelo apoio financeiro."Será algo de maravilhoso quando vislumbrarmos a verdadeira personalidade do homem. Crescerá naturalmente, simplesmente, à maneira das flores ou das árvores. Nunca se porá em discórdia, nem entrará em discussões ou contendas. Nada terá de provar. Conhecerá tudo. E no entanto não se ocupará do conhecimento. Será sábia. Bens materiais não medirão seu valor. Não haverá de ter coisa alguma. E terá no entanto todas as coisas; tão rica, o que dela venha a se tirar, ela ainda o haverá de ter. Não estará sempre se intrometendo com os demais, ou pedindo-lhes para serem iguais a si própria. Ela os amará por serem diferentes. E embora não vá se intrometer com os demais, ajudará a todos, como algo de belo nos ajuda por ser o que é."

show abstract

“…In this case, a compound classifier Content Management System was added to the root. As starting point for the decomposition of Content Management System, the ISO/IEC-9126-1-based quality model for the CMS domain (proposed by Franch et al [177]) was used. Although, some changes were needed in order to accommodate some of the F-SRPs.…”

Section: Text Input Managementmentioning

confidence: 99%

Definition and use of software requirement patterns in requirements engineering

Palomares Bonache

View full text Add to dashboard Cite

The final quality of software products and services depends on the requirements stated in the Software Requirements Specifications (SRSs). However, some problems like ambiguity, incompleteness and inconsistency have been reported in the writing of SRSs, especially when natural language is used. Requirements reuse has been proposed as a key asset for requirements engineers to efficiently elicit, validate and document software requirements and, as a consequence, obtain SRSs of better quality through more effective engineering processes. Among all the possible techniques to achieve reuse, patterns hold a prominent position. In their most classical form, patterns describe problems that occur over and over again, and then describe the core of the solution to these problems. Software engineering practitioners have adopted the notion of pattern in several contexts, remarkably related to software design (e.g., design patterns and software architectural patterns), but also in other software development phases, both earlier and later. Following this strategy, requirement patterns emerge as a natural way to reuse knowledge during the Requirements Engineering (RE) stage. Although there have been several techniques proposed to reuse requirements, it has been observed that no concrete proposal has achieved a wide acceptance, neither any covered all the necessary elements to encourage organizations to adopt requirements reuse. As a consequence, this thesis proposes the use of Software Requirement Patterns (SRPs) as a means to capture and reuse requirements knowledge in the context of information technology projects. Following the typical context-problem-solution structure of patterns, an SRP mainly consists of: a template (solution) that may generate one or more requirements when applied in a certain project, and some information (context-problem) to identify its applicability in that project. To facilitate their use, SRPs are encapsulated inside the PABRE (PAttern-Based Requirements Elicitation) framework. The framework covers all the elements that could be critical for the adoption of a requirements reuse technique. Specifically, the framework includes: - A metamodel that describes the structure and semantics of SRPs and their organization inside a catalogue. - An SRP catalogue composed by non-functional, non-technical and functional SRPs, the functional ones being specific for the content management system domain. - A method for guiding the use of an SRP catalogue during requirements elicitation and specification, as well as another one for constructing and updating it. - An economic model to perform cost-benefit analysis on the adoption of SRPs based on return-on-investment. - The PABRE system as technological support. In order to analyse the benefits and drawbacks of the SRPs proposed in this thesis, two empirical studies have been carried out to investigate the perception of participants about requirement patterns in general and SRPs in particular. The first one is an exploratory survey addressed to information technology people with industrial experience in RE, which analyses the current state of the practice of requirement patterns approaches. The second one corresponds to a set of semi-structured interviews, focussed on the SRP approach, conducted to requirements engineers of Swedish organizations. Moreover, as it has been discovered that there are few empirical studies showing the state of the practice of requirements reuse in industry, the first study also explores the current situation of requirements reuse practices in organizations. La qualitat final dels productes i serveis de software depèn del requisits definits en l’especificació de Requisits Software (ERS). Tot i així, alguns problemes com la ambigüitat, incompletesa i inconsistència han sigut detectats en la escriptura dels ERS, especialment quan el llenguatge natural és usat per escriure’ls. La reutilització de requisits ha sigut proposada com un recurs clau pels enginyers de requisits per tal d’obtenir, validar i documentar requisits software i, com a conseqüència, obtenir ERS de millor qualitat usant processos d’enginyeria més efectius. Entre totes les tècniques possibles per aconseguir la reutilització, els patrons tenen una posició destacada. En la seva forma més clàssica, els patrons descriuen problemes que ocorren sovint, i després descriuen la part central de la solució a aquests problemes. Els professionals de la enginyeria del software han adoptat la noció de patró en diferents àmbits, especialment en els relacionats amb el disseny del software (per exemple, els patrons de disseny i els patrons d’arquitectura del software), però també en altres etapes del desenvolupament del software, tant abans com després del seu disseny. Seguint aquesta estratègia, els patrons de requisits emergeixen com una manera natural de reutilitzar coneixement durant l’etapa d’enginyeria de requisits. Tot i que hi ha hagut varies tècniques proposades per reutilitzar requisits, s’ha observat que no hi ha cap proposta concreta que hagi aconseguit una àmplia acceptació, ni cap proposta completa que cobreixi tots els elements necessaris per animar a les organitzacions a adoptar la reutilització de requisits. Com a conseqüència, aquesta tesis proposa l’ús de Patrons de Requisits Software (en anglès Software Requirement Patterns o SRPs) com un medi per capturar i reutilitzar coneixement de requisits en l’àmbit de projectes de tecnologia de la informació. Seguint la estructura típica dels patrons de context-problema-solució, un SRP consisteix en: una plantilla (solució) que pot generar un o més requisits quan és aplicat en un projecte específic, i informació relacionada (context-problema) per identificar la seva aplicabilitat en un projecte. Per facilitar el seu ús, els SRP han sigut encapsulats dintre del framework PABRE (de l’anglès PAttern-Based Requirements Elicitation). El framework cobreix tots els elements que podrien ser crítics per adoptar una tècnica de reutilització de requisits. Més detalladament, el framework inclou: - Un meta model que descriu la estructura i semàntica dels SRPs i la seva organització dintre d’un catàleg.

show abstract

Experience Report on the Construction of Quality Models for Some Content Management Software Domains

Abstract: In previous work, we proposed

Cited by 3 publications

References 15 publications

A catalogue of functional software requirement patterns for the domain of content management systems

A catalogue of functional software requirement patterns for the domain of content management systems

A quality model for critical embedded systems

Definition and use of software requirement patterns in requirements engineering

Contact Info

Product

Resources

About