Figure 3 - uploaded by Francisca Losavio
Content may be subject to copyright.
![– External and Internal Quality Model ISO/IEC 9126-1 [23]](profile/Francisca-Losavio/publication/220299390/figure/fig2/AS:305426315923459@1449830716939/External-and-Internal-Quality-Model-ISO-IEC-9126-1-23.png)
Source publication
![Figure 1-RECLAMO [8]](profile/Francisca-Losavio/publication/220299390/figure/fig9/AS:668202648473613@1536323334820/RECLAMO-8_Q320.jpg)
![Figure 2 – Organization of the SQuaRE series of standards [21]](profile/Francisca-Losavio/publication/220299390/figure/fig1/AS:305426315923458@1449830716914/Organization-of-the-SQuaRE-series-of-standards-21_Q320.jpg)
![Figure 3 – External and Internal Quality Model ISO/IEC 9126-1 [23]](profile/Francisca-Losavio/publication/220299390/figure/fig2/AS:305426315923459@1449830716939/External-and-Internal-Quality-Model-ISO-IEC-9126-1-23_Q320.jpg)
![Figure 4 – In Use Quality Model [23]](profile/Francisca-Losavio/publication/220299390/figure/fig3/AS:305426315923460@1449830716960/In-Use-Quality-Model-23_Q320.jpg)
![Figure 5 – System requirements categorization [21]](profile/Francisca-Losavio/publication/220299390/figure/fig4/AS:305426315923461@1449830716977/System-requirements-categorization-21_Q320.jpg)
Abstract Object-oriented analysis and design have been more concerned with system functionality, neglecting non-functional aspects; the result is code which is tangled and difficult to maintain, contradicting main principles of object orientation. Aspect Oriented Software Development (AOSD) proposes the early specification of non-functional requiremen...
Context in source publication
Context 1
... product quality is actually defined by three quality models: external, internal (see Figure 3) and in use quality model (see Figure 4). Internal quality refers to the static properties on the structure (such as the number of lines of code, modular complexity, number of faults found in a sequence or activity diagram) of the software product (conformed by all the intermediate products or artifacts) produced during the development process. ...
Similar publications
In the Domain Engineering (DE) discipline, different approaches are used for one purpose, the treatment of non-functional requirements (NFR) to build a reference architecture (RA), or generic architecture from which all product members of a family of a domain, are generated. Consequently, the same process is adapted to different contexts and abstra...
Aspect oriented software development (AOSD), based on aspect oriented programming (AOP), is part of the post-object paradigm of software engineering. This study deals with the early treatment of crosscutting concerns combined with classical engineering requirements processes in which quality requirements are relevant. In spite of the increasing int...
![Fig.1. Categorización de los requisitos en ISO/IEC 25030 [9].](profile/Isi-Castillo/publication/271827636/figure/fig2/AS:667620739121159@1536184596820/Categorizacion-de-los-requisitos-en-ISO-IEC-25030-9_Q320.jpg)
Aspect Oriented Software Development (AOSD), based on Aspect Oriented Programming, is part of the post-object paradigm of software engineering. The early treatment of non functional requirements elicitation and specification, combining quality properties and crosscutting concerns at classical requirements engineering, are open research subjects. In...
Aspect oriented software development (AOSD), based on aspect oriented programming (AOP), is part of the post-object paradigm of software engineering. This study deals with the early treatment of crosscutting concerns combined with classical engineering requirements processes in which quality requirements are relevant. In spite of the increasing int...
Citations
... Improvements from previous ISOs, such as usability, further emphasize the issue of Accessibility, and there are additional quality attributes, efficiency, freedom from risk, and context scope, as well as defining lower levels [3]. An essential aspect of the software is functionality; the estimated value of the software agreed upon by the end-user and the development team must be expressed in a certain amount, one of which is in terms of functional size measurement (FSM) [4]. Fungsionalitas adalah fungsi sistem utama atau layanan yang disediakan oleh komponen perangkat lunak [5]. ...
... One element is very important from the other elements 2, 4,6,8 The value between the values above Calculating matrix normalization. ...
The quality model used in this paper is ISO 25010. Functional Suitability, Performance Efficiency, and Reliability are the characteristics to be used. The case study used is the ITS Academic Information System, and the method used for the basis of calculation is the AHP (Analytical Hierarchy Process) method. The initial stage is to make a list of questionnaire questions, which are then filled out by three stakeholders: experts, students, and developers. With the AHP method, experts will analyze the questionnaire results to determine the required weight. This weight is used to calculate the quality of the software. There are two types of software measurements: student questionnaires and developer questionnaires. These two questionnaires become data input. Automatic measurements are carried out on Time Behavior aspects, namely Response Time Testing. In the automatic measurement stage, the URL to be tested by the tester is used as data input. From this automatic measurement, we experimented with the response time of the destination URL to respond to requests and conversion results on a scale of one hundred. The final value of these two types of measurements will be used in several equations to get the final value of the quality of the software. The study results are in the form of automatic measuring instruments of software quality. The measurement results can be used as feedback in making improvements so that the quality value increases when measured. Regarding Functional Suitability, the ITS Academic Information System has provided features according to user needs. In the aspect of Performance Efficiency, the ITS Academic Information System can provide performance and performance according to user needs. Meanwhile, regarding reliability, the ITS Academic Information System can carry out a function under certain conditions and times
... Especially, NFR, it can be concerned as aspect of the system. According to [8], this work focuses on integrating Aspect Oriented Software Development (AOSD) concepts, classic requirements engineering notions, and the new standard ISO/IEC25030 on software quality requirements. The main result of this study is the REASQ (REquirements, Aspects and Software Quality) conceptual model, expressed in UML. ...
... 52 VI RESULTADOS El contenido de este capítulo es el resultado de aplicar la metodología seleccionada y de comparar y analizar cómo integrar los principios del Pensamiento Complejo con los objetivos de las etapas de la Ingeniería de Requisitos. A partir del estado del arte y el marco teórico se tomaron algunos autores representativos de la Complejidad (Nicolescu, 1996(Nicolescu, , 2006(Nicolescu, , 2008Edmonds, 1999;Benbya y McKelvey, 2006;Douglas y Kuras, 2006;Batorowicz y Shepherd, 2008;Morin, 2008;Douglas, 2009;Hofkirchner, 2009;Cooke, 2011;Jörg, 2011;Lemberger y Morel, 2012;Maadawy y Salah, 2012;Mahaux y Canon, 2012), del Pensamiento Complejo (Checkland, 1981Morin, 1994;Gibbons y Nowotny, 2002;Häberli y Thompson, 2002;Häberli et al., 2001;Lawrence y Després, 2004;Hunsinger, 2005;Moreira, Rashid y Arajo, 2005;Tate et al., 2006;Hass, 2009), de la Ingeniería de Requisitos (Boehm et al., 1978;Pohl, 1992Pohl, , 1994Al-Rawas y Easterbrook, 1996;Cardoso, 1998;Buglione y Abran, 1999;Annoni, et al. 2006;Camp, 2006;Carew, 2006;Castillo et al., 2010;Dick y Jones, 2012;Serna y Serna, 2015), y de la Gestión del Conocimiento (Loucopoulos y Champion, 1989;Guindon, 1989;Ramesh, 1993;Davenport y Prusak, 1998;Brown y Duguid, 1998;Guindon, 1990;Cysneiros et al., 2005;Caseau, Krob y Peyronnet, 2007;Serna, 2015;). Luego, y sin perder de vista el objetivo de mejorar la fiabilidad del software, se hizo un análisis de sus aportes para encontrar los principios que se podrían integrar y complementar para diseñar el modelo buscado. ...
En este libro se identifica la problemática de la fiabilidad del software y se presenta un método para gestionar la Ingeniería de Requisitos dividido en etapas, al que se incorpora los principios de la Transdisciplinariedad y la Multidimensionalidad del Pensamiento Complejo, para estructurar una propuesta inter-relacional lógica, orientada a gestionar esta fase del desarrollo de software. Se trata de una innovación a la forma como se lleva a cabo esta fase del ciclo de vida, con el objetivo de ayudar a mejorar la fiabilidad y seguridad del producto final. Cada uno de estos principios se analiza desde los aportes de diversos autores y se incorpora las posibilidades de conjugación a lo establecido para la Ingeniería de Requisitos. De esta manera se integran a las etapas del método de forma complementaria a los objetivos que cada una busca en la gestión de los requisitos del sistema.
... For two points of view -external quality and internal quality -a quality model was proposed in the ISO 9126 standard, consisting of 6 characteristics and 27 subcharacteristics and shown schematically in Fig. 4 . Fig. 4. External and Internal Quality ModelISO/IEC 91260-1 [54] According to [55], having a common goal, verification and validation differ in the sources of properties, rules and restrictions that are checked in their course, the violation of which is considered an error. ...
... Fig. 6. In Use Quality Model ISO/IEC 91260-1 [54] The validation of blockchain systems should take into account the characteristics that are indicated in this model. Validation methods, as mentioned earlier, are difficult to formalize. ...
... The PMS testing should be conducted earlier before the PMS is really applied in a project. The testing must meet the PMS functionality characteristics, which one of them is characteristic accuracy [5]. ...
This research explains the relationship between the end user requirement and accuracy of PMS (Project Management Software). The research aims are to analyze the PMS accuracy and measuring the probability of PMS accuracy in achieving ±1% of the end user requirement. The bias statistical method will be used to prove the PMS accuracy that based on the hypothesis testing. The result indicates the PMS is still accurate to be implemented in Aceh-Indonesia area projects that using the SNI (National Indonesia Standard as current method) with the accuracy index of ±7.5%. The achievement probability of reaching the end user requirement is still low of ±21.77%. In case of the PMS, the low achievement of the end user requirement is not only caused by the low accuracy of the PMS but also caused by the amount of variability error, which is influenced by the amount of variation of the project activity. In this study, we confirm that it is necessary to reconcile both conditions between the PMS accuracy and the end user requirements.
... The case study proposed is based on a simplified version of an online toy store (an e-commerce web-based application). This case is introduced in previous study (Castillo, Losavio, Matteo, & Boegh, 2010) with aim to obtain a common terminology to develop models associated with requirements, aspects, and quality of a software product. ...
... 7.2 | Functional requirements and quality goals Castillo et al. (2010) identifies the main functional concerns and related quality goals of the online toy store from the case study description. Their work also defines specific quality requirements related with each quality goal identified. ...
Pressman's (2010) definition of software quality is the conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software. The achievement of quality is a complex activity that is related with the process quality and product quality. However, still, it is not clear how product quality should apply in the development process. Frequently, the development team does not know what characteristics influence a specific entity and how these characteristics compose the quality of the product. This lack of knowledge reflects the need to define some document that serve as a valid quality specification that should be evaluated along the development process. This contribution addresses this need by introducing an ontology for document a quality scheme based on the product quality model of ISO/IEC 25010. The proposal follows this model with aims to clarify the properties that are normally present in a product and its meaning. The ontology incorporates the metric concept to represent the way in which quality should be measure. The ontology was implemented using Protégé, and it was evaluated using a set of metrics that estimate the required structural characteristics.
... In addition to the AO quality model by 13 Kumar et al., 14 Castillo et al. presented another quality model for AO software. Author has taken common framework related to UML model and named as; REASQ (Requirements, Aspects and Software Quality) model. ...
This paper presents a unique Aspect Oriented (AO) software quality model i.e. Proposed Aspect Oriented Software Quality Model (PAOSQMO) using important quality characteristics and their respective sub-characteristics. Security is exposed as a new characteristic along with its set of sub-characteristics by proposed quality model. PAOSQMO has derived Sub-characteristics for security as confidentiality, integrity, accountability, authenticity and non-repudiation. In order to validate the proposed model, we did the empirical analysis. Total fifty six participants from software companies, academics and research labs have been participated during our survey conducted to identify the missing attributes in AO software. A survey form was given in order to conduct the survey. We have identified different attributes and considered the most frequent attributes for further analysis. Firstly, we have classified the collected attributes from survey into characteristics and sub-characteristics using experts responses. Thereafter, pair wise relative weights for each characteristic and their respective sub-characteristics are taken. Finally, we have applied one of the MCDM approach i.e. Analytical Hierarchical Process (AHP) on PAOSQMO for empirical evaluation of quality model by considering three Aspect Oriented Projects.
... (e.g. [2], [3], [4]). The conceptual domain modeling in the business environment has been represented by UML, which is interested with providing a representation of things and objects" that exist and processes, activities and procedures that arise in a business environment. ...
Our research comes to supplement the previous researches that have represented business process modeling languages. The representation performed in this paper is focuses on two most widely used iterative method based on Use-Case scenarios for purchase processes: static structure and dynamic views. To clarify how to use this method we applied it in purchase process by some steps. Use-Cases should be kept as simple as possible. Occasionally, however, we will encounter irreducible complexity and will need to formulate complex Use-Cases. Rather than trying to capture this complexity with lots of branching and alternative flows, it is easier, and less error prone, to model the main flows through this branching network as separate scenarios. The results presented in this paper as some models in UML. In addition, these models that facilitates the analysis phase of purchase process and make processes clear from perspective of analysts, managers, employers and also users. On the other hand, the aim in this paper will make the design phase easier and explained as a future work to complete the design phase of the purchase operations in implementation and testing phases.
... In this model Complexity, Reusability, Modularity and Code-Reducibility are included in diverse characteristics of ISO/IEC 9126 Model. Castillo et al. proposed a conceptual quality model to elucidate the AOSD evolving technologies like aspect, composition concern, and quality requirement for software system [13]. REASQ Model is another name of this model which integrates ISO/IEC 9126 Model and ISO/IEC 25030 model in addition to articulated in UML. ...
Software reusability is very important and crucial attribute to evaluate the system software. Due to incremental growth of software development, the software reusability comes under attention of many researcher and practitioner. It is pretty easier to reuse the software than developing the new software. Software reusability reduces the development time, cost and effort of software product. Software reusability define the depth to which a module can be reused again with very little or no modification. However the prediction of this quality attribute is cumbersome process. Aspect oriented software development is new approach that introduce the concerns to overcome the issues with modular programming and object oriented programming. However many researcher worked on accessing the software reusability on object oriented system but the software reusability of aspect oriented system is not completely explored. This paper explores the various metric that affects the reusability of aspect oriented software and estimate it using fuzzy logic approach.
... They are highlighted in gray in Table III. Around half of the selected studies were validated by case studies, 12% by experiments and only one survey Case study [28], [33], [38], [49], [54], [56], [61]- [64], [69]- [71], [74] [35]- [37], [46]- [48], [52], [57], [58], [67], [72], [ Theory - [29]- [31], [41], [44], [55], [59], [66], [68] 9 ...
... MEG was evaluated in two pilot experiments involving two stakeholders each. Castillo et al. [58] propose the REASQ (REquirements, Aspects and Software Quality) conceptual model, expressed in UML. Sen and Barach [57] present a fuzzy quality function deployment approach for determining which of the non-functional requirements reported by earlier studies are important to a company's software selection decision based on and integrated with its functional requirements. ...
... The inputs of the analyzer are a requirements list and a catalog of QR derived from ISO 9126. [35], [48], [58], [68]. 29% of the selected studies discuss documentation, 73% of them are requirements documentations. ...
Software quality requirements (SQR) play a central role in software quality (SQ) success. The importance of mastering SQR can be seen as obvious, however, when it comes to customer satisfaction, end-users are often dissatisfied with SQ. In this paper, a systematic mapping study aims to summarize SQR research by answering nine mapping questions. In total, 51 articles were selected and classified according to multiple criteria: publication source, publication year, research type, research approach, contribution type of SQR literature, requirements engineering activity, well-known SQ model, software artifact and SQR type. The results show an increased interest in SQR research in recent years and reveal that conferences are the main SQR publication target. Most SQR research has used case studies. The dominant contribution type of SQR research is method while specification is the main requirements engineering activity identified. SQ models need to be more used for SQR identification. Design module and requirements documentation are the principal artifacts reported in SQR literature. External and internal SQR were the main SQR types addressed in literature. Identifying empirical solutions to address SQR is a promising research direction for researchers.
