Готові списки джерел за темами / SOFTWARE QUALITY ATTRIBUTE

Добірка наукової літератури з теми "SOFTWARE QUALITY ATTRIBUTE"

Автор: Grafiati
Опубліковано: 11 вересня 2023

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Зміст

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "SOFTWARE QUALITY ATTRIBUTE".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Статті в журналах з теми "SOFTWARE QUALITY ATTRIBUTE"

1

LEBIGA, MYKYTA, TETIANA HOVORUSHCHENKO, and MARIIA KAPUSTIAN. "NEURAL-NETWORK MODEL OF SOFTWARE QUALITY PREDICTION BASED ON QUALITY ATTRIBUTES." Computer systems and information technologies, no. 1 (April 14, 2022): 69–74. http://dx.doi.org/10.31891/csit-2022-1-9.

Повний текст джерела
Анотація:
The paper proposes a neural-network model of software quality prediction based on quality attributes. The proposedmodel differs from the known models, because it provides considering the importance of each quality attribute and their interactionwithin each software quality characteristic. The artificial neural network (ANN) outputs correspond to the values of software qualitycharacteristics (functional suitability, performance efficiency, usability, reliability, compatibility, security, maintainabi lity, portability).The artificial neural network (ANN) outputs make it possible assessing the total impact of quality attributes on software qualitycharacteristics
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Bachmann, F., L. Bass, M. Klein, and C. Shelton. "Designing software architectures to achieve quality attribute requirements." IEE Proceedings - Software 152, no. 4 (2005): 153. http://dx.doi.org/10.1049/ip-sen:20045037.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Makkar, Priyanka, Sunil Sikka, and Anshu Malhotra. "Optimization of Software Quality Attributes using Evolutionary Algorithm." International Journal of Electrical and Electronics Research 10, no. 2 (June 30, 2022): 131–37. http://dx.doi.org/10.37391/ijeer.100214.

Повний текст джерела
Анотація:
Software quality is a multidimensional concept. Single attribute can’t define the overall quality of the software. Software developer aims to develop software that possesses maximum software quality which depends upon various software quality attributes such as understand ability, flexibility, reusability, effectiveness, extendibility, functionality, and many more. All these software quality attributes are linked with each other and conflicting in nature. Further, these quality attributes depend upon the design properties of the software. During the designing phase of software, developers must optimize the design properties to develop good software quality. To obtain the appropriate value optimization is done. This paper implemented two multi-objective evolutionary algorithms (NSGA-2 and MOEA/D) to optimize software design properties to enhance software quality. While comparing NSGA-2 algorithm with original values it is found that there is a 1.73% improvement in the software quality on the other hand MOEA/D shows a 3.58% improvement in the software quality.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Ozkaya, I. "Making Practical Use of Quality Attribute Information." IEEE Software 25, no. 2 (March 2008): 25–33. http://dx.doi.org/10.1109/ms.2008.39.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Bajpayee, Payel, and Hassan Reza. "Toward Quality Attribute Driven Approach to Software Architectural Design." Journal of Software Engineering and Applications 10, no. 06 (2017): 483–99. http://dx.doi.org/10.4236/jsea.2017.106027.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

KHOSHGOFTAAR, TAGHI M., LOFTON A. BULLARD, and KEHAN GAO. "ATTRIBUTE SELECTION USING ROUGH SETS IN SOFTWARE QUALITY CLASSIFICATION." International Journal of Reliability, Quality and Safety Engineering 16, no. 01 (February 2009): 73–89. http://dx.doi.org/10.1142/s0218539309003307.

Повний текст джерела
Анотація:
Finding techniques to reduce software developmental effort and produce highly reliable software is an extremely vital goal for software developers. One method that has proven quite useful is the application of software metrics-based classification models. Classification models can be constructed to identify faulty components in a software system with high accuracy. Significant research has been dedicated towards developing methods for improving the quality of software metrics-based classification models. It has been shown in several studies that the accuracy of these models improves when irrelevant attributes are identified and eliminated from the training data set. This study presents a rough set theory approach, based on classical set theory, for identifying and eliminating irrelevant attributes from a training data set. Rough set theory is used to find small groups of attributes, determined by the relationships that exist between the objects in a data set, with comparable discernibility as larger sets of attributes. This allows for the development of simpler classification models that are easy for analyst to understand and explain to others. We built case-based reasoning models in order to evaluate their classification performance on the smaller subsets of attributes selected using rough set theory. The empirical studies demonstrated that by applying a rough set approach to find small subsets of attributes we can build case-based reasoning models with an accuracy comparable to, and in some cases better than, a case-based reasoning model built with a complete set of attributes.
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Zhang, Guoheng, Huilin Ye, and Yuqing Lin. "Quality attribute modeling and quality aware product configuration in software product lines." Software Quality Journal 22, no. 3 (March 20, 2013): 365–401. http://dx.doi.org/10.1007/s11219-013-9197-z.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Tao, Hongwei, Yixiang Chen, and Hengyang Wu. "A Reallocation Approach for Software Trustworthiness Based on Trustworthy Attributes." Mathematics 8, no. 1 (December 19, 2019): 14. http://dx.doi.org/10.3390/math8010014.

Повний текст джерела
Анотація:
Software trustworthiness is an important research field in software engineering. In order to appropriately evaluate it, some different measurement approaches have been proposed, which have important guiding significance for improving software trustworthiness. Recently, we have investigated attributes-based approaches. That is, how to maximize trustworthy degree of some software satisfying a given threshold by adjusting every attribute value such that the cost is minimal, i.e., the sum of all attribute values is as small as possible. The work is helpful to improve the software quality under the same cost. This paper continues this work and considers a reallocation approach to dealing with the problem that the threshold and the minimal constraints of every attribute values dynamically increase. In this process, the costs of trustworthiness improvement should be ensured to be minimal. For this purpose, we firstly define a reallocation model by mathematical programming. Then we introduce the notion of growth function. Based on this, a polynomial reallocation algorithm is designed to solve the above reallocation model. Finally, we verify our work on spacecraft softwares and the results show that this work is valid.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Anand, Adarsh, and Gunjan Bansal. "Interpretive structural modelling for attributes of software quality." Journal of Advances in Management Research 14, no. 3 (August 7, 2017): 256–69. http://dx.doi.org/10.1108/jamr-11-2016-0097.

Повний текст джерела
Анотація:
Purpose The “quality” of any product or service defines the agility of the product and its life cycle in dynamic environment. The demand of high “quality” becomes an imperative concern, when “software” is acting as a product or a service. Since the nature of the software is intangible and more complex, therefore the assurance of providing accurate results is anxiety for companies. The overall quality of the software is based upon many individual factors (or attributes) that makes software reliable, inclined and a long-lasting product in the marketplace. But how these factors can influence each other is significant to identify. Therefore, the purpose of this paper is to study the quality aspect of the software and analyse the interrelationship of impactful attributes. Design/methodology/approach The analysis has been done through responses sought from software development teams/clients in India. The questionnaire related to the software quality was administered to the sample population. Interconnection among impactful characteristics has been analysed by using a qualitative technique called interpretive structural modelling (ISM). The driving and dependency of the attributes under consideration has been classified using cross-impact matrix multiplication applied to classification (MICMAC) analysis. The procedure of applying ISM method has been automated and provided it as package “ISM” using R software. Findings In general, it is very complex job to determine the most impactful attribute of software quality. By applying ISM and MICMAC analysis on the set of attributes under consideration, it has been found that “reliability” along with “usability” and “performance” is the most influential attribute of software quality and preferred most. Research limitations/implications Though ISM provides an organized modelling framework yet its results are considered less statistically significant. Therefore, it would be interesting to concatenate the present findings with the findings of any analytical methodology; which gives statistically significant results. Practical implications The present proposal deals with the interpretation of the software quality attributes and their contextual relationship but with more effective and efficient manner. It can help management to understand the complexity of relationship amongst attributes (which are quality attributes here) more accurately and precisely. Since today is an era of automation, the manual part is being substituted so as to reduce the labour cost, improve safety, security and product quality to increase production. This study is, therefore, an effort and a helping hand in making the hassle free calculations for obtaining intermediate matrices and doing eventual calculations. Social implications n numbers of parameters can be selected to analyse the interrelationship of any project/study. Eradication human errors in applying transitivity law or applying any other operation in solving problem. The package created here can save precious time of users. Provides well-formatted and readable excel output files that make interpretation easier. Originality/value Software is one such product/service which plays a significant role in this high-technological world, where each and every firm try their best to be on the top of the list of consumers’ preference. For this purpose, companies reduce manual efforts by converting it into qualitative software that provides deliverables in a systematic manner. Therefore, it becomes imperative to study various interrelated quality attributes of the software. On the similar platform, ISM is a widely used technique and just to provide a helping hand in quantification of the qualitative attributes this paper facilitates the readers with algorithm developed using R software.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Guana, Victor, and Dario Correal. "Improving software product line configuration: A quality attribute-driven approach." Information and Software Technology 55, no. 3 (March 2013): 541–62. http://dx.doi.org/10.1016/j.infsof.2012.09.007.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Більше джерел

Дисертації з теми "SOFTWARE QUALITY ATTRIBUTE"

1

Cavalcanti, Ricardo de Oliveira. "Extending the riple-design process with quality attribute variability realization." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2433.

Повний текст джерела
Анотація:
Made available in DSpace on 2014-06-12T15:58:11Z (GMT). No. of bitstreams: 2 arquivo3303_1.pdf: 1930482 bytes, checksum: 5203b90b2f2248bb0739907c03b9a717 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010
Reúso de software é uma forma viável de obter ganhos de produtividade e melhoria no timeto- market tão desejados pelas empresas. O reúso não sistemático (Ad hoc) pode ser prejudicial, uma vez que a reutilização de artefatos de baixa qualidade pode diminuir a qualidade dos produtos finais. O reúso sistemático através da adoção de Linhas de Produto de Software (LPS) é uma boa alternativa para alcançar metas de qualidade e de redução de custos. Essa abordagem se tornou uma solução efetiva para gerar vantagem competitiva para as empresas. Arquiteturas de linhas de produto devem se beneficiar das comunalidades entre os produtos e possibilitar a variabilidade entre eles. Ao mesmo tempo, como uma arquitetura de software, precisa atender requisitos de atributos de qualidade. O desafio de atender atributos de qualidade em sistemas únicos (single systems) torna-se ainda mais complicada no contexto de linhas de produto porque a variabilidade pode ocorrer também nos atributos de qualidade. A variabilidade em atributos de qualidade é uma questão complexa. Entretanto, ela tem sido negligenciada ou ignorada pela maioria dos pesquisadores, uma vez que as atenções têm se mantido no alcance da variabilidade funcional. O foco deste trabalho é definir um processo para o design de arquiteturas de linhas de produto de software que possa lidar de forma eficaz com variabilidade em atributos de qualidade. O processo aprimora o RiPLE-Design com atividades e guias para o design com variabilidade de atributos de qualidade. Por fim, um estudo experimental é apresentado com o intuito de caracterizar e avaliar as melhorias propostas ao processo
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Yelleswarapu, Mahesh Chandra. "An Assessment of the Usability Quality Attribute in Open Source Software." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2193.

Повний текст джерела
Анотація:
Usability is one of the important quality attributes. Open source software products are well known for their efficiency and effectiveness. Lack of usability in OSS (Open Source Software) products will result in poor usage of the product. In OSS development there is no usability team, and one could therefore expect that the usability would be low for these products. In order to find out if this was really the case we made a usability evaluation using a questionnaire for four OSS products. The questionnaire was based on a review of existing literature. This questionnaire was presented to 17 people who are working with open source products. This evaluation showed that the overall usability was above average for all the four products. It seems, however, that the lack of a usability team has made the OSS products less easy to use for inexperienced users. Based on the responses to questionnaire and a literature review, a set of guidelines and hints for increasing the usability of OSS products was defined.
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Tigulla, Anil Reddy, and Satya Srinivas Kalidasu. "Evaluating Efficiency Quality Attribute in Open Source Web browsers." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2584.

Повний текст джерела
Анотація:
Context: Now a day’s end users are using different types of computer applications like web browsers, data processing tools like MS office, notepad etc., to do their day-to-day works. In the real world scenario, the usage of Open Source Software (OSS) products by both industrial people and end users are gradually increasing. The success of any OSS products depends on its quality standards. ‘Efficiency’ is one of the key quality factor, which portray the standards of product and it is observed that this factor is given little importance during its development. Therefore our research context lies within evaluating the efficiency quality attribute in OSS web browsers. Objectives: As discussed earlier the context of this research lies in evaluating the efficiency of OSS web browsers, the initial objective was to identify the available efficiency measures from the current literature and observe which type of measures are suitable for web browsers. Then our next objective is to compute values for the identified efficiency measures by considering a set of predefined web browsers from all the categories. Later we proposed Efficiency Baseline Criteria (EBC) and based on this criterion and experiment results obtained, the efficiency of OSS web browsers had been evaluated. Therefore the main objective of conducting this research is to formulate EBC guidelines, which can be later used by OSS developers to test their web browsers and ensure that all the quality standards are strictly adhered during the development of OSS products. Methods: Initially Literature Review (LR) was conducted in order to identify all the related efficiency quality attributes and also observe the sub-attribute functionalities, that are useful while measuring efficiency values of web browsers. Methods and procedures which are discussed in this LR are used as input for identifying efficiency measures that are related to web browsers. Later an experiment was performed in order to calculate efficiency values for CSS & proprietary set of web browsers (i.e. Case A) and OSS web browsers (i.e. Case B) by using different tools and procedures. Authors themselves had calculated efficiency values for both Case A and Case B web browsers. Based on the results of Case A web browsers, EBC was proposed and finally an statistical analysis (i.e. Mann Whitney U-test) is performed in order to evaluate the hypothesis which was formulated in experiment section. Results: From the LR study, it is observed that efficiency quality attribute is classified into two main categories (i.e. Time Behavior and Resource Utilization). Further under the category of Time behavior a total of 3 attributes were identified (i.e. Response time, Throughput and Turnaround time). From the results of LR, we had also observed the measuring process of each attribute for different web browsers. Later an experiment was performed on two different sets of web browsers (i.e. Case A and Case B web browsers). Based on the LR results, only 3 efficiency attributes (i.e. response time, memory utilization and throughput) were identified which are more suitable to the case of web browsers. These 3 efficiency attributes are further classified into 10 sub-categories. Efficiency values are calculated to both Case A and B for these 10 identified scenarios. Later from Case A results EBC values are generated. Finally hypothesis testing was done by initially performing K-S test and results suggest choosing non-parametric test (i.e. Mann Whitney U-test). Later Mann Whitney U-test was performed for all the scenarios and the normalized Z scores are more than 1.96, further suggested rejecting null hypothesis for all the 10 scenarios. Also EBC values are compared with Case B results and these also suggest us that efficiency standard of OSS web browsers are not equivalent to Case A web browsers. Conclusions: Based on quantitative results, we conclude that efficiency standards of OSS web browsers are not equivalent, when compared to Case A web browsers and the efficiency standards are not adhered during development process. Hence OSS developers should focus on implementing efficiency standards during the development stages itself in order to increase the quality of the end products. The major contribution from the two researchers to this area of research is “Efficiency Baseline Criteria”. The proposed EBC values are useful for OSS developers to test the efficiency standards of their web browser and also help them to analyze their shortcomings. As a result appropriate preventive measures can be planned in advance.
+91 - 9491754620
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Johansson, Per, and Henric Holmberg. "On the Modularity of a System." Thesis, Malmö högskola, Teknik och samhälle, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20183.

Повний текст джерела
Анотація:
Den här uppsatsen behandlar skapandet och designen av en arkitektur över ett system för behandling av depression och andra psykiska sjukdomar via internet, kallat Melencolia. Ett av kraven för detta projekt är att skapa ett system som kan utökas i framtiden. Vi har härlett detta krav till begreppet modularitet och för att skapa en modulär arkitektur för Melencolia har vi undersökt vad begreppet innebär och härlett det till att vara ett kvalitetsdrag hos flera kvalitetsattribut däribland ”maintainability” och ”reusability”. Med hjälp av ”Attribute Driven Design” kan en arkitektur skapas som fokuserar kring en viss typ av kvalitetsattribut. Eftersom modularitet inte är ett kvalitetsattribut utan en kvalitetsegenskap har vi varit tvungna att ändra indata till denna metod, från kvalitetsattribut till kvalitetsegenskap. Vidare har vi härlett och lagt fram en ny metod för att mäta kvalitetsegenskaper i en mjukvaruarkikektur.Slutligen har vi använt vår metod för att mäta graden av modularitet i Melencolias arkitektur.
This thesis considers the problem of creating and designing an architecture for a software project that will result in a system for treatment of depression on the Internet. One of the requirements for this project, named by Melencolia, is to create a system which can be extended in the future. From this requirement we have derived the concept of modularity. In order to create a modular architecture we have concluded that modularity is a quality characteristic of multiple quality attributes such as "maintainability" and "reusability".We deploy Attribute-Driven Design (ADD) in this Melencolia project. By doing this, an architecture that is focused around modularity can be created. Since modularity is not a quality attribute, but rather a quality characteristic, we had to change the input to ADD from a quality attribute to a quality characteristic.Furthermore, we derive and propose a new method for quality characteristic evaluation of software architectures.Finally we apply our aforementioned method on the architecture of Melencolia and by doing this we get an indication on how well our proposed architecture satisfies modularity.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Wikander, Daniel. "Exploring the quality attribute and performance implications of using GraphQL in a data-fetching API." Thesis, Malmö universitet, Fakulteten för teknik och samhälle (TS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20867.

Повний текст джерела
Анотація:
The dynamic query language GraphQL is gaining popularity within the field as more and more software architects choose it as their architectural model of choice when designing an API. The dynamic nature of the GraphQL queries provide a different way of thinking about data fetching, focusing more on the experience for the API consumer. The language provides many exciting features for the field, but not much is known about the implications of implementing them. This thesis analyzes the architecture of GraphQL and explores its attributes in order to understand the tradeoffs and performance implications of implementing a GraphQL architecture in a data-fetching API, as opposed to a conventional REST architecture. The results from the architectural analysis suggests that the GraphQL architecture values the usability and supportability attributes higher than its REST counterpart. A performance experiment was performed, testing the internal performance of GraphQL versus REST in a use-case where its dynamic functionality is not utilized (returning the same static response as its REST equivalent). The results indicate that the performance of GraphQL implementations are lower than that of its REST equivalents in use-cases where the dynamic functionality is not utilized.
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Li, Haorui. "Efficiency of hospitals : Evaluation of Cambio COSMIC system." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-1625.

Повний текст джерела
Анотація:

In this modern world, healthcare has becoming a popular word in human life. People pay their attention on their health protection and treatment, but at the same time, they need to bear the high expenditure for their healthcare processing.

It is a serious problem that the government income can not afford the large expense in healthcare industry. Especially in some developing countries, healthcare problem has become the problem for the nation development.

We would like to choose this basic way to solve this problem directly, to provide the channel to improve the efficiency of healthcare system, Cambio COSMIC.

The aim to analysis COSMIC for my case study is to find out the conclusion that how does the architect design the system from the stakeholders requirement to achieve the success of improving the efficiency of healthcare system. And how to measure the success for the system achieving to improve the efficiency of healthcare system is still required to indicate.

Стилі APA, Harvard, Vancouver, ISO та ін.
7

Almari, Hassan. "Software Patterns and Architecture Under Examination Hammer: An Approach to the Consolidation of Interdisciplinary Knowledge." Phd thesis, Canberra, ACT : The Australian National University, 2018. http://hdl.handle.net/1885/154722.

Повний текст джерела
Анотація:
Software engineering is normally perceived, and even defined, based upon applicability of scientific and technical knowledge, in order to provide solutions to different challenges. The bright side of engineering concepts in general, is the continuous process of acquiring knowledge and skills needed to develop and make adjustments to various systems, in respect to helping humankind. An important phase of this process is ”Architecting”, which is the big picture of any intended systems. While good architecture leads to successful systems, bad architecture can result in misfortune. In this thesis, my proposition is to investigate, in depth, both theoretical (academic) and industry domains, regarding the way in which they treat Software Pattern (SP), Software Architecture (SA), and Software Architecture Evaluation (SAE) techniques. I argue that the process of creating, evaluating, and documenting SPs and SA with no common guidelines, standards, and frameworks, will result in unused and conflicted information within their areas, which finally will impact the software engineering field. While the employment of interdisciplinary knowledge (such as SPs, modelling techniques, description languages, evaluation methods, standards, and frameworks), could elevate SA development and validation methodologies, and increase its utilisation within the software engineering community. The goal here is to help build better systems, which could be improved by developing suitable SA, and evaluate its qualities by proper methods and tools, before further development, which should save time as well as money. Therefore, after a long process of analysing the current-state-of-the-art, I have introduced in this thesis novel findings concerning descriptions, relationships, documentation, and utilisation in relation to SA, SAE, and SPs, through employing several investigatory techniques, including comparisons between reliable references, questionnaires, field study, and case study. The investigation of SPs resulted in creating a database as a partial solution, in order to minimise their confusion within the literature, concerning their definitions, categorisations, and relationships with different quality attributes Quality Attribute (QA)s; also, to introduce the information in a proper fashion for users, which includes the required data that supports comparisons between pattern references, and to facilitate their selection processes. The issues, gaps, limitations, inconsistencies, and conflicts within current SA, QAs, and SPs discovered by this study, such as their poor description and the ignorance of them by developers during software development, has led to important recommendations, as well as suggestions for future research. The required information from different sectors (government, academia and industry) regarding SPs, SA, SAE, and modelling languages, has been gathered, and analysed through two surveys and a field study. The strong relationships and influences between the aforementioned areas were introduced and proven by a case study analysis for the Real-time Control System Real-time Control System (RCS) reference architecture, followed by introducing a conceptual paradigm that aimed to improve and generalise the Moreno et al. [2008] performance model. The outcomes from this thesis provide the basis for future work. Also, the information from different interdisciplinary knowledge merged to form new concepts for SA evaluation, which are recommended for future study.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Гаврилюк, Ірина Вікторівна, та Irina Viktorovna Gavrilyuk. "Дослідження методів та засобів комунікації вимог на етап тестування програмного забезпечення". Thesis, Тернопільський національний технічний університет імені Івана Пулюя, 2015. http://elartu.tntu.edu.ua/handle/lib/21464.

Повний текст джерела
Анотація:
Дана робота присвячена дослідженню методів та засобів комунікації вимог на етап тестування програмного забезпечення. Процес тестування програмного забезпечення відіграє дуже важливу роль на всіх етапах життєвого циклу програмного продукту (ПП). Якість програмного забезпечення – характеристика програмного забезпечення, ступінь відповідності ПЗ до вимог. При цьому вимоги можуть трактуватись по-різному, що породжує декілька незалежних визначень терміну. Якість ПЗ – набір властивостей продукту (сервісу або програм), що характеризують його здатність задовольнити встановлені або передбачувані потреби замовника. Поняття якості має різні інтерпретації залежно від конкретної програмної системи і вимог до неї моделей. Розглянуто запропоновані метрики для обчислення значень показників якості. Проаналізувавши методи комунікації вимог якості, для дослідження обрано методи Сааті, Коггера і Ю, простого алгоритму вибірки та QFD. Вхідними даними для знаходження вагових коефіцієнтів якості є оцінки атрибутів, які встановлені незалежними експертами. Для розв’язання задачі багатокритеріальної оптимізації будуються та обчислюються матриці попарних рівнянь. Складність обчислень та кількість ітерацій залежать від кількості встановлених атрибутів та обраного методу. На основі досліджених існуючих методів розроблено алгоритми обчислення вагових коефіцієнтів для характеристик якості, в залежності від значень яких здійснюється трасування вимог. Розроблено програмне забезпечення, яке реалізовує ці алгоритми, і полегшує процес комунікації вимог якості на початкових етапах життєвого циклу програмного забезпечення.
This work is devoted to the study of methods and means of communication requirements at the stage of software testing. The software testing process plays a very important role at all stages of the software product lifecycle (PP). The quality of the software is a software feature, the degree of compliance of the software with requirements. In this case, requirements can be interpreted in different ways, which gives rise to several independent definitions of the term. Software quality - a set of properties of a product (service or software) that characterizes its ability to meet the customer's established or foreseeable needs. The concept of quality has different interpretations depending on the specific software system and the requirements for it models. The proposed metrics for calculating the values ​​of quality indicators are considered. After analyzing the methods of communication of quality requirements, methods for Saati, Kogger and Yu, the simple sampling algorithm and QFD are chosen for the study. Input data for determining weighting quality factors is an assessment of the attributes set by independent experts. To solve the multicriterial optimization problem, matrices of pairwise equations are constructed and calculated. The complexity of the calculations and the number of iterations depends on the number of attributes set and the chosen method. On the basis of the existing existing methods, we developed algorithms for calculating weight coefficients for quality characteristics, depending on the values ​​of which trace requirements are performed. The software that implements these algorithms is developed and facilitates the process of communicating quality requirements at the initial stages of the software lifecycle.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Larsson, Magnus. "Predicting Quality Attributes in Component-based Software Systems." Doctoral thesis, Västerås : Mälardalen University, 2004. http://www.mrtc.mdh.se/publications/0696.pdf.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Bundy, Gary Neal. "Assessing software quality in Ada based products with the objectives, principles, attributes framework." Thesis, This resource online, 1990. http://scholar.lib.vt.edu/theses/available/etd-06112009-063410/.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Більше джерел

Книги з теми "SOFTWARE QUALITY ATTRIBUTE"

1

Attributes Of Quality Scenarios/Scenario Sets Used In Software Requirements Elicitation. Storming Media, 1997.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Частини книг з теми "SOFTWARE QUALITY ATTRIBUTE"

1

Khalid, Lina. "Achieving Quality Attribute." In Software Architecture for Business, 51–75. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-13632-1_4.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Bass, Len, Mark Klein, and Felix Bachmann. "Quality Attribute Design Primitives and the Attribute Driven Design Method." In Software Product-Family Engineering, 169–86. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-47833-7_17.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Purhonen, Anu. "Quality Attribute Taxonomies for DSP Software Architecture Design." In Software Product-Family Engineering, 238–47. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-47833-7_21.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Diaz-Pace, J. Andres, Rebekka Wohlrab, and David Garlan. "Supporting the Exploration of Quality Attribute Tradeoffs in Large Design Spaces." In Software Architecture, 3–19. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-42592-9_1.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Shah, Unnati, Sankita Patel, and Devesh Jinwala. "A Semi-automated Approach to Generate an Adaptive Quality Attribute Relationship Matrix." In Requirements Engineering: Foundation for Software Quality, 239–56. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-44429-7_17.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Diaz-Pace, Andres, Hyunwoo Kim, Len Bass, Phil Bianco, and Felix Bachmann. "Integrating Quality-Attribute Reasoning Frameworks in the ArchE Design Assistant." In Quality of Software Architectures. Models and Architectures, 171–88. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-87879-7_11.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

d’Aloisio, Giordano, Antinisca Di Marco, and Giovanni Stilo. "Democratizing Quality-Based Machine Learning Development through Extended Feature Models." In Fundamental Approaches to Software Engineering, 88–110. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-30826-0_5.

Повний текст джерела
Анотація:
AbstractML systems have become an essential tool for experts of many domains, data scientists and researchers, allowing them to find answers to many complex business questions starting from raw datasets. Nevertheless, the development of ML systems able to satisfy the stakeholders’ needs requires an appropriate amount of knowledge about the ML domain. Over the years, several solutions have been proposed to automate the development of ML systems. However, an approach taking into account the new quality concerns needed by ML systems (like fairness, interpretability, privacy, and others) is still missing.In this paper, we propose a new engineering approach for the quality-based development of ML systems by realizing a workflow formalized as a Software Product Line through Extended Feature Models to generate an ML System satisfying the required quality constraints. The proposed approach leverages an experimental environment that applies all the settings to enhance a given Quality Attribute, and selects the best one. The experimental environment is general and can be used for future quality methods’ evaluations. Finally, we demonstrate the usefulness of our approach in the context of multi-class classification problem and fairness quality attribute.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Medellin, John M., and Mitchell A. Thornton. "A Discussion on Blockchain Software Quality Attribute Design and Tradeoffs." In Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, 19–28. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-23943-5_2.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Tawfik, Sherif M., and Marwa M. Abd-Elghany. "Investigating Software Requirements Through Developed Questionnaires To Satisfy The Desired Quality Systems (Security Attribute Example)." In Advanced Techniques in Computing Sciences and Software Engineering, 245–50. Dordrecht: Springer Netherlands, 2009. http://dx.doi.org/10.1007/978-90-481-3660-5_41.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Su, Jian, Lu Han, Yue Li, Shufen Liu, Zhilin Yao, and Tie Bao. "Research on Building and Analysis for Attribute Model in Quality Evaluation of Domain Software." In Human Centered Computing, 752–58. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-31854-7_74.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "SOFTWARE QUALITY ATTRIBUTE"

1

Allen, Claudine, and Ilenius Ildephonce. "Communicability - A Software Quality Attribute Proposal." In SoutheastCon 2023. IEEE, 2023. http://dx.doi.org/10.1109/southeastcon51012.2023.10115145.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

"MODELING QUALITY ATTRIBUTE VARIABILITY." In 3rd International Conference on Evaluation of Novel Approaches to Software Engineering. SciTePress - Science and and Technology Publications, 2008. http://dx.doi.org/10.5220/0001759801690176.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Rago, Alejandro, Santiago Vidal, J. Andres Diaz-Pace, Sebastian Frank, and André van Hoorn. "Distributed quality-attribute optimization of software architectures." In the 11th Brazilian Symposium. New York, New York, USA: ACM Press, 2017. http://dx.doi.org/10.1145/3132498.3132509.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Jeon, Sanghoon, Myungjin Han, Eunseok Lee, and Keun Lee. "Quality Attribute Driven Agile Development." In 2011 9th International Conference on Software Engineering Research, Management and Applications (SERA). IEEE, 2011. http://dx.doi.org/10.1109/sera.2011.24.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Svahnberg, M., and K. Henningsson. "Consolidating different views of quality attribute relationships." In 2009 ICSE Workshop on Software Quality (WoSQ 2009). IEEE, 2009. http://dx.doi.org/10.1109/wosq.2009.5071556.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Wahler, Michael, Raphael Eidenbenz, Aurelien Monot, Manuel Oriol, and Thanikesavan Sivanthi. "Quality Attribute Trade-Offs in Industrial Software Systems." In 2017 IEEE International Conference on Software Architecture Workshops (ICSAW). IEEE, 2017. http://dx.doi.org/10.1109/icsaw.2017.10.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Stormer, Christoph. "Software Quality Attribute Analysis by Architecture Reconstruction (SQUA3RE)." In 11th European Conference on Software Maintenance and Reengineering (CSMR'07). IEEE, 2007. http://dx.doi.org/10.1109/csmr.2007.43.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Boehm, Barry. "Architecture-Based Quality Attribute Synergies and Conflicts." In 2015 IEEE/ACM 2nd International Workshop on Software Architecture and Metrics (SAM). IEEE, 2015. http://dx.doi.org/10.1109/sam.2015.18.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Etxeberria, Leire, and Goiuria Sagardui. "Evaluation of Quality Attribute Variability in Software Product Families." In 2008 15th Annual IEEE International Conference on Engineering of Computer Based Systems (ECBS). IEEE, 2008. http://dx.doi.org/10.1109/ecbs.2008.14.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Ratzinger, Jacek, Harald Gall, and Martin Pinzger. "Quality Assessment Based on Attribute Series of Software Evolution." In 14th Working Conference on Reverse Engineering (WCRE 2007). IEEE, 2007. http://dx.doi.org/10.1109/wcre.2007.39.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Звіти організацій з теми "SOFTWARE QUALITY ATTRIBUTE"

1

Bowen, T. P., G. B. Wigle, and J. T. Tsai. Specification of Software Quality Attributes. Volume 2. Software Quality Specification Guidebook. Fort Belvoir, VA: Defense Technical Information Center, February 1985. http://dx.doi.org/10.21236/ada153989.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Bowen, T. P., G. B. Wigle, and J. T. Tsai. Specification of Software Quality Attributes. Volume 1. Final Report. Fort Belvoir, VA: Defense Technical Information Center, February 1985. http://dx.doi.org/10.21236/ada153988.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Barbacci, Mario R., Mark H. Klein, and Charles B. Weinstock. Principles for Evaluating the Quality Attributes of a Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, March 1997. http://dx.doi.org/10.21236/ada324233.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Також вас можуть зацікавити розширені добірки на тему "SOFTWARE QUALITY ATTRIBUTE" для конкретних типів джерел:
Статті в журналах Дисертації
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

До бібліографії