Дисертації з теми "SOFTWARE QUALITY ATTRIBUTE"
Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: SOFTWARE QUALITY ATTRIBUTE.
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-35 дисертацій для дослідження на тему "SOFTWARE QUALITY ATTRIBUTE".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте дисертації для різних дисциплін та оформлюйте правильно вашу бібліографію.
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: 2010Reú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
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.
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
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.
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.
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.
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.
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.
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.
Повний текст джерела
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/.
Повний текст джерела
11
Mårtensson, Frans. "Software Architecture Quality Evaluation : Approaches in an Industrial Context." Licentiate thesis, Karlskrona : Blekinge Institute of Technology, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00313.
Повний текст джерелаАнотація:
Software architecture has been identified as an increasingly important part of software development. The software architecture helps the developer of a software system to define the internal structure of the system. Several methods for evaluating software architectures have been proposed in order to assist the developer in creating a software architecture that will have a potential to fulfil the requirements on the system. Many of the evaluation methods focus on evaluation of a single quality attribute. However, in an industrial system there are normally requirements on several quality aspects of the system. Therefore, an architecture evaluation method that addresses multiple quality attributes, e.g., performance, maintainability, testability, and portability, would be more beneficial. This thesis presents research towards a method for evaluation of multiple quality attributes using one software architecture evaluation method. A prototype-based evaluation method is proposed that enables evaluation of multiple quality attributes using components of a system and an approximation of its intended runtime environment. The method is applied in an industrial case study where communication components in a distributed realtime system are evaluated. The evaluation addresses performance, maintainability, and portability for three alternative components using a single set of software architecture models and a prototype framework. The prototype framework enables the evaluation of different components and component configurations in the software architecture while collecting data in an objective way. Finally, this thesis presents initial work towards incorporating evaluation of testability into the method. This is done through an investigation of how testability is interpreted by different organizational roles in a software developing organization and which measures of source code that they consider affecting testability.
12
Henningsson, Kennet. "Trade-offs and Conflicts Between Quality Attributes." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5215.
Повний текст джерелаАнотація:
It is next to impossible to let a day go by without coming into contact with a computer system in some way, either by direct usage, or making a telephone call that is directed by computer systems. Due to the importance of computer systems we are all concerned with their quality, directly or indirectly, a malfunctioning system will disturb our lives in more or less drastic ways. Each stakeholder promotes his qualities and priorities for the system, and this will eventually lead to conflict, depending on relations between qualities. There is no simple solution to the problem of relating and conflicting quality attributes. But by making an informed decision it is possible to soften the effects of the trade-offs and gain a higher level of total software quality. The way to make an informed decision is to have knowledge about the relations between quality attributes along with insights of the consequences of the decision. This report gives a short introduction to the problem, and surveys both the relations stated within academia, and industry. The intention is to explore the knowledge present within academia and collect and present the established relations found by researchers. Further this report presents a survey carried out at companies working in different areas with software engineering, to show which relations that are visible to industry and how they are handling the relations between quality attributes. This gathered knowledge intends to support the ambition towards higher quality in software engineering.
13
Dorsey, Edward Vernon. "The automated assessment of computer software documentation quality using the objectives/principles/attributes framework." Thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-03302010-020606/.
Повний текст джерела
14
Cooke, Alan. "X-Tools: A Case Study in Building World Class Software." International Foundation for Telemetering, 2010. http://hdl.handle.net/10150/605982.
Повний текст джерелаАнотація:
ITC/USA 2010 Conference Proceedings / The Forty-Sixth Annual International Telemetering Conference and Technical Exhibition / October 25-28, 2010 / Town and Country Resort & Convention Center, San Diego, CaliforniaX-Tools is a collection of utilities for validation, translation, editing and report generation designed to enable the Flight Test Instrumentation (FTI) community to quickly adopt the XidML 3.0 meta-data standard. This paper discusses the challenges of developing such software that meets the current and future needs of the FTI community, and meets the increasingly high quality standards expected of modern software. The paper first starts by discussing the needs of the FTI community and the specific functional requirements of software. These include the ability to fit in with legacy systems, the ability to handle many tens of thousands of parameters, support for new networked-based technologies and support for hardware from any vendor. The non-functional requirements of FTI orientated software are also described and it is suggested that the key non-functional requirements include testability, modifiability, extensibility and maintainability. Finally, as a case study, the X-Tools from ACRA CONTROL are presented. The paper discusses their design, and the tactics used to meet the functional and non-functional requirements of the FTI industry. The paper then outlines how the rigorous quality standards were met and describes the specific mechanisms used to verify the quality of the software.
15
Wallnau, Kurt C. "Predictability By Construction : Working the Architecture/Program Seam." Doctoral thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-10150.
Повний текст джерелаАнотація:
Contemporary software engineering practice overemphasizes the distinction of software design from software implementation, and designer (“software architect”) from implementor (“computer programmer”). In this contemporary meme, software architects are concerned with large-grained system structures, quality attributes that arise from these structures (security, availability, performance, etc.) and quality attribute tradeoff to satisfy conflicting stakeholder needs; programmers are concerned with low–level algorithms and data structures, program functionality, and with satisfying architectural intent. However, software is unique in that design and implementation are not cleanly separable. While architect and programmer may have many different design concerns, they also have many complementary and interacting concerns; their respective design practices must be well–integrated. Instead, contemporary architecture and programming practices are diverging. Architects are likely to regard programming as a routine production activity, while programmers are likely to regard architecture as a routine management activity; communication is hindered by a lack of shared vocabulary or appreciation of mutual concerns. Instead of effective integration, a gap has opened in software architecture and programming practice. The research reported here defines the architecture/program seam (“the Seam”), a region of overlap in software architecture and programming practice. The Seam emphasizes design concerns centered on achieving predictable runtime behavior. For a behavior to be predictable it must be described in a theory that must ultimately be consistent with basic theories of computation, and each such theory must have objective evidence to demonstrate that theory observations correspond to system observations. The validity of a theory will likely depend on invariants that can be expressed, and enforced, by means of theory–induced design rules. A system that satisfies the design rules of a theory is then regarded as having behavior that is predictable by construction with respect to that theory. Predictability by construction reduces uncertainty, and hence risk in design, and helps designers explain complex design decisions. The research reported here also defines prediction–enabled component technology (PECT) as a foundation technology to support the Seam, and demonstrates a prototype on industrial problems in electric grid substation control, industrial robot control, and desktop streaming audio. The prototype PECT extends a basic component technology of pure assembly (“Pin”) with theory extension points (“reasoning frameworks”) that are used to achieve predictability by construction. Reasoning frameworks for real–time performance and temporal–logic model checking have been developed, with statistical confidence intervals providing evidence of predictive quality for the former, and code–embeddable proof certificates providing evidence for the latter. Finally, the research reported here defines the Seam itself as inducing a new kind of evolutionary design problem, whose solutions require the integration of programming language theory, design theory, specialized theories of system behavior and deep systems expertise.
16
Buason, Gunnar. "Evaluating the implementation of the monitor synchronization mechanism when implemented using concurrency patterns in C++." Thesis, University of Skövde, Department of Computer Science, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-518.
Повний текст джерелаАнотація:
With the increased use of computers in every-day live, the demand for newer and better software is increasing day by day. This advancement has resulted in that many developers are searching for ways to decrease their development time. One approach is to use design patterns when designing applications. Design pattern are acknowledged solutions to known design problems that can be reused over and over again without ever doing the same thing twice. The most recent advancement of identifying design patterns has been within the domain of concurrent systems.
Design pattern within concurrent systems are of interest in this project because of its young age. Development of concurrent applications has often been compared to constant reinvention of the wheel, because code reuse is very low and solutions to design problems are being rediscovered over and over again. By using design pattern, an attempt is made to avoid that. The question is if design patterns are capable of standing under that load.
This project takes as a case study the problem of protecting a shared resource in a concurrent application, and implements two different solutions to that problem using a special design pattern. These two implementations are then evaluated, with consideration to certain software quality attributes, in a qualitative way.
This project shows how a pattern can be used to solve a common synchronization problem. It discusses the nature of design patterns, what needs to be considered when they are implemented and how a pattern language can affect the implementation.
17
Waqas, Ahmad, and Fawad Kamal. "Modeling Patterns in Software Design." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2350.
Повний текст джерелаАнотація:
Software patterns provide solutions to recurring design problems, provide a way to reason about the quality attributes, and support stakeholders in understanding the system. Naturally, the use of software patterns emerges from the requirements of the software. Use Cases have been a traditional and authentic approach to document these requirements. We propose a way to mine these patterns by sing use cases and advocate their significance in saving resources and time. For this purpose, an open-source system is discussed and four design patterns are mined with the help of use cases elicited from the documentation and literature available for the selected system. Patterns mined in this system are then document in GOF format.Furthermore, the consequences of few patterns on quality attributes are studied and an additional design pattern is proposed to improve the quality of the system.Folkspark Vägan 15:11 ,372 40 Ronneby ,Sweden
18
Wnukiewicz, Karol Kazimierz. "The role of quality requirements in software architecture design." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2253.
Повний текст джерелаАнотація:
An important issue during architectural design is that besides functional requirements, software architecture is influenced greatly by quality requirements [9][2][7], which often are neglected. The earlier quality requirements are considered, the less effort is needed later in the software lifecycle to ensure a sufficient software quality levels. Errors due to lack of their fulfilment are the most expensive and difficult to correct. Therefore, attention to quality requirements is crucial during an architectural design. The problem is not only to gather the system’s quality requirements, but to establish a methodology that helps to deal with them during the software development. Literature has paid some attention to software architecture in the context of quality requirements, but there is still lack of effective solutions in this area. To alleviate the problem, this paper lays out important concepts and notions of quality requirements in a way they can be used to drive design decisions and evaluate the architecture to estimate whether these requirements are fulfilled. Important concepts of software architecture area are presented to indicate how important quality requirements are during the design and what are the consequences of their lack in a software system. Moreover, a quality requirement-oriented design method is proposed as an outcome of the literature survey. This method is a model taking quality requirements into account at first, before the core functionality is placed. Besides the conceptual solution to the identified problems, this paper also suggests a practical method of handling quality requirements during a design. A recommendation framework for choosing the most suitable architectural pattern from a set of quality attributes is also proposed. Since the literature provides insufficient qualitative information about quality requirement issues in terms of software architectures, an empirical research is conducted as means for gathering the required data. Therefore, a systematic approach to support and analyze architectural designs in terms of quality requirements is prepared. Finally, quality requirement-oriented and pattern-based design method is further proposed as a result of investigating patterns as a tool for addressing quality requirements at different abstraction levels of a design. The research is concerned with the analysis of software architectures against one or more desired software qualities that ought to be achieved at the architectural level.http://wnukiewicz.pl kareel@gmail.com
19
Al-Daajeh, Saleh. "Balancing Dependability Quality Attributes for Increased Embedded Systems Dependability." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6158.
Повний текст джерелаАнотація:
Embedded systems are used in many critical applications where a failure can have serious consequences. Therefore, achieving a high level of dependability is an ultimate goal. However, in order to achieve this goal we are in need of understanding the interrelationships between the different dependability quality attributes and other embedded systems’ quality attributes. This research study provides indicators of the relationship between the dependability quality attributes and other quality attributes for embedded systems by identifying the impact of architectural tactics as the candidate solutions to construct dependable embedded systems.
20
Koziolek, Anne [Verfasser]. "Automated Improvement of Software Architecture Models for Performance and Other Quality Attributes / Anne Koziolek." Karlsruhe : KIT Scientific Publishing, 2014. http://www.ksp.kit.edu.
Повний текст джерела
21
Nitesh, Varma Rudraraju Nitesh, and Boyanapally Varun Varun. "Data Quality Model for Machine Learning." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18498.
Повний текст джерелаАнотація:
Context: - Machine learning is a part of artificial intelligence, this area is now continuously growing day by day. Most internet related services such as Social media service, Email Spam, E-commerce sites, Search engines are now using machine learning. The Quality of machine learning output relies on the input data, so the input data is crucial for machine learning and good quality of input data can give a better outcome to the machine learning system. In order to achieve quality data, a data scientist can use a data quality model on data of machine learning. Data quality model can help data scientists to monitor and control the input data of machine learning. But there is no considerable amount of research done on data quality attributes and data quality model for machine learning. Objectives: - The primary objectives of this paper are to find and understand the state-of-art and state-of-practice on data quality attributes for machine learning, and to develop a data quality model for machine learning in collaboration with data scientists. Methods: - This paper mainly consists of two studies: - 1) Conducted a literature review in the different database in order to identify literature on data quality attributes and data quality model for machine learning. 2) An in-depth interview study was conducted to allow a better understanding and verifying of data quality attributes that we identified from our literature review study, this process is carried out with the collaboration of data scientists from multiple locations. Totally of 15 interviews were performed and based on the results we proposed a data quality model based on these interviewees perspective. Result: - We identified 16 data quality attributes as important from our study which is based on the perspective of experienced data scientists who were interviewed in this study. With these selected data quality attributes, we proposed a data quality model with which quality of data for machine learning can be monitored and improved by data scientists, and effects of these data quality attributes on machine learning have also been stated. Conclusion: - This study signifies the importance of quality of data, for which we proposed a data quality model for machine learning based on the industrial experiences of a data scientist. This research gap is a benefit to all machine learning practitioners and data scientists who intended to identify quality data for machine learning. In order to prove that data quality attributes in the data quality model are important, a further experiment can be conducted, which is proposed in future work.
22
Guceglioglu, A. selcuk. "A Pre-enactment Model For Measuring Process Quality." Phd thesis, METU, 2006. http://etd.lib.metu.edu.tr/upload/12607425/index.pdf.
Повний текст джерелаАнотація:
Most of the process measurement studies are related with time and cost based
models. Although quality is the other conventional aspect, there are no widely used
models for measuring the process quality in the literature. In order to provide
complementary information about the quality, a process quality measurement model
has been chosen to be developed and the studies about process characteristics have
been searched in the scope of the thesis. Moreover, by utilizing the similarities
between process and software, the studies in software quality have been investigated.
In the light of the researches, a model is built on the basis of ISO/IEC 9126 Software
Product Quality Model. Some of the quality attributes are redefined in the model
according to the process characteristics. In addition, new attributes unique only to the
process are developed. A case study is performed and its results discussed from
different perspectives of applicability, understandability and suitability.
23
Haghverdian, Pol, and Martin Olsson. "Identification of cloud service use-cases and quality aspects:end-user perspective : Learnability, Operability and Security quality attributes and their corresponding use cases." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-12753.
Повний текст джерелаАнотація:
Context. With the entry of smart-phones on the market in the beginningof 2007, the integration of an mp3 player, camera and gps into an all in onedevice. As the integration was realized, creating and storing own contentbecame easier. Therefore the need of more storage became a problem as thesmart-phones were limited in capacity. The 3G network was on the rise andthe cloud solutions could help to contribute to the storage problems usersstarted to have. Objectives. In this study we will evaluate what can be done with use casesin terms of quality attributes, seeing it from a users perspective by havingusers rank use cases for cloud services. With further investigation we willmake a contribution of what the differences between public and personalclouds are. Methods. Use-cases were found by the conducted empirical study andwere based on a Systematic mapping review. In this review, a number ofarticle sources are used, including Google search, Bth summon and Googlescholar. Studies were selected after reading the articles and checked if thepapers matched our defined inclusion criteria. We also designed a surveywith variable amount of questions depending on what the participant wouldanswer. The questions were featured in terms of functionality interpretedfrom the use-cases found in the SLM. Results. Through our SLM we found six different use-cases which were Recovery, Collaborative working, Password protection, Backup, Version tracking and Media streaming. The identified quality attributes gave two or moremappings to their corresponding use-case. As for the comparison betweendifferent clouds, only two out of six use-cases where implemented for the Personal cloud. Conclusions. This gave us the conclusion that the vendors have beenmostly focusing on the storage part of the Personal cloud, but there are solutions in order to increase the functionalities. Those solutions will probably not fit everyone as it includes open source software, with skills of handling installation and other procedures by the user.
24
Gurses, Ozgur. "Non-functional Variability Management By Complementary Quality Modeling In A Software Product Line." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12612571/index.pdf.
Повний текст джерелаАнотація:
Software product lines provide the opportunity to improve productivity, quality and time-to-market of software-based systems by means of systematic reuse. So as to accomplish systematic software reuse, elicitation of commonality knowledge is to be upheld by the analysis and management of variability knowledge inherent in domain requirements. Considerable effort is devoted to the management of functional variability, often neglecting the impact of quality concerns originating from non-functional requirements. In this thesis, a hybrid approach concentrating on the modeling of quantitative as well as qualitative concerns on quality has been proposed. This approach basically aims to support the domain design
process by modeling non-functional variability. It further aims to support application design process by providing trade-off selection ability among quality concerns to control functional features that belong to the same domain. This
approach is implemented and evaluated on an example domain to reveal its benefits on non-functional variability.
25
Koziolek, Anne [Verfasser], and R. [Akademischer Betreuer] Reussner. "Automated Improvement of Software Architecture Models for Performance and Other Quality Attributes / Anne Koziolek. Betreuer: R. Reussner." Karlsruhe : KIT-Bibliothek, 2011. http://d-nb.info/1017321884/34.
Повний текст джерела
26
Mohsin, Ahmad. "A framework to support the stochastic software architecture modeling and analysis for system of systems." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 2021. https://ro.ecu.edu.au/theses/2472.
Повний текст джерелаАнотація:
Context: A System of Systems (SoS) is a large-scale distributed system that achieves global missions through the collaboration of autonomous Constituent Systems (CSs). Hence, an SoS is a complex, dynamic system whose CSs are not known precisely at design time, and the environment in which it operates is uncertain. The behavior of an SoS is unpredictable due to underlying architectural characteristics such as autonomy and independence. Moreover, unknown conditions and the volatility under which an SoS operates have significant effects on crucial Quality Attributes (QAs) such as performance, reliability, and security. Hence, SoS is a non-deterministic system whose structure and behavior must be modeled and analyses qualitatively and quantitatively to foresee any potential impact on the SoS attributes critical for achieving the missions.
Problem: Software Architecture (SA) plays a vital role in the design and development of complex, software-intensive systems that achieve high quality performance by satisfying both the functionalities and the QAs. In this regard, architecture modelling languages are used to represent SA at design time, producing abstract models that can be used for analysis at run-time. The SA descriptions facilitate the communication among stakeholders to validate the design of SoS during the early stages of the life cycle. However, most of the existing modelling specifications have certain limitations when it comes to representing SoS architectures descriptions because they: (i) are able to describe deterministic behaviors and structures of known single systems only; (ii) do not have the expressive power to specify and reason SoS emergent behavior with the ability to constrain SoS uncertainties; (iii) lack essential capabilities to manage SoS architectural characteristics such as dynamic interactions of CSs and SoS evaluation; and (iv) do not provide essential formal foundations enabling architecture models to be used for architectural analysis at later stages, thereby failing to ensure architectural consistency and correctness between abstract models and implementation models. As a result, SoS architecture models cannot give predictive insights into the systems; therefore, SoS architectural evaluations are insufficient to verify and validate the stochastic nature of SoS and ensure that it conforms to the stated requirements.
Objectives: In order to overcome these issues, this thesis proposes a stochastic SA modelling and analysis framework for SoS. The core contributions of this thesis are: (i) the formulation of Hybrid Stochastic Formalism (HSF) for describing stochastic structures and emergent behaviours using Model-Driven Engineering (MDE), (ii) the specification and reasoning of CSs uncertainties when interacting with architectural elements at design time, (iii) the use of a combination of formal transformation rules and MDE to map formal abstract models to concrete models for performing architecture evaluations, (iv) the use of stochastic model checking as software architecture verification of stochastic SoS architecture models, and (v) the use of Markovian Discrete Events Specifications to validate SoS dynamics as software architecture simulations.
Contributions: The main contributions of this thesis are fourfold. Firstly, it introduces hybrid formalism which is capable of producing stochastic software architecture models as Markov Chains. Secondly, the stochastic models from the abstract architecture are evaluated for the first time both for verification and validation purposes, providing predictive insights into SoS missions and their QAs. Thirdly, SoS dynamics and evolution are analysed by means of abstract models with formal transformation rules that ensure architectural consistency and correctness. Fourthly, predictive architecture analysis offers various insights to stakeholders, including software architects, enabling them to make informed decisions early in the life cycle of SoS design.
Results: A number of case studies of a Fire Monitoring Emergency Response SoS are designed to evaluate the proposed approach. The Fire Monitoring system exhibits all the core properties of an SoS as it is composed of independent CSs and operates in uncertain conditions to achieve global missions in a collaborative manner. The results show that the proposed methodology supports high-quality SoS SA models to (i) manage the stochastic dynamics of SoS dealing with structural and behavioral uncertainties, (ii) minimize operational failures by providing correct and precise architectural descriptions for achieving missions (iii) support evaluations with predictions of SoS functionalities and QAs at design time, and (iv) design software architecture models ensuring high quality.
27
Tibermacine, Chouki. "Contractualisation de l'évolution architecturale de logiciels à base de composants : Une approche pour la préservation de la qualité." Phd thesis, Université de Bretagne Sud, 2006. http://tel.archives-ouvertes.fr/tel-00512361.
Повний текст джерелаАнотація:
De toutes les étapes qui constituent le processus de maintenance, l'étape de compréhension d'une application avant son évolution, et l'étape de vérification de sa progression et de sa non régression aprés évolution sont de loin les plus coûteuses. Dans cette these, je présente une approche qui diminue les coûts associés a ces deux étapes, pour des applications conçues à l'aide de composants. Dans cette approche, les liens unissant les attributs qualité d'une application et les décisions architecturales sont documentés formellement. La définition de ces liens se fait a chaque étape du cycle de vie de l'application. J'ai développé un environnement d'assistance à l'évolution, qui exploite cette documentation, pour d'une part, garantir sa mise a jour et d'autre part, notifier au développeur les effets possibles sur les exigences qualité des changements architecturaux proposés. Cette documentation forme ainsi un contrat dit d'évolution. Il s'agit d'un accord entre l'architecte de l'application et le responsable de son évolution. Le premier doit expliciter ses décisions de conception, sous la forme d'un ensemble de contraintes, afin qu'elles puissent être respectées lors du développement et de l'évolution. Le second doit respecter ce contrat afin de bénéficier d'une garantie de préservation de la qualité initialement requise. Ceci permet, principalement, de réduire les coûts associés aux tests de non-régression sur l'aspect non-fonctionnel. Cette même documentation est utilisée pour tracer toutes les décisions architecturales tout au long du processus de développement d'un logiciel. Il est possible, ainsi, de vérifier, à une étape donnée du processus, la non-altération de toutes les décisions prises dans les étapes en amont. J'ai proposé un outil permettant de transformer vers une représentation unique, puis évaluer, les contraintes définies lors des différentes étapes. Cette traçabilité des décisions a pour objectif de rendre persistants les attributs qualité qui sont à l'origine de ces décisions, à travers toutes les étapes du cycle de vie d'un logiciel.
28
Toresson, Gabriel. "Documenting and Improving the Design of a Large-scale System." Thesis, Linköpings universitet, Programvara och system, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-157733.
Повний текст джерелаАнотація:
As software systems become increasingly larger and more complex, the need to make them easily maintained increases, as large systems are expected to last for many years. It has been estimated that system maintenance is a large part of many IT-departments’ software development costs. In order to design a complex system to be maintainable it is necessary to introduce structure, often as models in the form of a system architecture and a system design. As development of complex large-scale systems progresses over time, the models may need to be reconstructed. Perhaps because development may have diverted from the initial plan, or because changes had to be made during implementation. This thesis presents a reconstructed documentation of a complex large-scale system, as well as suggestions for how to improve the existing design based on identified needs and insufficiencies. The work was performed primarily using a qualitative manual code review approach of the source code, and the proposal was generated iteratively. The proposed design was evaluated and it was concluded that it does address the needs and insufficiencies, and that it can be realistically implemented.
29
Andersson, Jonas. "Enterprise Information Systems Management : An Engineering Perspective Focusing on the Aspects of Time and Modifiability." Doctoral thesis, KTH, Electrical Systems, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-3372.
Повний текст джерела
30
SINGH, PRIYA. "ANALYSING THE EFFECTS OF REFACTORING ON SOFTWARE QUALITY ATTRIBUTES." Thesis, 2018. http://dspace.dtu.ac.in:8080/jspui/handle/repository/16391.
Повний текст джерелаАнотація:
Bad-smell indicates code-design flaws and poor software quality that weaken software
design and inversely affects software development. It also works as a catalyst for bugs
and failures in the software-system. Refactoring methods are used by software
practitioners as corrective actions for bad-smells. Refactoring is not only limited to
removing bad-smells but it does have a strong correlation with quality attributes.
Countless studies are present in the literature that studies the effect of refactoring
methods on software quality attributes. It is said to improve certain aspects of quality.
Also, refactoring is a costly activity and the problem relies upon the fact that there are
over seventy refactoring-methods available in literature and multiple refactoring
methods can be used to nullify the effect of a particular bad-smell. So, it becomes very
difficult to apply refactoring on complete source-code and almost impossible if software
size is dramatically large. Thus, there arises a need for prioritizing classes in some way.
This study aims to first provide a systematic literature review on the correlation of
refactoring-methods and bad-smells and their improvement on internal as well as
external quality attributes and second, it comes up with a way to apply refactoring to
only severely affected classes to improve the overall software quality. The systematic
literature review helps software developers in identifying the commonly prevalent bad
smell, their possible refactoring solution and effect of those refactoring methods on
software quality attributes and guide the researchers in conducting future research. In
the end, a framework is proposed that detects a small subset of classes from the entire
v
source-code instantly require refactoring. This prioritization of classes is based on two
factors-severity of the presence of bad-smells and object-oriented characteristics. The
approach is evaluated on eight open-source software-systems written in Java using ten
most common bad-smells and six widely known Chidamber & Kemerer metrics. Both
these factors help in calculating a new metric Quality Depreciation Index Rule (QDIR)
that exposes those classes that are highly affected by bad-smells and demand an
immediate refactoring solution. Results of the empirical study indicate that QDIR is an
effective metric to remove bad-smells in an environment of stringent time constraints
and limited cost, making the maintenance of software-system easier and effective with
enhanced software quality.
31
Wang, Hsiang-Ying, and 王湘楹. "Software Quality Attributes - A Resource-Based Perspective." Thesis, 2011. http://ndltd.ncl.edu.tw/handle/81299303302442938485.
Повний текст джерелаАнотація:
碩士國立中山大學
資訊管理學系研究所
99
Many software development projects were not able to meet their deadlines with expected qualities under budgets. Basically, it was because the stakeholders and the de-velopment team sharing different expectations and misunderstanding the essence of how software was built. In most cases, the budget and resources were allocated according to the Functional Requirements, which described the features about the software. But on the contrary the development teams were striving in making decision about how to mitigate those Non-functional Requirements which were not included in the budget during the development cycle. However, to mitigate the Non-functional Requirements is not without a price, and letting development team impose resources arbitrarily will make software budget estimation more complicated and worse. This research pointed out what Non-functional Requirements should be abides by the international standard ISO 9126, offered a relatively accurate budget estimation framework. The framework showed how the stakeholders and the development team reach the consensus about the software, how to integrate with Cost Accounting to monitor the budget distribution and to implicate how software should be scheduled and estimated the cost for next coming projects.
32
Karve, Sanchit. "Assessing quality attributes of open source software by mining low ceremony evidence." Thesis, 2012. http://hdl.handle.net/1957/33638.
Повний текст джерелаАнотація:
Programmers often have to choose components online for reuse based on software quality. To help with this choice, most component repositories (SourceForge, CodeProject, etc.) provide information such as user ratings and reviews of components. However, the reusability of components is not immediately obvious from
this material. To make things worse, reviews and other material could potentially contradict one another about reusability or any other issue. Moreover, there could be multiple components that claim to perform identical tasks in which case it becomes difficult to identify the most reusable component. This thesis presents the result of two studies aimed at discovering how to use material from a component repository to automatically characterize the reusability of components. It was found that two factors (out of three) were significant predictors of reusability. Additionally, a review summarizer was developed to summarize user reviews and return the overall opinion reflected by the comments.Graduation date: 2013
33
Yeh, Tzu-Sheng, and 葉自盛. "A Study on the Software Design of Quality Control Charts for Attributes." Thesis, 1997. http://ndltd.ncl.edu.tw/handle/05330066025550206163.
Повний текст джерелаАнотація:
碩士國立台灣工業技術學院
管理技術研究所
85
This thesis make research into the quality process control for attributes.The purpose of this study is to build a system analysis frame and develop an application program of attribute control charts system. Because the thesis make research adopt Shewhart norm and Thumb norm to elevate judge right. So the application program of this thesis can quicklycalculate data, analysis control charts and drawing control charts. Then this application program can suggest opinion, revise process and reduce a lot of defective products.
34
Zhang, Guoheng. "Quality attributes modeling in feature models and feature model validation in software product lines." Thesis, 2013. http://hdl.handle.net/1959.13/1036757.
Повний текст джерелаАнотація:
Research Doctorate - Doctor of Philosophy (PhD)In a software product line, a feature model represents the commonalities and variabilities among a family of software systems. Each valid combination of features authorized by a feature model corresponds to a possible product of the software product line. In feature-based product configuration, the desired features are selected from a feature model based on the customers’ requirements, but the selected features must satisfy the selection constraints specified in the feature model. In practice, two problems arise as the major obstacles of using feature models in product configuration. Firstly, a feature model may have errors which must be resolved for the effective product configuration. The feature model validation aims to identify the feature model errors and provide explanations for each identified error. The current validation approaches transform a feature model into a constraint satisfaction problem (CSP) and use solvers to reason on the CSP. However, the use of solvers might take an infeasible amount of time for validating large-scale feature models, as CSP exhibits the exponential complexity and requires a combination of heuristics and combinational search methods. A more efficient feature model validation approach is needed. Another problem is to assess the product quality in feature-based product configuration. In software development, the product quality is mostly handled until the final product is generated and tested. However, if the final product cannot satisfy the customers’ quality requirements, it will be very costly to fix the problems. Therefore, the product quality should be assessed in feature-based product configuration which is considered as the first stage of deriving valid products. To achieve this aim, the quality attributes must be modelled in a feature model. The current quality attributes modelling approaches have several limitations, such as requiring real products which are difficult to obtain or involving onerous human efforts. A systematic quality attributes modelling approach is needed to reduce the efforts involved in domain experts’ judgments. This research aims to address the above problems. First, I developed an efficient validation approach based on the contradictory feature relationships behind the errors. As the contradictory feature relationships were found based on feature relationship propagation, the solvers were not required by this approach. Second, I developed a quality attributes modelling approach which uses domain experts to make judgments and uses analytic hierarchical process to reduce the efforts involved in the judgments. A knowledge database called quality attribute knowledge base is generated to maintain the captured quality knowledge. Finally, I enhanced the feature-based product configuration with the captured quality knowledge. A desired product is configured from a feature model in a quality-aware manner. A prototype tool was developed to implement the concepts of the proposed approaches and a set of empirical experiments were carried out to evaluate the proposed approaches.
35
Aksu, B., Anant R. Paradkar, Matas Marcel de, Ö. Özer, T. Güneri, and Peter York. "A quality by design approach using artificial intelligence techniques to control the critical quality attributes of ramipril tablets manufactured by wet granulation." 2012. http://hdl.handle.net/10454/10109.
Повний текст джерелаАнотація:
NoQuality by design (QbD) is an essential part of the modern approach to pharmaceutical quality. This study was conducted in the framework of a QbD project involving ramipril tablets. Preliminary work included identification of the critical quality attributes (CQAs) and critical process parameters (CPPs) based on the quality target product profiles (QTPPs) using the historical data and risk assessment method failure mode and effect analysis (FMEA). Compendial and in-house specifications were selected as QTPPs for ramipril tablets. CPPs that affected the product and process were used to establish an experimental design. The results thus obtained can be used to facilitate definition of the design space using tools such as design of experiments (DoE), the response surface method (RSM) and artificial neural networks (ANNs). The project was aimed at discovering hidden knowledge associated with the manufacture of ramipril tablets using a range of artificial intelligence-based software, with the intention of establishing a multi-dimensional design space that ensures consistent product quality. At the end of the study, a design space was developed based on the study data and specifications, and a new formulation was optimized. On the basis of this formulation, a new laboratory batch formulation was prepared and tested. It was confirmed that the explored formulation was within the design space.