To see the other types of publications on this topic, follow the link: Maintainability.
Dissertations / Theses on the topic 'Maintainability'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Maintainability.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Nytomt, Fredrik. "Service reliability and maintainability /." Luleå, 2004. http://epubl.luth.se/1402-1757/2004/55.
Full text
2
Styger, Michael Stefan. "Design for maintainability in der Aufzugsindustrie /." Zürich : ETH, 2008. http://e-collection.ethbib.ethz.ch/show?type=diss&nr=18086.
Full text
3
Wake, Steven A. "Predicting maintainability with software quality metrics." Thesis, Virginia Tech, 1988. http://hdl.handle.net/10919/43067.
Full textAbstract:
Maintenance of software makes up a large fraction of the time and money spent in the software life
cycle. By reducing the need for maintenance these costs can also be reduced. Predicting where
maintenance is likely to occur can, help to reduce maintenance by prevention. This thesis details a
study of the use of software quality;metrics to determine high complexity components in a software
system. By the use of a history of maintenance done on a particular system, it is shown that a
predictor equation can be developed to identify components which needed maintenance activities.
This same equation can also be used to determine which components are likely to need maintenance
in the future. Through the use of.these predictions and software metric complexities it should
be possible to reduce the likelihood of a component needing maintenance. This might be accomplished
by reducing the complexity of that component through further decomposition.Master of Science
4
Wan, Husain Wan Mohd Sufian Bin. "Maintainability prediction for aircraft mechanical components utilising aircraft feedback information." Thesis, Cranfield University, 2011. http://dspace.lib.cranfield.ac.uk/handle/1826/7272.
Full textAbstract:
The aim of this research is to propose an alternative approach to determine the
maintainability prediction for aircraft components. In this research, the author looks at
certain areas of the maintainability prediction process where missteps or
misapplications most commonly occur. The first of these is during the early stage of
the Design for Maintainability (DfMt) process. The author discovered the importance
of utilising historical information or feedback information. The second area is during
the maintainability prediction where the maintenance of components is quantified;
here, the author proposes having the maximum target for each individual
maintainability component.
This research attempts to utilise aircraft maintenance historical data and
information (i.e. feedback information systems). Aircraft feedback information
contains various types of information that could be used for future improvement
rather than just the failure elements. Literature shows that feedback information such
as Service Difficulty Reporting System (SDRS) and Air Accidents Investigation Branch,
(AAIB) reports have helped to identify the critical and sensitive components that need
more attention for further improvement.
This research consists of two elements. The first is to identity and analyse
historical data. The second is to identify existing maintainability prediction
methodologies and propose an improved methodology. The 10 years’ data from
Federal Aviation Administration (FAA) SDRS data of all aircraft were collected and
analysed in accordance with the proposed methodology before the processes of
maintainability allocation and prediction were carried out.
The maintainability was predicted to identify the potential task time for each
individual aircraft component. The predicted tasks time in this research has to be in
accordance with industrial real tasks time were possible. One of the identified
solutions is by using maintainability allocation methodology. The existing
maintainability allocation methodology was improved, tested, and validated by using
several case studies. The outcomes were found to be very successful.
Overall, this research has proposed a new methodology for maintainability
prediction by integrating two important elements: historical data information, and
maintainability allocation. The study shows that the aircraft maintenance related
feedback information systems analyses were very useful for deciding maintainabilityeffectiveness; these include planning, organising maintenance and design
improvement. There is no doubt that historical data information has the ability to
contribute an important role in design activities. The results also show that
maintainability is an importance measure that can be used as a guideline for managing
efforts made for the improvement of aircraft components.
5
Lin, Zixin. "Process Reliability, Availability and Maintainability (RAM) Analysis." Thesis, University of Manchester, 2010. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.516356.
Full text
6
Berglund, Dan. "Improving maintainability on modern cross-platform projects." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-96003.
Full textAbstract:
As software systems grow in size they will also grow in complexity. If the increased complexity is not managed the system will be increasingly difficult to maintain. The effect of unmaintainable software is even more distinct when using a agile development process. By increasing the maintainability of the system these problems will be dealt with and the system can be extended with sustained efficiency. This thesis will evaluate the development process of a modern, agile company in order to find changes that will promote increased maintainability. The result is an modified process that will increase the maintainability with the smallest possible overhead for the development organisation. The result is based on earlier studies of development technologies that have proven to increase the maintainability. The implementation of these technologies are adjusted to fit the development team, and some of the technologies that are not suitable for the team are rejected.
7
Marcelino, Luis Filipe Fernandes. "An immersive environment for supporting maintainability assessment." Thesis, University of Salford, 2004. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.413450.
Full text
8
Kadi, Sabry. "Measuring Maintainability and latency of Node.js frameworks." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-22160.
Full textAbstract:
Context: Node.js is an established web framework built using JavaScript. As a result, there are a wide variety of frameworks that have emerged that specialize in different quality attributes and functionalities. Some of which are heavily geared to performance and benchmarking while others might focus on security, availability, robustness, etc. Objectives: The project aims to explore different Node.js server-side frameworks and determine their maintainability using metrics such as Halstead metrics, Maintainability index, source line of code as well as Logical source lines of code. This thesis also explores if there is a correlation between the quality attributes maintainability and performance. Realization: In order to explore the different quality attributes, the thesis relied upon experiments and a literature review. The hierarchical method in this thesis was first to examine their performance, later examine their overall maintainability. Examined is also the impact of comments and how they can affect the results of the maintainability index Results: The results indicate all the selected frameworks have a low-to borderline medium cyclomatic complexity, also a high degree of maintainability using two different 3 metric maintainability index formulas. The latency tests indicate the different frameworks produce similar performance results. Conclusion: Concluded in this thesis is, there seems to be no relationship between both lines of code, logical lines of code, and cyclomatic complexity. There also seems to be no correlation between Halstead volume and the overall maintainability index for both the 3 metric formulas used. There is a slight indication of a relationship between Halstead Effort and Cyclomatic Complexity using one of the 3 metric formulas i.e., as the cyclomatic complexity decreases the overall maintainability (using Halsted’s effort instead of Halstead’s volume) increases.
9
Hoffman, Fredrik. "Architectural software patterns and maintainability: A case study." Thesis, University of Skövde, Department of Computer Science, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-528.
Full textAbstract:
The importance of building maintainable software is being recognized in the community of software development. By developing software that is easy to maintain, the time and resources needed to perform the modifications may be decreased. This will in turn mean economical savings and increased profits.
Architectural software patterns are said to promote the development of maintainable software. The aim of this project was therefore to investigate whether architectural software patterns possess this property or not. A case study was performed where two candidate architectures were compared using a method called Architectural analysis of modifiability. This method uses change scenarios and modification ratios to identify differences between candidate architectures. A system developed at Ericsson Microwave Systems AB was used for the case study.
One of the candidate architectures consisted of two architectural software patterns: the Layers pattern and the Model-View-Controller pattern. The architecture analysis showed that the Layers pattern did promote maintainability whereas the Model-View-Controller pattern did not, from the basis of judgement associated with the method.
10
Häggander, Daniel. "Software design conflicts : maintainability versus performance and availability /." Ronneby : Department of Software Engineering and Computer Science, Blekinge Institute of Technology, 2001. http://www.bth.se/fou/forskinfo.nsf/01f1d3898cbbd490c12568160037fb62/8ee6838b9de1d235c1256ccd004867f9!OpenDocument.
Full text
11
Gill, Simon Adrain. "Application of human factors methodologies to aircraft maintainability." Thesis, University of Nottingham, 2009. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.537824.
Full text
12
Häggander, Daniel. "Software Design Conflicts : Maintainability versus Performance and Availability." Doctoral thesis, Karlskrona : Blekinge Institute of Technology, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00224.
Full textAbstract:
A major goal in software engineering is to reduce the cost of maintaining software systems. Finding design methods which make software more easily maintainable has thus been one of the most prioritized challenges during the past decade. While mainstream software design has concentrated on maintainability, other software disciplines e.g. high-performance computing and high-availability systems, have developed other design methods which primarily support the quality attributes that are more important in their areas. More recently, demands have been made for high performance and high availability in typical mainstream software. At the same time, traditional high-performance and high-availability systems tend to incorporate more advanced business functionality, i.e. different software disciplines have started to converge. The situation is not unproblematic since the software design methods developed for achieving performance and availability may have been developed with a limited influence from maintainability, and vice versa. It is thus important to identify and analyze emerging design conflicts. In this thesis I have studied conflicts between maintainability design methods onthe one hand, and performance and availability methods and techniques on the other. I present the results of four case-studies involving four different applications. It is a characteristic of these applications that half of the system can be regarded as a telecommunications system and the other as a typical main-stream system, i.e. all systems make high demands on performance and availability but also very high demands on high maintainability. In studying these applications, I have identified two major conflicts: granularity in dynamic memory usage and source code size. My results show that these two conflicts can cause problems of such amplitude that some applications become unusable. I found that conflicts in certain situations are inherent; in other cases they can be avoided - or at least reduced - by adjusting the design methods used. I have also shown that conflicts may quite simply be a matter of misconceptions. Ten guidelines have been combined into a simple process with the aim of helping software designers to avoid and reduce conflicts. A method which automatically reduces the dynamic memory conflict in object-oriented applications written in C++ has been developed, implemented and evaluated. Finally, I have defined optimal recovery schemes for high availability clusters.
13
Albattah, Waleed. "SOFTWARE MAINTAINABILITY AND TESTABILITY PREDICTIONS USING PACKAGE COHESION." Kent State University / OhioLINK, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=kent1415737576.
Full text
14
Jaradat, Omar. "Enhancing the Maintainability of Safety Cases Using Safety Contracts." Licentiate thesis, Mälardalens högskola, Inbyggda system, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-29133.
Full textAbstract:
Safety critical systems are those systems whose failure could result in loss of life, significant property damage, or damage to the environment. These systems require high quality and dependability levels in them, where system safety is a major property that should be adequately assured to avoid any severe outcomes. Many safety critical systems in different domains (e.g., avionics, railway, automotive, etc.) are subject to a certification. The certification process is based on an evaluation of whether the associated hazards to a system are mitigated to an acceptable level. Safety cases are often required to demonstrate how a regulatory body can reasonably conclude that a system is acceptably safe from the evidence available. The development of safety cases has become common practice in many safety critical system domains. However, safety cases are costly since they need significant amount of time and efforts to produce. This cost can be dramatically increased (even for already certified systems) due to system changes as they require maintaining the safety case before it can be submitted for certification. Anticipating potential changes is useful since it reveals traceable consequences that will eventually reduce the maintenance efforts. However, considering a complete list of anticipated changes is difficult. What can be easier though is to determine the flexibility of system components to changes. Sensitivity analysis has been proposed as a useful tool to measure the flexibility of the different system properties to changes. Furthermore, the concept of contracts have been proposed as a means for facilitating the change management process due to their ability to record the dependencies among system's components. In this thesis, we use sensitivity analysis to support changes prediction and prioritisation. We also use safety contracts to record the information of changes that will ultimately advise the engineers what to consider and check when changes actually happen.
15
Vaziry-Zanjany, Mohammad Ali. "Aircraft conceptual design modelling incorporating reliability and maintainability predictions." Thesis, Cranfield University, 1996. http://dspace.lib.cranfield.ac.uk/handle/1826/3437.
Full textAbstract:
A computer assisted conceptual aircraft design program has been developed (CACAD). It has an optimisation capability, with extensive break-down in maintenance costs. CACAD's aim is to optimise the size, and configurations of turbofan-powered transport aircraft. A methodology was developed to enhance the reliability of current aircraft systems, and was applied to avionics systems. R&M models of thermal management were developed and linked with avionics failure rate and its maintenance cost prediction methods. The impact of the environmental control system, and engine-provided bleed flow was also modelled and incorporated into CACAD. The program showed the ARINC 600 & 408A flow rates to the avionics bay, and to the deck instruments may both profitably be increased by 50%. This keeps the direct operating cost (DOC) increase at bay for long-range passenger aircraft, and offers a reduction of up to 1% in DOC for the short to medium range passenger aircraft. A methodology was developed to model all aspects of future high risk technologies, with special consideration given to reliability, maintainability, and development cost (R, M&D) predictions as applied to variable camber wings (VCW). Many aspects of VCW were modelled. These included different types of drag saving due to chord- wise, as well as span-wise camber variation. Models were also derived for mass, maintenance cost, and extra development cost increments for wing trailing edge devices, flight control, and hydraulic systems. On incorporation into CACAD, a reduction in DOC of up to 3.5% was predicted. The VCW technology were evaluated for DOC improvements, against a number of existing, future, and derivative aircraft, under different sensitivity conditions. R, M&D predictions were shown to be decisive in addressing the feasibility of a new technology. The R&M predictions of the whole study shows that, long range, low to medium capacity derivative transport aircraft are most appropriate for the VCW technology, and the short to medium range, low to medium capacity aircraft are most suitable for reliability enhancement projects of aircraft advanced systems.
16
Andreopoulos, William. "Achieving software quality through heuristic transformations, maintainability and performance." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2001. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/MQ58771.pdf.
Full text
17
Barabady, Javad. "Improvement of system availability using reliability and maintainability analysis /." Luleå : Luleå University of Technology, 2005. http://epubl.luth.se/1402-1757/2005/92.
Full text
18
Vaziry-Zanjany, Mohammad Ali (F). "Aircraft conceptual design modelling incorporating reliability and maintainability predictions." Thesis, Cranfield University, 1996. http://hdl.handle.net/1826/3437.
Full textAbstract:
A computer assisted conceptual aircraft design program has been developed
(CACAD). It has an optimisation capability, with extensive break-down in
maintenance costs. CACAD's aim is to optimise the size, and configurations of
turbofan-powered transport aircraft.
A methodology was developed to enhance the reliability of current aircraft systems,
and was applied to avionics systems. R&M models of thermal management were
developed and linked with avionics failure rate and its maintenance cost prediction
methods. The impact of the environmental control system, and engine-provided bleed
flow was also modelled and incorporated into CACAD. The program showed the
ARINC 600 & 408A flow rates to the avionics bay, and to the deck instruments may
both profitably be increased by 50%. This keeps the direct operating cost (DOC)
increase at bay for long-range passenger aircraft, and offers a reduction of up to 1% in
DOC for the short to medium range passenger aircraft.
A methodology was developed to model all aspects of future high risk technologies,
with special consideration given to reliability, maintainability, and development cost
(R, M&D) predictions as applied to variable camber wings (VCW). Many aspects of
VCW were modelled. These included different types of drag saving due to chord-
wise, as well as span-wise camber variation. Models were also derived for mass,
maintenance cost, and extra development cost increments for wing trailing edge
devices, flight control, and hydraulic systems. On incorporation into CACAD, a
reduction in DOC of up to 3.5% was predicted. The VCW technology were evaluated
for DOC improvements, against a number of existing, future, and derivative aircraft,
under different sensitivity conditions. R, M&D predictions were shown to be decisive
in addressing the feasibility of a new technology.
The R&M predictions of the whole study shows that, long range, low to medium
capacity derivative transport aircraft are most appropriate for the VCW technology, and the short to medium range, low to medium capacity aircraft are most suitable for
reliability enhancement projects of aircraft advanced systems.
19
Yin, Qiying. "Incorporating reliability availability and maintainability (RAM) into process synthesis." Thesis, University of Manchester, 2012. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.556621.
Full text
20
Hedbäck, Andreas, and Deniz Ayar. "Expanding a Motion Controlled Game With Focus on Maintainability." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-149667.
Full textAbstract:
Motion controlled games can be a good physical activity for children, but the game has to be fun and engaging. We have, with a starting point in an existing base game, developed an achievement module which follows certain code standards to make it easier to understand, and to make hand overs of the code smoother. More work on the rest of the game has also been done to make it more engaging, while clean up of the existing code to follow the same standards.
21
Zellagui, Soumia. "Reengineering Object Oriented Software Systems for a better Maintainability." Thesis, Montpellier, 2019. http://www.theses.fr/2019MONTS010/document.
Full textAbstract:
Les systèmes logiciels existants représentent souvent des investissements importants pour les entreprises qui les développent avec l’intention de les utiliser pendant une longue période de temps. La qualité de ces systèmes peut être dégradée avec le temps en raison des modifications complexes qui leur sont incorporées. Pour faire face à une telle dégradation lorsque elle dépasse un seuil critique, plusieurs stratégies peuvent être utilisées. Ces stratégies peuvent se résumer en: 1) remplaçant le système par un autre développé à partir de zéro, 2) poursuivant la maintenance(massive) du système malgré son coût ou 3) en faisant une réingénierie du système. Le remplacement et la maintenance massive ne sont pas des solutions adaptées lorsque le coût et le temps doivent être pris en compte, car elles nécessitent un effort considérable et du personnel pour assurer la mise en œuvre du système dans un délai raisonnable. Dans cette thèse, nous nous intéressons à la solution de réingénierie. En général, la réingénierie d’un système logiciel inclut toutes les activités après la livraison à l’utilisateur pour améliorer sa qualité. Cette dernière est souvent caractérisé par un ensemble d’attributs de qualité. Nous proposons trois contributions pour améliorer les attributs de qualité spécifiques, que soient:la maintenabilité, la compréhensibilité et la modularité. Afin d’améliorer la maintenabilité, nous proposons de migrer les systèmes logiciels orientés objets vers des systèmes orientés composants. Contrairement aux approches existantes qui considèrent un descripteur de composant comme un cluster des classes, chaque classe du système existant sera migré en un descripteur de composant. Afin d’améliorer la compréhensibilité, nous proposons une approche pour la reconstruction de modèles d’architecture d’exécution des systèmes orientés objet et de gérer la complexité des modèles résultants. Les modèles, graphes, générés avec notre approche ont les caractéristiques suivantes: les nœuds sont étiquetés avec des durées de vie et des probabilités d’existence permettant 1) une visualisation des modèles avec un niveau de détail. 2) de cacher/montrer la structure interne des nœuds. Afin d’améliorer la modularité des systèmes logiciels orientés objets, nous proposons une approche d’identification des modules et des services dans le code source de ces systèmes.Dans cette approche, nous croyons que la structure composite est la structure principale du système qui doit être conservée lors du processus de modularisation, le composant et ses composites doivent être dans le même module. Les travaux de modularisation existants qui ont cette même vision, supposent que les relations de composition entre les éléments du code source sont déjà disponibles ce qui n’est pas toujours évident. Dans notre approche, l’identification des modules commence par une étape de reconstruction de modèles d’architecture d’exécution du système étudié. Ces modèles sont exploités pour d’identification de relations de composition entre les éléments du code source du système étudié. Une fois ces relations ont été identifiées, un algorithme génétique conservatif aux relations de composition est appliqué sur le système pour identifier des modules. En dernier, les services fournis par les modules sont identifiés à l’aide des modèles de l’architecture d’exécution du système logiciel analysé. Quelques expérimentations et études de cas ont été réalisées pour montrer la faisabilité et le gain en maintenabilité, compréhensibilité et modularité des logiciels traités avec nos propositionsLegacy software systems often represent significant investmentsfor the companies that develop them with the intention of using themfor a long period of time. The quality of these systems can be degraded over time due to the complex changes incorporated to them.In order to deal with these systems when their quality degradation exceeds a critical threshold, a number of strategies can be used. Thesestrategies can be summarized in: 1) discarding the system and developinganother one from scratch, 2) carrying on the (massive) maintenance of the systemdespite its cost, or 3) reengineering the system. Replacement and massive maintenance are not suitable solutions when the cost and time are to be taken into account, since they require a considerable effort and staff to ensurethe system conclusion in a moderate time. In this thesis, we are interested in the reengineering solution. In general, software reengineering includes all activities following the delivery to the user to improve thesoftware system quality. This latter is often characterized with a set of quality attributes. We propose three contributions to improve specific quality attributes namely: maintainability, understandability and modularity.In order to improve maintainability, we propose to migrateobject oriented legacy software systems into equivalent component based ones.Contrary to exiting approaches that consider a component descriptor as a clusterof classes, each class in the legacy system will be migrated into a componentdescriptor. In order to improve understandability, we propose an approach forrecovering runtime architecture models of object oriented legacy systems and managing the complexity of the resulted models.The models recovered by our approach have the following distinguishing features: Nodes are labeled with lifespans and empirical probabilities of existencethat enable 1) a visualization with a level of detail. 2) the collapsing/expanding of objects to hide/show their internal structure.In order to improve modularity of object-oriented software systems,we propose an approach for identifying modulesand services in the source code.In this approach, we believe that the composite structure is the main structure of the system that must be retained during the modularization process, the component and its composites must be in the same module. Existing modularization works that has this same vision assumes that the composition relationships between the elements of the source code are already available, which is not always obvious. In our approach, module identification starts with a step of runtime architecture models recovery. These models are exploited for the identification of composition relationships between the elements of the source code. Once these relationships have been identified, a composition conservative genetic algorithm is applied on the system to identify modules. Lastly, the services provided by the modules are identified using the runtime architecture models of the software system. Some experimentations and casestudies have been performed to show the feasibility and the gain inmaintainability, understandability and modularity of the software systems studied with our proposals
22
Mousavi, Seyedamirhossein. "Maintainability Evaluation of Single Page Application Frameworks : Angular2 vs. React." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-60901.
Full textAbstract:
Web applications are subject to intense market forces, fast delivery and rapid requirement and code change. These are the factors that make maintainability a significant concern in any and especially web application development. In this report we develop a functional equivalent prototype from an existing Angular app, using ReactJs and afterward compare their maintainability as defined by ISO/IEC 25010. The maintainability comparison is made by calculating maintainability index for each of the applications using Plato analysis tool. The results do not show a significant difference in the calculated value of the final products. Source code analysis shows that changes in data flow need more modification in the Angular app, but with the objective oriented approach provided by Angular, we can have smaller chunks of code and thus higher maintainability per file and respectively a better average value. We conclude that regarding the lack of research and models in this area, MI is a consistent measurement model and Plato is a suitable tool for analysis. Though maintainability is highly bounded to the implementation, functionalities which are provided by the Angular framework as a bundle is more appropriate for large enterprises and complex products where React works better for smaller products.
23
Perepletchikov, Mikhail, and mikhail perepletchikov@rmit edu au. "Software Design Metrics for Predicting Maintainability of Service-Oriented Software." RMIT University. Computer Science and Information Technology, 2009. http://adt.lib.rmit.edu.au/adt/public/adt-VIT20091105.144445.
Full textAbstract:
As the pace of business change increases, service-oriented (SO) solutions should facilitate easier maintainability as underlying business logic and rules change. To date, little effort has been dedicated to considering how the structural properties of coupling and cohesion may impact on the maintainability of SO software products. Moreover, due to the unique design characteristics of Service-Oriented Computing (SOC), existing Procedural and Object-Oriented (OO) software metrics are not sufficient for the accurate measurement of service-oriented design structures. This thesis makes a contribution to the field of SOC, and Software Engineering in general, by proposing and evaluating a suite of design-level coupling and cohesion metrics for predicting the maintainability of service-oriented software products early in the Software Development LifeCycle (SDLC). The proposed metrics can provide the following benefits: i) facilitate design decisions that could lead to the specification of quality SO designs that can be maintained more easily; ii) identify design problems that can potentially have a negative effect on the maintainability of existing service-oriented design structures; and iii) support more effective control of maintainability in the earlier stages of SDLC. More specifically, the following research was conducted as part of this thesis: - A formal mathematical model covering the structural and behavioural properties of service-oriented system design was specified. - Software metrics were defined in a precise, unambiguous, and formal manner using the above model. - The metrics were theoretically validated and empirically evaluated in order to determine the success of this thesis as follows: a. Theoretical validation was based on the property-based software engineering measurement framework. All the proposed metrics were deemed as theoretically valid. b. Empirical evaluation employed a controlled experimental study involving ten participants who performed a range of maintenance tasks on two SO systems developed (and measured using the proposed metrics) specifically for this study. The majority of the experimental outcomes compared favourably with our expectations and hypotheses. More specifically, the results indicated that most of the proposed metrics can be used to predict the maintainability of service-oriented software products early in the SDLC, thereby providing evidence for the validity and potential usefulness of the derived metrics. Nevertheless, a broader range of industrial scale experiments and analyses are required to fully demonstrate the practical applicability of the metrics. This has been left to future work.
24
Senbayrak, Ziya. "Effects Of Spl Domain Engineering On Testing Cost And Maintainability." Master's thesis, METU, 2013. http://etd.lib.metu.edu.tr/upload/12615495/index.pdf.
Full textAbstract:
A software product line (SPL) consists of a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. Together with testing of final deliverable products developed within the SPL, called Integration Testing, particularly important in this context is the way individual hardware as well as software components in an SPL are tested and certified for usage within the SPL. This study investigates specific approaches and techniques proposed in the literature for unit testing in the SPL context. Problems inherent to this issue were studied and possible solutions aiming towards systematic and effective testing of hardware as well as software units in SPLs have been proposed. The specific problems of SPL testing in ASELSAN were investigated in the light of these possible solutions and their applicability as well as their benefits were quantitatively assessed.
25
SANTANNA, CLAUDIO NOGUEIRA. "MAINTAINABILITY AND REUSABILITY OF ASPECT-ORIENTED SOFTWARE: AN ASSESSMENT FRAMEWORK." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2004. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=5447@1.
Full textAbstract:
COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIORO desenvolvimento de software orientado a aspectos (DSOA) vem obtendo maior atenção tanto da academia quanto da indústria. Sistemas orientados a aspectos compreendem novas abstrações de engenharia de software e tratam de diferentes dimensões de complexidade. Conseqüentemente, o DSOA traz novos problemas para a engenharia de software experimental. Novos mecanismos de avaliação são necessários para medir os graus de manutenibilidade e reusabilidade de sistemas orientados a aspectos. Esta dissertação apresenta um framework de avaliação para o DSOA composto por dois elementos: um conjunto de métricas e um modelo de qualidade. No intuito de evitar a reinvenção de soluções já testadas, esses elementos são baseados em princípios bem conhecidos da engenharia de software e métricas já existentes. O framework proposto foi avaliado no contexto de dois estudos empíricos de domínios distintos, com características, níveis de controle e níveis de complexidade diferentes. O primeiro estudo empírico comparou uma abordagem orientada a objetos com uma abordagem orientada a aspectos para o projeto e implementação de um sistema multi- agentes. O segundo estudo envolveu a aplicação do framework proposto para avaliar as implementações em Java e AspectJ dos padrões de projeto da GoF.
Aspect-oriented software development (AOSD) is gaining wide attention both in research environments and in industry. Aspect- oriented systems encompass new software engineering abstractions and different complexity dimensions. As a consequence, AOSD poses new problems to empirical software engineering. It requires new assessment mechanisms to measure the maintainability and reusability degrees of aspect-oriented systems. This dissertation presents an assessment framework for AOSD, which is composed of two components: a suite of metrics and a quality model. These components are based on well-known principles and existing metrics in order to avoid the reinvention of well-tested solutions. The proposed framework has been evaluated in the context of two different empirical studies with different characteristics, diverse domains, varying control levels and different complexity degrees. The first study compared an object-oriented approach and an aspect-oriented approach to the design and implementation of a multi-agent system. The second study involved the application of the proposed framework to evaluate Java and AspectJ implementations of the GoF design patterns.
26
Kung, Chieh Julius. "Fatigue and fracture reliability and maintainability process for structural systems." Diss., The University of Arizona, 1991. http://hdl.handle.net/10150/185661.
Full textAbstract:
Structures subject to oscillatory stresses are vulnerable to fatigue and/or fracture failure. But some fatigue and fracture design factors are subject to considerable uncertainty. Therefore, probabilistic and statistical methods are appropriate as tools for making design decisions and reliability assessments of structural systems. System reliability can be improved by a maintenance program of periodic inspection and repair or replacement of damaged members. But there are also uncertainities introduced by the inspection process. In summary, the fatigue/fracture reliability and maintainability (FRM) process for a structural system is a "replacement/repair renewal" process complicated by a large number of random variables and small failure probabilities for a typical system. The goal of this research is to develop an efficient numerical method to estimate the reliability and performance of structural systems subject to the FRM process. Reliability methods such as first order reliability methods (FORM) and second order reliability methods (SORM) are not appropriate as tools to analyze the FRM process. As a continuation of the FRM study by Torng (1989), an equivalent member approach is introduced. A sampling simulation procedure is employed. The "equivalent member approach" considers each member (a series system) as a single member having one single stress concentration representing the "weakest" component. Elementary extreme value theory is applied to approximate the distribution of ultimate strength and fatigue strength of the member. It is demonstrated that significant savings in computer (CPU) time is achieved without sacrificing accuracy in reliability and performance estimates. Typically, the sampling scheme employed herein will result in an improvement in computer time by a factor of 1000 relative to the direct Monte Carlo method. One goal of this research is to study the relationship between the design factors of the tension-leg platform (TLP) tendon system. Effects on system reliability and maintenance performance (repair and replacement rates) are studied as a function of (a) number of joints, J, (b) number of members, M, (c) inspection frequency, (d) inspection sensitivity as defined by the POD (probability of detection) curve, (e) ultimate tensile strength, (f) repair policy, etc. The performance of an initially damaged or flawed tendon system is investigated. The reliability of a tendon system that uses pressurized tendon to detect through thickness cracks is studied as is the vulnerability of the tendon system before replacement of broken tendon.
27
Acimovic, Aleksandar, and Aleksandar Bajceta. "Test script design approaches supporting reusability, maintainability and review process." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-44724.
Full textAbstract:
Software testing is widely considered to be one of the most important parts of software development life-cycle. In this research, we investigated potential improvements in the testing process and design of automated test scripts inside Bombardier Transportation. For the creation of automated test scripts BT is using a group of programs called TAF (Test Automation Framework). These scripts are used for testing Train Control Management System (TCMS), software that is used for managing the train. TAF can export its test scripts in XML format. XML scripts are analyzed in order to identify the most frequent changes. To better understand the life cycle of automated Test scripts official documentation that defines the Verification and Validation process inside BT was analyzed. Also, an interview was conducted with one of the responsible persons for testing. We believe that we have found a possible solution for improving testing process and creation of automated test scripts in BT, and to evaluate it proof of concept tool was developed. The main idea behind the tool is to write the test script using keywords which are based on analysis that was conducted on test specification documentation. These keywords represent frequent actions that are being tested on the train. By storing those actions in keywords re-usability of test script is being increased. Also, because they are based on naturally language, they are having positive effect on readability and maintenance of the test script.
28
Wilson, Michael Thomas. "Technology advancement in intelligent buildings a through preplanning process pertaining to long-term maintainability /." Thesis, Available online, Georgia Institute of Technology, 2004:, 2004. http://etd.gatech.edu/theses/available/etd-08172004-150143/unrestricted/wilson%5Fmichael%5Ft%5F200412%5Fms.pdf.
Full textAbstract:
Thesis (M.S.)--Building Construction, Georgia Institute of Technology, 2005.Dr. Felix T. Uhlik III, Committee Member ; Mr. Cliff Stern, Committee Member ; Dr. Rita Oberle, Committee Member ; Ms. Kathy O. Roper, Committee Chair. Includes bibliographical references.
29
Ibrahim, M. E. "Advanced applications of smart materials research for the enhancement of Australian defence capability." Fishermans Bend, Victoria : Defence Science and Technology Organisation, 2009. http://nla.gov.au/nla.arc-24764.
Full text
30
Lucas, Steven A. Hammond Terrence E. "Methods for continuous improvement of fielded jet engine reliability and maintainability /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1994. http://handle.dtic.mil/100.2/ADA294757.
Full text
31
Gibbins, Wilson K. "The relationship among commenting style, software complexity metrics, and software maintainability." Thesis, This resource online, 1988. http://scholar.lib.vt.edu/theses/available/etd-04122010-083707/.
Full text
32
Gardner, Simon C. "A design methodology for reliability and maintainability : related to manufacturing industries." Thesis, Coventry University, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.287517.
Full text
33
Nggada, Shawulu Hunira. "Multi-objective system optimisation with respect to availability, maintainability and cost." Thesis, University of Hull, 2012. http://hydra.hull.ac.uk/resources/hull:6369.
Full textAbstract:
Safety critical engineering systems are becoming increasingly larger and more complex. One way of ensuring the dependability of such systems is via architectural redundancy and replication of components. Use of redundancy has its limitations though, as it can increase the size, weight and cost of a system beyond acceptable levels. An alternative approach to improving dependability is by designing the system with preventive maintenance (PM) in mind. A well articulated PM policy can reduce the occurrence of system failure, thereby improving dependability attributes such as safety, reliability and availability as well as cost. In a typical scenario, components of the system are maintained periodically at a fixed time interval (month, year, etc). This interval may vary from component to component and therefore the determination of an optimal PM schedule for all components in the system is non trivial. The options for maintenance are simply too many to exhaustively enumerate and evaluate, and therefore the choice of an optimal PM schedule that provide the best trade-offs between dependability and cost becomes a search and optimisation problem. It is precisely this problem that this thesis addresses. Firstly, the thesis investigates the effects of perfect and imperfect preventive maintenance policies on system reliability, availability and cost by establishing mathematical models for both policies. Secondly, a multi-objective optimisation approach is formulated for PM scheduling that takes into account dependability and cost, and finally the approach is evaluated on two case studies using a well-established semi-automated dependability analysis tool - HiP-HOPS. The approach allows automatic model transformation such as substitution of components as well as PM maintenance to be applied by Genetic Algorithms as mechanisms for automatically improving design and achieving trade-offs between dependability and cost. Results from case studies show that this approach can provide an effective tool for definition of PM schedules and lead to engineering and economic benefits.
34
Dodge, Meghan N., and Robert F. III McKelvey. "Why the survivability onion should include Reliability, Availability, and Maintainability (RAM)." Thesis, Monterey, California: Naval Postgraduate School, 2013. http://hdl.handle.net/10945/37614.
Full textAbstract:
Approved for public release; distribution is unlimitedReliability, Availability, and Maintainability (RAM) and Survivability are both diverse disciplines that explore how a system will perform when placed within an operational environment. This Joint Applied Project provides a qualitative analysis of the interconnectivity of RAM and Survivability. It shows that an in-depth RAM analysis ensures military personnel are better protected throughout the life cycle. Methodologies for improving reliability and maintainability are also presented, to include physics of failure, highly accelerated life testing/highly accelerated stress screening, preventative maintenance determination and pit stop engineering. This analysis uses an Active Protection System (APS) to show that, when RAM is included in the Survivability Onion; both Survivability and RAM evaluations benefit; survivability assessments become more complete; RAM assessments are completed sooner; and ultimately, better systems are put into the hands of service members. As APS requirements are developed, it is important that they include the Materiel Availability Key Performance Parameter with associated Reliability and Ownership Cost Key System Attributes. When evaluating an APS (or any system) the independent evaluator team members need to integrate and discuss the impacts of the capabilities and limitations they observed with each other to ensure that the deficiencies are properly addressed in the reports.
35
Lucas, Steven A., and Terrence E. Hammond. "Methods for continuous improvement of fielded jet engine reliability and maintainability." Thesis, Monterey, California. Naval Postgraduate School, 1994. http://hdl.handle.net/10945/42832.
Full textAbstract:
Approved for public release, distribution unlimitedIn an overall effort to reduce total operating costs within the Department of Defense, several Defense Management Review Decisions were issued which significantly affected the Navy's inventory levels for spare parts. This thesis examines the effect of these changes on requisition processing at the wholesale level. The primary objective is to determine if requirements are being satisfied from wholesale stock on hand at the Point of Entry (POE) of the requisition, or if unnecessary additional costs and delivery delays are incurred as a result of incorrect processing of the requisitions. In-depth analysis is conducted on requisitions submitted by West coast fleet units for DLA managed material for which wholesale stock was available at the POE. Research revealed that requisitions were not always satisfied locally and that adherence to current policy was inconsistent, causing delays and additional costs. A supplemental finding revealed a need for wholesale stock positioning policy changes where material would be actively positioned at selected stock points to support regional demand.
36
Cho, Daniel. "Identifying the Essential Reliability, Availability, and Maintainability Tasks for Aerospace Systems." Digital Commons at Loyola Marymount University and Loyola Law School, 2011. https://digitalcommons.lmu.edu/etd/379.
Full textAbstract:
This report provides the essential Reliability, Availability, and Maintainability (RAM) tasks that can be applicable to all types of aerospace projects varying in contract cost and complexity. The drive for this study was to identify a set of tailorable tasks to apply towards smaller aerospace programs. Though the report is specifically focused on aerospace projects, these essential RAM tasks and principles can be applied across all types of complex systems that require a high level of reliability. Methods of analysis were primarily focused on comparing Northrop Grumman Aerospace System (NGAS) reliability processes to the commercial industries best practices for reliability. A paper study of reliability plans and interviews of key reliability engineers were used to baseline the reliability process at NGAS. To baseline the commercial industry processes, a paper study was performed on best practices and lessons learned.
Results indicate that NGAS processes for RAM are lean and effective. Over 16 programs plans were reviewed, which dated from the 1970's to current programs, and they all show a consistent process for conducting reliability analysis. On the contrary, the commercial industry RAM practices are inconsistent and are still being matured. Of the commercial industries reviewed, the nuclear power industry best matched the reliability processes with NGAS. Based on interviews and paper studies, the essential RAM activities are summed up by two activities, the Failure Modes and Effects Analysis (FMEA), and Reliability Predictions/ Analysis. These two tasks provide the highest value in achieving the programs reliability goals.
Current NGAS RAM practices match the best practices performed in the commercial industry, but tailoring and scope reduction is necessary when applying these practices for smaller aerospace programs. Based of program budget and complexity, this paper provides the recommendations for tailoring the essential reliability tasks, the FMEA and Reliability Predictions. Specific instructions were provided on how to tailor the essential reliability tasks to obtain the highest value based on the program budget and complexity. These basic instructions can be summarized as: All complex programs, regardless of budget should perform a functional FMEA. As complexity and budget increases, additional detailed FMEAs shall be performed for units of risk Based on the FMEA, a Critical Items List shall be created and managed to closure. It is vital that there is a plan to work off any reliability risks Part count method should be performed if budget and time are limited. Part stress method often uses outdated failure rate databases, causing over conservative predictions. There is higher value to the program to perform a part count method to identify areas of concern in the design
37
van, Dreven Jonne. "Functional Decomposition Techniques and Their Impact on Performance, Scalability and Maintainability." Thesis, Blekinge Tekniska Högskola, Institutionen för datavetenskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-21876.
Full textAbstract:
Context The last decade shows many solution proposals of functional decomposition techniques to aid in developing microservice architectures. While some solutions may work, it is uncertain what the effects are on quantitative, measurable metrics; thus, the proposals require validation. Objective The study measures the effects of various functional decomposition techniques on performance, scalability, and maintainability. Furthermore, the study will compare the treatments in order to find whether a statistical significance exists. Method The study uses a controlled experiment containing three functional decomposition techniques—Event Storming, Actor/Action, and Service Cutter—applied on the same use case. The use case follows the CoCoMe framework, which forms the basis of the experiment. Results Each treatment shows similar behavior while presenting different architectural designs. The study found no statistical significance for performance, scalability, and maintainability. Conclusion Evidence suggests that the convenience of an approach might be more important than the resulting architecture since they will likely lead to the same outcome. If performance issues arise, it would likely be due to the microservices architecture and not the functional decomposition technique; therefore, the microservices architecture might not equally benefit any situation or corporation. Furthermore, the study found that service granularity might not be as relevant as some studies claim it to be, and other factors could be more crucial.
38
Ghosheh, Emad. "A novel model for improving the maintainability of web-based systems." Thesis, University of Westminster, 2010. https://westminsterresearch.westminster.ac.uk/item/905xy/a-novel-model-for-improving-the-maintainability-of-web-based-systems.
Full textAbstract:
Web applications incorporate important business assets and offer a convenient way for businesses to promote their services through the internet. Many of these web applica- tions have evolved from simple HTML pages to complex applications that have a high maintenance cost. This is due to the inherent characteristics of web applications, to the fast internet evolution and to the pressing market which imposes short development cycles and frequent modifications. In order to control the maintenance cost, quantita- tive metrics and models for predicting web applications’ maintainability must be used. Maintainability metrics and models can be useful for predicting maintenance cost, risky components and can help in assessing and choosing between different software artifacts. Since, web applications are different from traditional software systems, models and met- rics for traditional systems can not be applied with confidence to web applications. Web applications have special features such as hypertext structure, dynamic code generation and heterogenousity that can not be captured by traditional and object-oriented metrics. This research explores empirically the relationships between new UML design met- rics based on Conallen’s extension for web applications and maintainability. UML web design metrics are used to gauge whether the maintainability of a system can be im- proved by comparing and correlating the results with different measures of maintain- ability. We studied the relationship between our UML metrics and the following main- tainability measures: Understandability Time (the time spent on understanding the soft- ware artifact in order to complete the questionnaire), Modifiability Time(the time spent on identifying places for modification and making those modifications on the software artifact), LOC (absolute net value of the total number of lines added and deleted for com- ponents in a class diagram), and nRev (total number of revisions for components in a class diagram). Our results gave an indication that there is a possibility for a relationship to exist between our metrics and modifiability time. However, the results did not show statistical significance on the effect of the metrics on understandability time. Our results showed that there is a relationship between our metrics and LOC(Lines of Code). We found that the following metrics NAssoc, NClientScriptsComp, NServerScriptsComp, and CoupEntropy explained the effort measured by LOC(Lines of Code). We found that NC, and CoupEntropy metrics explained the effort measured by nRev(Number of Revi- sions). Our results give a first indication of the usefulness of the UML design metrics, they show that there is a reasonable chance that useful prediction models can be built from early UML design metrics.
39
Raza, Ali. "Improving Reuse and Maintainability of Communication Software With Conversation-Aware Aspects." DigitalCommons@USU, 2014. https://digitalcommons.usu.edu/etd/3700.
Full textAbstract:
Inter-process communications (IPC) are ubiquitous in today’s software systems, yet they are rarely treated as first-class programming concepts. Implementing crosscutting concerns for message-based IPC are difficult, even using aspect-oriented programming languages (AOPL) such as AspectJ. Many of these challenges are because the context of a communication-related crosscutting concern is often a conversation consisting of message sends and receives. Hence, developers typically have to implement communication protocols manually using primitive operations, such as connect, send, receive, and close. This dissertation describes an extension to AspectJ, called CommJ, with which developers can implement communication-related concerns in cohesive and loosely coupled aspects. It then presents preliminary, but encouraging results from a subsequent study that begin by defining a reuse and maintenance quality model. Subsequently the results show seven different ways in which CommJ can improve the reusability and maintainability of applications requiring network communications.
40
Agusa, Kiyoshi. "Software Development Technique for WEB Applications with High Reliability and High Maintainability." INTELLIGENT MEDIA INTEGRATION NAGOYA UNIVERSITY / COE, 2004. http://hdl.handle.net/2237/10352.
Full text
41
Præsto, Richard. "Articulated Maintenance : Improving maintainability for the nextgenerations of Volvo CE’s articulated haulers." Thesis, Luleå tekniska universitet, Institutionen för ekonomi, teknik och samhälle, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-66641.
Full textAbstract:
This is a project performed by me, Richard Præsto, student at Luleå University ofTechnology, with the intentions to suggest an improvement for the maintenancesystem of Volvo Construction Equipment’s articulated haulers. Today, themaintenance process consists of several different maintenance points and isperformed by maintenance technicians all over the world – but since the machinesneed to be taken out of production in order to receive maintenance, the processneeds to be quick. By researching documents, performing field studies and testingnew ideas, several different solutions were found and evaluated, to eventually befiltered down to one final concept. The final concept, which suggested animprovement of the engine oil and engine filter exchange processes, lived up to theexpectations by fulfilling the project goals and objectives. It was concluded that thesolution was a clear improvement and that it was also applicable to the whole rangeof the VCE machines.
42
O'Keefe, John Daniel. "A reliability, maintainability, supportability and availability analysis of a submarine sonar system." Master's thesis, This resource online, 1990. http://scholar.lib.vt.edu/theses/available/etd-02022010-020050/.
Full text
43
Lewis, John A. "A methodology for integrating maintainability into large-scale software using software metrics." Thesis, Virginia Tech, 1989. http://hdl.handle.net/10919/43094.
Full textAbstract:
Maintainability must be integrated into software as early in the development life cycle as possible to avoid overwhelming maintenance costs at later stages. This research describes a methodology which assists in the development of maintainable systems and does so without disrupting industry standard development techniques. The process uses software metrics and iterative enhancement concepts to reduce the complexity of high-level language code, making it less error-prone and more maintainable. The experiment uses large-scale system software from a major software producer.Master of Science
44
Lewis, Doris Trinh 1957. "A ROBUST METHOD FOR USING MAINTAINABILITY COST MODELS (RELIABILITY, OPTIMIZATION, SENSITIVITY, UNCERTAINTY)." Thesis, The University of Arizona, 1986. http://hdl.handle.net/10150/292098.
Full text
45
Turk, Tuna. "The Effect Of Software Design Patterns On Object-oriented Software Quality And Maintainability." Master's thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12611104/index.pdf.
Full textAbstract:
This study investigates the connection between design patterns, object oriented (OO) quality metrics and software maintainability. The literature on OO metrics, design patterns and software maintainability are reviewed, the relation between OO metrics and software maintainability is investigated, and then, in terms of obtained maintainability indicator metrics, the maintainability change of an application due to usage of design patterns is observed.
46
Du, Junrong. "Evaluation of equipment reliability, availability and maintainability in an oil sands processing plant." Thesis, University of British Columbia, 2008. http://hdl.handle.net/2429/7527.
Full textAbstract:
The oil sands industry is a developing sector of Canada’s economy; one area of focus for
oil sands companies is to improve plant maintenance and overall plant availability.
Although considerable progress has been made in the improvement of plant maintenance
in other industries, oil sands and mining companies in general do not significantly benefit
from this due to variable feed supply that impacts plant performance. As well historically
for mining maintenance has not been done well.
The work presented in this thesis develops a framework for understanding oil sands
processing plant key equipment failures by utilizing data collected over two years at
Albian Sands Energy Inc, an operator of an oil sands mine in Alberta, Canada. The data
is used to calculate mean time between maintenance for key pieces of oils sand
processing equipment. As well various statistical techniques are applied to the data to
identify the best maintenance strategies for the site. Finally the efficacy of advanced
statistical techniques, such as Power Law modeling, for predicting time to next failure for
equipment is demonstrated.
47
Rodriguez, Luis H. (Luis Humberto) 1968. "View-based abstraction : enhancing maintainability and modularity in the presence of implementation dependencies." Thesis, Massachusetts Institute of Technology, 1997. http://hdl.handle.net/1721.1/43526.
Full textAbstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1997.Includes bibliographical references (p. 173-177).
by Luis H. Rodriguez, Jr.
Ph.D.
48
Magnusson, Erik, and David Grenmyr. "An Investigation of Data Flow Patterns Impact on Maintainability When Implementing Additional Functionality." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-57024.
Full textAbstract:
JavaScript is breaking ground with the wave of new client-side frameworks. However, there are some key differences between some of them. One major distinction is the data flow pattern they applying. As of now, there are two predominant patterns used on client side frameworks, the Two-way data flow pattern and the Unidirectional data flow pattern. In this research, an empirical experiment was conducted to test the data flow patterns impact on maintainability. The scope of maintainability of this research is defined by a set of metrics: Amount of lines code, an amount of files and amount of dependencies. By analyzing the results, a conclusion could not be made to prove that the data flow patterns does affect maintainability, using this research method.
49
SARAIVA, Juliana de Albuquerque Gonçalves. "Classifying metrics for assessing object-oriented software maintainability: a family of metrics’ catalogs." Universidade Federal de Pernambuco, 2014. https://repositorio.ufpe.br/handle/123456789/12152.
Full textAbstract:
Submitted by Nayara Passos (nayara.passos@ufpe.br) on 2015-03-12T14:07:25Z
No. of bitstreams: 2
TESE Juliana de Albuquerque Gonçalves Saraiva.pdf: 2801469 bytes, checksum: 2f35aeb3fe1c0178a717be10adc01c26 (MD5)
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)Made available in DSpace on 2015-03-12T14:07:25Z (GMT). No. of bitstreams: 2 TESE Juliana de Albuquerque Gonçalves Saraiva.pdf: 2801469 bytes, checksum: 2f35aeb3fe1c0178a717be10adc01c26 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2014
FACEPE, INES
Atualmente, Programao Orientada a Objetos (POO) um dos paradigmas mais utilizados. Complementarmente, a manutenibilidade de software considerada um atributo de software que desempenha um papel importante com relao ao nvel de qualidade. Neste contexto, a Manutenibilidade de Software Orientado a Objetos (MSOO) foi estudada atravs de anos e vrios pesquisadores propuseram um elevado nmero de mtricas para a medir. Como consequncia do nmero e da diversidade de mtricas existentes, alm da no padronizao nas definies e nomenclatura, a tomada de deciso sobre quais mtricas podem ser adotadas para realizar estudos em MSOO difcil. Desta forma, um mapeamento sistemtico foi realizado a fim de encontrar quais mtricas so usadas como indicadores de MSOO. Houve uma seleo inicial de 5175 estudos primrios e 138 artigos foram selecionados, resultando em 568 mtricas encontradas. Analisando as 568 mtricas, foram encontradas inconsistncias na nomenclatura destas mtricas, pois havia mtricas com nomes iguais mas significados diferentes (8 casos envolvendo 17 mtricas) e tambm mtricas com nomes diferentes e significados semelhantes (32 casos envolvendo 214 mtricas). Alm disto, uma categorizao destas mtricas foi proposta, sendo identificadas 7 categorias e 17 subcategorias. Estas categorias representam os cenrios de adoo de mtricas de MSOO. Adicionalmente, um portal web de mtricas foi desenvolvido para fornecer informaes sobre as mtricas para outros pesquisadores e tambm gerar catlogos de mtricas de acordo com o contexto da aplicao das mesmas. Este portal tambm pode ser alimentado sistematicamente por outros pesquisadores que lidam com mtricas de MSOO, fazendo com que os resultados deste trabalho possam representar os primeiros passos para padronizao e compreenso destas mtricas. Por ltimo, um quasi-experimento foi realizado para checar o grau de cobertura do catlogo proposto pela abordagem aqui apresentada quando o mesmo comparado com catlogos sugeridos por especialistas. 90% de cobertura foi obtido e este resultado foi confirmado com 99% de grau de confiana usando o Teste de Wilcoxon. De forma complementar, houve uma pesquisa de opinio para checar se os especialistas acharam catlogo gerado usando a nossa abordagem semelhante ou melhor do que o sugerido por eles. Sendo assim, os resultados da anlise da cobertura dos catlogos pode servir como indcios da utilidade da abordagem proposta para a escolha de mtricas na avaliao de MSOO.
Currently, Object-Oriented Programming (OOP) is one of the most used paradigms. Complementarily, the software maintainability is considered a software attribute that plays an important role in quality level. In this context, the Object-Oriented Software Maintainability (OOSM) has been studied through years, and many researchers have proposed a large number of metrics to measure it. As a consequence of the number and diversity of metrics, beyond the no standardization in metrics definition and naming, the decision-making process about which metrics can be adopted in experiments on OOSM, or even their using in software companies is a difficult task. Therefore, a systematic mapping study was conducted in order to find which metrics are used as indicators in OOSM assessments. There was an initial selection of 5175 primary studies and 138 were selected, resulting in 568 metrics found. Analyzing the 568 metrics, inconsistencies in metrics’ naming were found because there were metrics with the same names but different meanings (8 cases involving 17 metrics) and also, there were metrics with different names, however with similar meanings (32 cases involving 214 metrics). Moreover, a metrics’ categorization has been proposed to facilitate decision-making process about which ones have to be adopted, and 7 categories and 17 subcategories were identified. These categories represent the evaluation scenarios where OOSM metrics should be used. Additionally, a metrics’ web portal was developed to provide information about the metrics collected in this research, and to generate metrics’ catalogs according to the context of their adoption. This portal can also be systematically fed by other researchers that work with OOSM metrics, making the results of this work the first steps towards metrics’ standardization, and the improvement of the metrics’ validation. Finally, a quasi-experiment was conducted to check the coverage index of the catalogs generated using our approach over the catalogs suggested by experts. 90% of coverage was obtained and this result was confirmed with 99% of confidential level using the Wilcoxon Test. Complementarily, a survey was conducted to check the experts’ opinion about the catalog generated by the portal when they were compared by the catalogs suggested by the experts. Thus, the coverage evaluation can be the first evidences of the usefulness of the proposed approach for metrics’ choice in OOSM evaluation.
50
Rao, Naresh Krishna. "Scheduling optimal maintenance times for a system based on component reliabilities." Diss., Virginia Tech, 1992. http://scholar.lib.vt.edu/theses/available/etd-05042006-164506/.
Full text