Dissertations / Theses on the topic 'Software Measurement Framework'

To see the other types of publications on this topic, follow the link: Software Measurement Framework.

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 23 dissertations / theses for your research on the topic 'Software Measurement Framework.'

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

Wille, Cornelius [Verfasser]. "Software Agent Measurement Framework / Cornelius Wille." Aachen : Shaker, 2005. http://d-nb.info/118657741X/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Zhang, Jianhao, and Xuxiao Chen. "Software Evolvability Measurement Framework during an Open Source Software Evolution." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13983.

Full text
Abstract:
Context: Software evolution comes with the increasing growth of software applications both in size and complexity. Unlike the software maintenance, software evolution addresses more on the adaption of the new fast-changing requirements. Then the term of “software evolvability” comes with its importance for evaluating the evolution status of the software. However, it is not clearly identified especially in the context of open source software (OSS). Besides the most studies are about the description of software evolvability as a quality attribute, and very few research have done on the measurement of software evolvability during the software evolution process. Objectives: In this study we perform an in-depth investigation on identification of the OSS evolvability, and figure out the appropriate metrics used for measuring the OSS evolvability. Based on that we finally proposed the open source software evolvability measurement framework (OSEM) which could be used for measuring the software evolvability generally in an OSS context. Methods: At first, we conducted a literature review by combining backward snowballing search with systematic database search. Two research questions which are RQ1 and RQ2 are proposed for helping us to retrieve the key information for building the needed framework. Then we performed a case study on VLC media player (an OSS project) to validate the processes of the proposed framework. Results: Based on literature we could explicitly identify the OSS evolvability, and figure out the differences of software evolvability addressed in OSS context and non OSS context (e.g, the traceability refers to documentation in non OSS context, however in OSS context it refers to the release version of OSS project). Besides we also fulfill the evolvability measuring method by addressing the process of prioritization of evolvability sub-characteristics. In the end we implement the OSEM framework on VLC media player and get the well documented results which are clearly presented and easy to understand. Such results could be taken by the VLC developers as an input for the design and development of the VLC. Conclusions: We conclude that the open source software measurement framework (OSEM) is applicable, based on the time we spent on the case of VLC media player it is quite fast and efficient to use such framework. The results from the conduction of this framework are documented well and very clear for OSS users/developers to follow.
APA, Harvard, Vancouver, ISO, and other styles
3

Cruickshank, Kristian John. "A validation metrics framework for safety-critical software-intensive systems." Thesis, Monterey, Calif. : Naval Postgraduate School, 2009. http://edocs.nps.edu/npspubs/scholarly/theses/2009/Mar/09Mar%5FCruickshank.pdf.

Full text
Abstract:
Thesis (M.S. in Software Engineering)--Naval Postgraduate School, March 2009.
Thesis Advisors: Michael, James B. ; Shing, Man-Tak. "March 2009." Description based on title screen as viewed on April 23, 2009. Author subject terms: Software Metrics, Safety Metrics, Validation Metrics, Metrics Framework, Validation, Safety-Critical Software, Software Engineering, Goal Question Metric, Goal Structuring Notation. Includes bibliographical references (p. 119-121). Also available in print.
APA, Harvard, Vancouver, ISO, and other styles
4

Berry, Michael CSE UNSW. "Assessment of software measurement." Awarded by:University of New South Wales. CSE, 2006. http://handle.unsw.edu.au/1959.4/25134.

Full text
Abstract:
Background and purpose. This thesis documents a program of five studies concerned with the assessment of software measurement. The goal of this program is to assist the software industry to improve the information support for managers, analysts and software engineers by providing evidence of where opportunities for improving measurement and analysis exist. Methods. The first study examined the assessment of software measurement frameworks using models of best practice based on performance/success factors. The software measurement frameworks of thirteen organisations were surveyed. The association between a factor and the outcome experienced with the organisations' frameworks was then evaluated. The subsequent studies were more info-centric and investigated using models of information quality to assess the support provided for software processes. For these studies, information quality models targeting specific software processes were developed using practitioner focus groups. The models were instantiated in survey instruments and the responses were analysed to identify opportunities to improve the information support provided. The final study compared the use of two different information quality models for the assessing and improving information support. Assessments of the same quantum of information were made using a targeted model and a generic model. The assessments were then evaluated by an expert panel in order to identify which information quality model was more effective for improvement purposes. Results. The study of performance factors for software measurement frameworks confirmed the association of some factors with success and quantified that association. In particular, it demonstrated the importance of evaluating contextual factors. The conclusion is that factor-based models may be appropriately used for risk analysis and for identifying constraints on measurement performance. Note, however, that a follow-up study showed that some initially successful frameworks subsequently failed. This implied an instability in the dependent variable, success, that could reduce the value of factor-based models for predicting success. The studies of targeted information quality models demonstrated the effectiveness of targeted assessments for identifying improvement opportunities and suggest that they are likely to be more effective for improvement purposes than using generic information quality models. The studies also showed the effectiveness of importance-performance analysis for prioritizing improvement opportunities.
APA, Harvard, Vancouver, ISO, and other styles
5

Islam, A. K. M. Moinul, and Michael Unterkalmsteiner. "Software Process Improvement Measurement and Evaluation Framework (SPI-MEF)." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2493.

Full text
Abstract:
During the last decades, the dependency on software has increased. Many of today’s modern devices embed software to control their functions. The increasing dependency has also taken part in shaping the software development process to produce better quality software. Many researchers and practitioners have spent large investments to improve the software development process. A research area within software engineering that addresses the assessment and improvement issues in development processes is called Software Process Improvement (SPI). One of the essential aspects in software process improvement is measuring the outcome of the implemented changes. The measurement and evaluation of software process improvement provides the means for the organization to articulate the achievement level of their goals. Although the importance of measuring and evaluating the outcome of software process improvement is paramount, there exist no common guidelines or systematic methods of measuring and evaluating the improvement. This condition evokes difficulties for practitioners to implement software process improvement measurement programs. This issue has raised the challenge to develop and implement an effective framework for measuring and evaluating the outcome of software process improvement initiatives. This thesis presents a measurement and evaluation framework for software process improvement. SPI-MEF provides guidelines in the form of systematic steps to evaluate the outcome of software process improvement. The framework is based on key concepts which were elaborated in previous work. In this thesis, a validation of SPI-MEF is also conducted by involving representatives from academia and industry. The validation is aimed to judge the frameworks’ usability, applicability and usefulness. Finally, a refinement of the framework is carried out based on the input from the validation.
APA, Harvard, Vancouver, ISO, and other styles
6

Aktunc, Ozgur. "An entropy-based measurement framework for component-based hierarchical systems." Birmingham, Ala. : University of Alabama at Birmingham, 2007. https://www.mhsl.uab.edu/dt/2008r/aktunc.pdf.

Full text
Abstract:
Thesis (Ph. D.)--University of Alabama at Birmingham, 2007.
Additional advisors: Gary J. Grimes, Chittoor V. Ramamoorthy, Murat N. Tanju, Gregg L. Vaughn, B. Earl Wells. Description based on contents viewed Feb. 12, 2009; title from PDF t.p. Includes bibliographical references (p. 150-158).
APA, Harvard, Vancouver, ISO, and other styles
7

Wagner, Palheta Viana Paulino. "FROISPI Framework return on investment of software process improvement." Universidade Federal de Pernambuco, 2009. https://repositorio.ufpe.br/handle/123456789/1982.

Full text
Abstract:
Made available in DSpace on 2014-06-12T15:53:37Z (GMT). No. of bitstreams: 2 arquivo1924_1.pdf: 3478481 bytes, checksum: a0f58f98b37132402ca52683d62410df (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009
Fundação de Amparo à Pesquisa do Estado do Amazonas
As empresas de software brasileiras buscam conquistar cada vez mais o mercado nacional e internacional, os quais estão mais competitivos. A estratégia viável é investir no aumento da qualidade e produtividade. O foco desse trabalho é investigar fatores relevantes para mensurar o Return on Investment (ROI) em Melhoria de Processo de Software (MPS). Com o objetivo de propor um framework constituído por fases baseado nos conceitos da ROI Methodology, utilizando indicadores utilizados por David Rico em ROI of SPI e uma seleção de medições utilizadas para MPS. As fases são: Identificação do problema; Diagnóstico detalhado; Estimativa de ROI; Implementação e Encerramento. Para cada fase, baseados no paradigma GQM Goal-Question-Metric foram definidos indicadores de medição para monitorar o FROISPI. As quatro primeiras fases seguem o conceito clássico do PDCA, que para cada solução sugerida de melhoria, analisa seus resultados e se os mesmos forem considerados plenamente satisfatórios, seguirá para a fase de Encerramento, caso contrário o processo cíclico continua até a necessidade de melhoria ser satisfeita. Na fase de Encerramento serão apresentados à alta direção os resultados alcançados com a utilização do FROISPI. O experimento foi executado em três organizações de maturidade bem distintas, mas somente uma organização conseguiu concluir com êxito
APA, Harvard, Vancouver, ISO, and other styles
8

Horgan, Gerard. "Construction of a quality assurance and measurement framework for software projects." Thesis, Kingston University, 2000. http://eprints.kingston.ac.uk/20649/.

Full text
Abstract:
The way in which quality is modelled within an organisation has typically followed either a fixed-model or a tailorable approach. Fixed-model techniques suffer the disadvantage of inflexibility to local environments, since, the parameters of these models cannot be changed by users or designers to reflect their own views. The tailorable approaches tend to preclude cross-project comparisons. In addition, both techniques lack comprehensive guidelines for building quality into a software product, and lack the ability to resolve conflicts where individuals disagree about the model parameters. In this work, the construction of a new approach is described which overcomes these deficiencies. Since metrics and metric measurement is an important component of quality models, common metrics and measurement techniques are identified, before the construction and evaluation of the new quality modelling approach is presented. A common metric is software size, measurement of which can be performed by use of the Function Point Analysis (FPA) technique. The weighting and adjustment factors of the traditional FPA approach are simplified here, to produce a new estimation technique which can be used at early stages in the development lifecycle. The new model is validated against two project datasets, and the results show a good degree of accuracy when estimating the FPA count, although a lower performance is achieved when estimating actual effort. The major component of this thesis is the construction of the new quality modelling approach, that enables local requirements tailoring whilst providing the ability to perform cross-project comparisons. Unlike existing techniques, comprehensive conflict resolution mechanisms are incorporated, and it is shown that the approach can be used to measure different software entities, allowing direct comparisons between measurements and thus producing more consistent results. The implementation consists of the construction of a software tool supporting the new methodology, and use of both this tool and the technique on real projects at a large financial organisation. The validation of the approach is performed against a list of requirements for a good quality model, and from feedback both from use on the projects and from a questionnaire survey.
APA, Harvard, Vancouver, ISO, and other styles
9

Zhu, Liming Computer Science &amp Engineering Faculty of Engineering UNSW. "Software architecture evaluation for framework-based systems." Awarded by:University of New South Wales. Computer Science and Engineering, 2007. http://handle.unsw.edu.au/1959.4/28250.

Full text
Abstract:
Complex modern software is often built using existing application frameworks and middleware frameworks. These frameworks provide useful common services, while simultaneously imposing architectural rules and constraints. Existing software architecture evaluation methods do not explicitly consider the implications of these frameworks for software architecture. This research extends scenario-based architecture evaluation methods by incorporating framework-related information into different evaluation activities. I propose four techniques which target four different activities within a scenario-based architecture evaluation method. 1) Scenario development: A new technique was designed aiming to extract general scenarios and tactics from framework-related architectural patterns. The technique is intended to complement the current scenario development process. The feasibility of the technique was validated through a case study. Significant improvements of scenario quality were observed in a controlled experiment conducted by another colleague. 2) Architecture representation: A new metrics-driven technique was created to reconstruct software architecture in a just-in-time fashion. This technique was validated in a case study. This approach has significantly improved the efficiency of architecture representation in a complex environment. 3) Attribute specific analysis (performance only): A model-driven approach to performance measurement was applied by decoupling framework-specific information from performance testing requirements. This technique was validated on two platforms (J2EE and Web Services) through a number of case studies. This technique leads to the benchmark producing more representative measures of the eventual application. It reduces the complexity behind the load testing suite and framework-specific performance data collecting utilities. 4) Trade-off and sensitivity analysis: A new technique was designed seeking to improve the Analytical Hierarchical Process (AHP) for trade-off and sensitivity analysis during a framework selection process. This approach was validated in a case study using data from a commercial project. The approach can identify 1) trade-offs implied by an architecture alternative, along with the magnitude of these trade-offs. 2) the most critical decisions in the overall decision process 3) the sensitivity of the final decision and its capability for handling quality attribute priority changes.
APA, Harvard, Vancouver, ISO, and other styles
10

Mughal, Aftab Ahmad, and Muhammad Nadeem. "A Framework for a More Structured, Integrated and Effective Software Measurement Process." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4072.

Full text
Abstract:
Software organizations have been initiating measurement programs as part of their software process improvement practices which in turn increase the quality of the software products. However, high numbers of organizations reported their measurement programs as failures. One of the major difficulties they faced was stated to be the difficulty in deciding which set of measures to collect for different software entities; products, processes, and resources. In addition to what should be collected, organizations would like to collect as minimum number of measures as possible in order to be cost effective. Different goal based measures selection models have been introduced to aid in these, namely Goal Question Metric (GQM) is one of the most well known and adopted ones by software organizations. It facilitates measurement programs to define goals and then collect measures according to goals. However, the current approaches require being more structured and integrated to enable an effective software measurement process. ‘Structured’ means the goals, questions and measures as well as their vertical and horizontal relations are well-defined. A structured measurement process can be ‘integrated’ to the organization via establishing links between business and organizational goals and the measurement process. The whole process becomes more ‘effective’ as these goals and measures become traceable, and hence the mechanisms to prioritize and select the optimum set of measures could be established. In this research work our main focus is to evaluate goal based models and to develop a framework for a more effective measurement process, called Structured Optimized Measurement Selection (SOMS). As part of SOMS, alternative ways for goals prioritization and measures optimization are proposed. In order to make the whole process more efficient, a tool is developed as well. Both SOMS with different alternative prioritization and optimization techniques as well as the tool were evaluated by conducting case studies in a CMMI level 3 software development organization and the results are compared to a previous case study conducted on the same case by using other techniques which are extensions of GQM, i.e. namely Structured Prioritized Goals Questions Metrics (SPGQM) and Optimum Measures Set Decision (OMSD).
APA, Harvard, Vancouver, ISO, and other styles
11

Cheng, Chow Kian, and Rahadian Bayu Permadi. "Towards an Evaluation Framework for Software Process Improvement." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3625.

Full text
Abstract:
Software has gained an essential role in our daily life in the last decades. This condition demands high quality software. To produce high quality software many practitioners and researchers put more attention on the software development process. Large investments are poured to improve the software development process. Software Process Improvement (SPI) is a research area which is aimed to address the assessment and improvement issues in the software development process. One of the most important aspects in software process improvement is to measure the results gained from the embarked process change. Without measuring the results, it is hard to tell whether the goals have been achieved or not. However, measurement for software process improvement is not a trivial task. Furthermore, there is no common systematic methodology that can be used to help measuring the performance of software process improvement initiatives. This thesis is intended to provide basic key concepts for the effective measurement and evaluation of the outcome of software process improvement. A major part of this thesis presents the systematic review in evaluating the outcome of software process improvement. The systematic review is aimed at the identification of the major issues in software process improvement evaluation and to gather the requirements for a software process improvement measurement and evaluation framework. Based on the results of the systematic review, a measurement and evaluation model is formulated. The objective of the model is to provide the groundwork for a software process improvement measurement and evaluation framework. The model is deemed to be applicable in a broad spectrum of scenarios by providing concepts that are independent from specific SPI initiatives.
APA, Harvard, Vancouver, ISO, and other styles
12

Asghari, Negin. "Evaluating GQM+ Strategies Framework for Planning Measurement System." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6060.

Full text
Abstract:
Context. Most organizations are aware of the significance of software measurement programs to help organizations assess and improve the ways they develop software. Measurement plays a vital role in improving software process and products. However, the number of failing measurement programs is high and the reasons are vary. A recent approach for planning measurement programs is GQM+Strategies, which makes an important extension to existing approaches, it links measurements and improvement activities to strategic goals and ways to achieve this goals. However, concrete guides of how to collect the information needed to use GQM+strategies is not provided in the literature yet. Objectives. The contribution of this research is to propose and assess an elicitation approach (The Goal Strategy Elicitation (GSE) approach) for the information needed to apply GQM+strategies in an organization, which also leads to a partial evaluation of GQM+strategies as such. In this thesis, the initial focus is placed on eliciting the goals and strategies in the most efficient way. Methods. The primary research approach used is action research, which allows to flexibly assess a new method or technique in an iterative manner, where the feedback of one iteration is taken into the next iteration, thus improving on the method or technique proposed. Complementary to that, we used literature review with the primary focus to position the work, explore GQM+strategies, and to determine which elicitation approach for the support of measurement programs have been proposed. Results. The Goal Strategy Elicitation (GSE) approach as a tool for eliciting goals and strategies within the software organization to contribute in planning a measurement program has been developed. The iterations showed that the approach of elicitation may not be too structured (e.g. template/notation based), but rather shall support the stakeholders to express their thoughts relatively freely. Hence, the end-result was an interview guide, not based on notations (as in the first iteration), and asking questions in a way that the interviewees are able to express themselves easily without having to e.g. distinguish definitions for goals and strategies. Conclusions. We conclude that the GSE approach is a strong tool for the software organization to be able to elicit the goals and strategies to support GQM+Strategies. GSE approach evolved in each iteration and the latest iteration together with the guideline is still used within the studied company for eliciting goals and strategies, and the organization acknowledged that they will continue to do so. Moreover, we conclude that there is a need for further empirical validation of the GSE approach in further full-scale industry trials.
APA, Harvard, Vancouver, ISO, and other styles
13

Tan, Jia. "FOUUX : A Framework for Usability & User Experience." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2662.

Full text
Abstract:
The main focus of the research in this thesis is to develop a consolidated framework of usability and user experience testing for telecom companies. The existing usability standards, literature and models are reviewed. Different usability evaluation methods; user experience definitions and evaluation methods are identified through a comprehensive literature survey. A brief discussion of the relationship between usability and user experience together with the challenges are also presented. Based on these, then it is explained how to unify these several resources into a single consolidated framework. A unified terminology for the usability attributes, sub-attributes and measures are presented in the framework. The framework is called Framework for Usability and User Experience (FOUUX). FOUUX serves as a guideline for tracing and interpreting the data collected on usability of products. It includes nine usability attributes, each of which corresponds to a specific aspect of usability that is identified in an existing standard, literature or model. These nine usability attributes are decomposed into twenty seven sub-attributes, and the relationship between the attributes and sub-attributes are presented. Questions and measures are then classified under sixty three sub-goals utilizing the Goal Question Metric (GQM) approach. In this thesis study, case study approach was used for validating the framework. The framework has been applied to a specific industry share case, that is, the Fitness application which is being developed by an industrial partner.
APA, Harvard, Vancouver, ISO, and other styles
14

Umoh, Emem Koffi. "REFINTO : an ontology-based requirements engineering framework for business-IT alignment in financial services." Thesis, University of Manchester, 2016. https://www.research.manchester.ac.uk/portal/en/theses/refinto-an-ontologybased-requirements-engineering-framework-for-businessit-alignment-in-financial-services(06738060-cedd-47cb-925e-1b897129bfd0).html.

Full text
Abstract:
Business-IT alignment has been a top research topic for three decades now and consistently ranks high on CIO priorities and concerns. In spite of its seeming advantages, sustainable business-IT alignment remains elusive in practice. This can be attributed to the language and knowledge gaps which impede mutual understanding between business and IT stakeholders. It can also be attributed to the limitations imposed by approaching alignment solely from a strategic perspective. This thesis argues for an ontology-based framework that bridges the language and knowledge gaps through closer interaction between business and IT stakeholders throughout the software development and project management lifecycles, especially at the requirements engineering stage. Attempts at achieving sustainable business-IT alignment predominantly focus on strategic alignment and have not been successful for various reasons. Firstly, driving down alignment initiatives to the operational and tactical levels is challenging. Secondly, it is difficult to operationalize the metrics used for evaluating alignment maturity at strategic levels. These limitations are less pronounced at the functional levels of an organization. It is at these levels that business strategies are executed and interaction between business and IT personnel is most frequent. The interaction between business and IT stakeholders in the execution of IT projects presents an opportunity that can be leveraged to drive alignment maturity. The proposed framework is discussed in terms of its underpinning hypotheses, workflows, tool design and implementation, its use with a third party framework and tool. Antecedents to operational and tactical alignment such as quality, reuse, communication, learning, and shared understanding, are proposed as a practical means of achieving sustainable alignment maturity. The framework is applied to real world, business-critical projects in a top global financial services organization and validated using descriptive statistical analysis and structural equation modelling techniques. Contributions made through the study are highlighted. This includes the Alignment Forces Model which unifies the proposed framework and its support tool within software development and project management lifecycles. The Alignment Forces model and how it can be applied in practice is presented. Results of the quantitative data analyses indicate support for the arguments for the framework towards improving business-IT alignment, however with some limitations. Results also indicate support for the hypotheses for the antecedents to sustainable alignment maturity at lower organizational levels put forward. Finally, suggestions on furthering the study, addressing its limitations, and refining the framework and tool are articulated.
APA, Harvard, Vancouver, ISO, and other styles
15

Otte, Tobias. "An investigation into quality assurance of the Open Source Software Development model." Thesis, University of Wolverhampton, 2010. http://hdl.handle.net/2436/109997.

Full text
Abstract:
The Open Source Software Development (OSSD) model has launched products in rapid succession and with high quality, without following traditional quality practices of accepted software development models (Raymond 1999). Some OSSD projects challenge established quality assurance approaches, claiming to be successful through partial contrary techniques of standard software development. However, empirical studies of quality assurance practices for Open Source Software (OSS) are rare (Glass 2001). Therefore, further research is required to evaluate the quality assurance processes and methods within the OSSD model. The aim of this research is to improve the understanding of quality assurance practices under the OSSD model. The OSSD model is characterised by a collaborative, distributed development approach with public communication, free participation, free entry to the project for newcomers and unlimited access to the source code. The research examines applied quality assurance practices from a process view rather than from a product view. The research follows ideographic and nomothetic methodologies and adopts an antipositivist epistemological approach. An empirical research of applied quality assurance practices in OSS projects is conducted through the literature research. The survey research method is used to gain empirical evidence about applied practices. The findings are used to validate the theoretical knowledge and to obtain further expertise about practical approaches. The findings contribute to the development of a quality assurance framework for standard OSSD approaches. The result is an appropriate quality model with metrics that the requirements of the OSSD support. An ideographic approach with case studies is used to extend the body of knowledge and to assess the feasibility and applicability of the quality assurance framework. In conclusion, the study provides further understanding of the applied quality assurance processes under the OSSD model and shows how a quality assurance framework can support the development processes with guidelines and measurements.
APA, Harvard, Vancouver, ISO, and other styles
16

Irshad, Mohsin. "Measuring Cost Avoidance Through Software Reuse." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5083.

Full text
Abstract:
Context. Software Reuse is considered as silver-bullet for software development. However, measuring bene ts of software reuse is difficult and cumbersome task because of varying number of factors involved in it. Di erent reuse cost models already exist in literature which measure var- ious di erent attributes of software reuse. Mainly these models are used for calculating return over investment or cost-bene t analysis. Objectives.We have investigated that very few cost eco- nomic models have been proposed for measuring costs avoidance,degree of empirical validation, assumptions, types ofartifacts they can measure and whether they provide guide- lines on collection of metrics for measuring reuse bene ts. Methods.In this research, a systematic review was con- ducted. Based on the results of systematic review, a model was proposed which can measure cost avoided by reuse of every kind of artifact. In a systematic all major article sources were used. Studies were selected after reading titles and abstracts. Three cost avoidance models were found and an analysis of these models was performed. Based on the analysis, a new model was proposed to ll the gap left by these studies. Results. New model measures every kind of reuse artifact and provides guidelines on how and what to measure in order to calculate reuse bene ts. This model was then validated in the industry and technology was transferred to the industry for future usage. Guidelines for improved savings were developed. Conclusions. We conclude that many models are related to each other and use similar techniques to measure the cost avoidance however they can not measure all kinds of reuse artifacts. New model performed well in industry. However, we found that the new model should accommodate maintenance costs since these are major savings by software reuse. Moreover, we conclude that there is a need for further validation of guidelines and model in industry.
node.node@gmail.com ; +46700183541 ;
APA, Harvard, Vancouver, ISO, and other styles
17

Gustafsson, Adam. "An Analysis of Platform Game Design : Implementation Categories and Complexity Measurements." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-35517.

Full text
Abstract:
This thesis addresses design and development associated problems identified within theplatform-game genre. The problem described originates from the fluctuating curve ofinterest towards the platform-game genre that can be observed between the 1980’s andtoday. The problem stated in this thesis is that modern platform-game developers mayoften overlook and –or deprioritize important design and gameplay related componentsthat we find reoccurring in previously popular games within the genre.This thesis strives to address such problems by decomposing the developmentprocess of a platform game into a light framework titled Implementation categories. Allincluded categories represent a set of design and development related platform-gamecomponents – primarily identified through previous research in the field. In order tocreate an understanding of each category’s complexity - as well as account for thepossibilities to use the categories as a guideline when developing a platform game - aprototype game was developed. The Implementation categories included in theprototype was then measured with a set of software complexity metrics. This thesis willmotivate and explain the selection of implementation categories, account for the usageof software complexity metrics as well as present a detailed documentation of theprototype development.The result of this thesis is a thorough presentation of the Implementation categories -attached with complexity examples for each category as well as a complete gameprototype. The complete results of this thesis will hopefully be of assistance in smallscale,independent or academic game projects in regard of design, decision making,prioritization and time planning.
APA, Harvard, Vancouver, ISO, and other styles
18

Malla, Prakash, and Bhupendra Gurung. "Adaptation of Software Testability Concept for Test Suite Generation : A systematic review." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4322.

Full text
Abstract:
Context: Software testability, which is the degree to which a software artifact facilitates process of testing, is not only the indication of the test process effectiveness but also gives the new perspective on code development. Since more than fifty percent of total software development costs is related to testing process activities, Software testability has always been the improving area in software domain so that we can make the software development process effective with respect to test cases writing and fault detection process. Objectives: The research though this thesis will have the objective of proposing a conceptual framework considering the testability issues for the simpler test suite generation and facilitating the concerned persons with better effectiveness of testing. We investigate the testability factors and testability metrics basically with the help of the systematic literature review and the proposed framework’s feasibility is evaluated with case study. Methods: Initially, we conduct the literature review to get broad knowledge on this domain as well for the key documents. Then study starts with the systematic literature review process guided by the review protocol to collect the testability factors and measurements. The framework is validated with the case study. The research documents are included from highly trusted e-database including Compendex, Inspec, IEEE Xplore, ACM Digital Library, Springer Link and Scopus. Altogether 36 primary documents are included for the study and results are extracted. Results: From the results of systematic literature review, Software testability factors and associated measurements are found and the construction of framework for simple test generation as guidelines evaluate with case study. To make the test suite generation simpler, we propped a framework based on the FTA concepts and breakdown of high level testability factors to its simpler form of measureable level. Conclusions: Numbers of different software testability factors are presented in different researches in different perspectives. We collect important testability factors and associated measurement methods and we concluded the effect of testability in simpler test suite generation with the help of framework evaluated by case study.
APA, Harvard, Vancouver, ISO, and other styles
19

Yazbek, Hashem [Verfasser]. "Framework of quality measurement in CASE tool based software development / von: Hashem Yazbek." 2010. http://d-nb.info/1010409085/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
20

Júnoš, Peter. "Flexible Event Processing Subsystem for the Java Performance Monitoring Framework." Master's thesis, 2015. http://www.nusl.cz/ntk/nusl-350896.

Full text
Abstract:
Java Performance Measurement Framework (JPMF) is a framework dedicated to description of points, where the performance is measured. This description is used to gather performance data in these running points. Data are gathered and written without any processing. The handling increases bandwidth and puts high load on the storage. JPMF does not provide any possibility for user to reduce this data. This thesis aims to solve the described problem by introduction of filtering and aggregation, that should reduce the bandwidth. Additionally, performance bottlenecks in various parts of JPMF are investigated and removed. Powered by TCPDF (www.tcpdf.org)
APA, Harvard, Vancouver, ISO, and other styles
21

Nzou, Viola. "Development of a framework to understand the factors that influence software productivity in agile teams." Diss., 2017. http://hdl.handle.net/10500/26007.

Full text
Abstract:
Productivity improvement in the software industry is one of the major challenges facing many software development companies in this century. Most companies have adopted agile methodologies in order to profit from the benefits claimed for them. Agile methodologies are characterised by frequent software delivery, short feedback loops, quicker response to change, and problem identification earlier in the development process. The agile approach has been recognised as paving a way for companies to acquire higher software productivity, delivering good-quality and cost-effective software, enabling software development companies to respond to business challenges with their demands for high quality, high performance and high development speed in delivering the final product. For companies that adopt agile methodologies, understanding the factors that influence their teams’ software development productivity is a challenging task for management and practitioners today. In this research, an analysis is presented that identifies productivity factors that affect agile teams. It is a study of agile methods to identify common agile practices and/or values that have impact on productivity, and describes suitable metrics that could be used to measure agile team productivity. A qualitative research approach was used, and the case study was chosen as the research strategy. Two South African companies that are located in two different provinces and that adopted agile methodologies in their software development, were selected for the case studies. Qualitative content analysis was used in the research to permit subjective interpretation of factors that influence agile team productivity, and to analyse to what extent these factors affected productivity. This research has shown that an understanding of the factors that influence an agile team’s productivity gives significant insight into the way agile teams work, motivates team members to work together, and leads to uniform metrics in tracking each team’s progress. The study indicates that tracking an agile team’s work and providing adequate tools needed to execute their tasks results in improving agile team productivity. It should be recognised that using metrics to measure performance in agile teams is helpful in creating a team’s culture and trust. In this study, it was found that the factors identified in both literature and case studies affected productivity in the two companies under study, both positively and negatively. The study also found that applying the correct metrics in assessing, analysing and reviewing an agile team’s performance is important when monitoring productivity. Successful software delivery is only possible if individuals are committed to their work, are provided with the necessary tools and have access to a stable working environment. In addition, individual factors such as knowledge, skills, abilities, personalities and experience should be considered when forming agile teams. Consideration of these factors will result in grouping people that are able to work together and achieve a common goal, which is important in improving productivity. A conceptual framework for agile team productivity was proposed. The discussion of the findings is presented in more detail in this research.
School of Computing
M.Sc. (Computing)
APA, Harvard, Vancouver, ISO, and other styles
22

Von, Gordon Albert Fredrich Johannes. "The design of a software architectural framework for tunnelling metering protocols over TCP/IP and low bandwidth packet switched networks with support for proprietary addressing." Diss., 2007. http://hdl.handle.net/2263/29032.

Full text
Abstract:
This document discusses the concept of drivers implemented within the context of the REMPLI (Real-Time Energy Management over Power line and Internet, see section 1.8.) network. The process image approach and the tunnelling approach are presented and reasoning is given why the tunnelling approach is preferred. Each of the drivers implemented is associated with a specific metering protocol. This document further discusses the general architecture of such a driver structure. The generic software architecture serves as a framework for integrating serial communication based metering protocols over packet-orientated remote networks and meters, by tunnelling the protocol data units to the remote meters. Principally each Protocol Driver consists of three parts, one part situated at the Application Server, one at the Access Point and one at the Node. This document then gives a description of the general driver structure within the REMPLI network and briefly explains the functions of all the modules contained within the driver structure. An example is used to show how these modules, which make up the software architecture of the Protocol Driver, are used to send an application generated request from the Application Server to the Metering Equipment and sending the response back from the remote Metering Equipment to the Application Server. This dissertation further discusses the need for address translation within the REMPLI network and the need to restrict access to meters by using these addresses and an access control list. This document also discusses the need for a “Keep-alive” signalling scheme, if supported by the underlying protocol and gives a general concept as to how it should be implemented. The role of an Optimization Module is also discussed for low bandwidth networks by means of an M-Bus example. Finally the M-Bus protocol driver implementation is discussed. The results achieved are presented, showing that the driver architecture can successfully be used to tunnel the M-Bus protocol to remote meters, provided the underlying network conforms to the quality of service requirements determined by the implemented metering protocol. The work proposed in this document started off as part of the REMPLI project by the REMPLI team but was completed independently.
Dissertation (MEng (Computer Engineering))--University of Pretoria, 2008.
Electrical, Electronic and Computer Engineering
unrestricted
APA, Harvard, Vancouver, ISO, and other styles
23

Tawakol, Abdel Maguid. "Performance Analysis of TCAMs in Switches." Thesis, 2012. http://hdl.handle.net/10012/6654.

Full text
Abstract:
The Catalyst 6500 is a modern commercial switch, capable of processing millions of packets per second through the utilization of specialized hardware. One of the main hardware components aiding the switch in performing its task is the Ternary Content Addressable Memory (TCAM). TCAMs update themselves with data relevant to routing and switching based on the traffic flowing through the switch. This enables the switch to forward future packets destined to a location that has already been previously discovered - at a very high speed. The problem is TCAMs have a limited size, and once they reach their capacity, the switch has to rely on software to perform the switching and routing - a much slower process than performing Hardware Switching that utilizes the TCAM. A framework has been developed to analyze the switch’s performance once the TCAM has reached its capacity, as well as measure the penalty associated with a cache miss. This thesis concludes with some recommendations and future work.
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography