Metric collection process and Project Management activities cannot be performed in an integrated fashion on most of the software projects. In software engineering world, there are Project Management Tools that has embedded project metrics and there are various Metric Collection Tools that collect specific metrics for satisfying requirements of different software life cycle phase activities (Configuration Management, Requirements Management, Application Development tools etc.). These tools however are not communicating with each other with any interface or any common database. This thesis focuses on the development of a tool to define, export, collect and use metrics for software project planning, tracking and oversight processes. To satisfy these objectives, POMMES with functionalities of Generic Metric Definition, Collection, Analysis, and Import, Update and Export of Project Metrics from 3rd Party Project Management Tools is developed and implemented in a software organization during this thesis work.

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).

<p>The purpose of this thesis is to explore what software evaluation methods are currently available that can assist organizations and companies in procuring a software solution for some particular task or purpose for a specific type of business. The thesis is based on a real-world scenario where a company, Volvo Technology Corporation (VTEC), is in the process of selecting a new intellectual property management system for their patent department. For them to make an informed decision as to which system to choose, an evaluation of market alternatives needs to be done. First, a set of software evaluation methods and techniques are chosen for further evaluation. An organizational study, by means of interviews where questions are based on the ISO 9126-1 Software quality model, is then conducted, eliciting user opinions about the current system and what improvements a future system should have. The candidate methods are then evaluated based on the results from the organizational study and other pertinent factors in order to reach a conclusion as to which method is best suited for this selection problem. The Analytical Hierarchy Process (AHP) is deemed the best choice.</p>

The purpose of this thesis is to explore what software evaluation methods are currently available that can assist organizations and companies in procuring a software solution for some particular task or purpose for a specific type of business. The thesis is based on a real-world scenario where a company, Volvo Technology Corporation (VTEC), is in the process of selecting a new intellectual property management system for their patent department. For them to make an informed decision as to which system to choose, an evaluation of market alternatives needs to be done. First, a set of software evaluation methods and techniques are chosen for further evaluation. An organizational study, by means of interviews where questions are based on the ISO 9126-1 Software quality model, is then conducted, eliciting user opinions about the current system and what improvements a future system should have. The candidate methods are then evaluated based on the results from the organizational study and other pertinent factors in order to reach a conclusion as to which method is best suited for this selection problem. The Analytical Hierarchy Process (AHP) is deemed the best choice.

The main goal of diploma thesis is to propose a model for metrics description and metrics themselves, which will be used for different project areas effectiveness and performance evaluation during core banking systems implementation. The second goal is to describe metrics using MBI (Management of Business Informatics) model and compare results. The thesis has the next structure: - theoretical part, where main terms and research works which addressed to the same topic are described; -analytical part, where models for metrics description and metrics will be introduced; - conclusion, where results will be evaluated and models will be compared.