The goal of this thesis is to create a proposal of framework which can be used to support software quality management in a small development company. Framework is composed of processes, methodologies and tools which together should improve the quality of software products of a company. Concrete implementation of the framework is shown as a case study. Data for the case study were collected in the company Cleverbee, where the author worked during the case study's creation. Personal contribution of the author of the thesis is firstly the creation of the framework concept based on author's experiences and commented list of concrete results of framework's implementation. The detailed goal setting for this thesis and the definition of the target reader can be found in the chapter 1. Introduction. The definition of main terms, which will appear in the rest of the thesis, is contained in the chapter 2. Terms. Chapter 3. Software quality and its definition is explains the term "software quality" and the nature of the small companies. Chapter 4. Software quality management forms the theoretical foundation of the thesis. In this chapter you find how the methodologies RUP and CMMI view the software quality. Chapter 5. Framework concept contains the concept of the software quality management framework. Framework is based upon relevant sources and also author's personal experience. The chapter 6. Case study describes the concrete example of the implementation of the proposed framework. The case study also contains descriptions of the used software tools. The chapter 7. Conclusion contains the brief resume of the findings of the thesis.

The thesis is focused on the role of assurance within project management standards. Firstly, the theoretical role of assurance was established based on the performed research. Three main areas of interest have been identified: Assurance over business, the project itself and the product. The role established in the theoretical part of the work was subsequently compared to information systems development methodologies and project management standards. From the comparison with AUP, Scrum and FDD methodologies, it seems that the better assurance is defined, the longer the feedback cycle is. During the comparison with the three most widespread project management standards - IPMA, PRINCE2 and PMBOK - various areas have been identified where these are not fully compliant with the theoretical role of assurance. Additions to IPMA and PMBOK have been created to support the compliance with the theoretically established role of assurance, fulfilling the objective set for the practical part of the work and providing benefits to IT project management professionals that struggle to deliver quality products while following one of the aforementioned standards.

This thesis examines integration testing of object-oriented software. The process of integrating and testing procedural programs is reviewed as foundation for testing object-oriented software. The complexity of object-oriented software is examined. The relationship of integration testing and the software development life cycle is presented. Scenarios are discussed which account for the introduction of defects into the software. The Unified Modeling Language (UML) is chosen for representing pre-implementation and post-implementation models of the software. A demonstration of the technique of using post-implementation models representing the logical and physical views as an aid in integration and system testing of the software is presented. The use of UML diagrams developed from the software is suggested as a technique for integration testing of object-oriented software. The need for automating the data collection and model building is recognized. The technique is integrated into the Revised Spiral Model for Object-Oriented Software Development developed by du Plessis and van der Walt. / Computing / D.Phil. (Computer Science)

This thesis examines integration testing of object-oriented software. The process of integrating and testing procedural programs is reviewed as foundation for testing object-oriented software. The complexity of object-oriented software is examined. The relationship of integration testing and the software development life cycle is presented. Scenarios are discussed which account for the introduction of defects into the software. The Unified Modeling Language (UML) is chosen for representing pre-implementation and post-implementation models of the software. A demonstration of the technique of using post-implementation models representing the logical and physical views as an aid in integration and system testing of the software is presented. The use of UML diagrams developed from the software is suggested as a technique for integration testing of object-oriented software. The need for automating the data collection and model building is recognized. The technique is integrated into the Revised Spiral Model for Object-Oriented Software Development developed by du Plessis and van der Walt. / Computing / D.Phil. (Computer Science)

Nowadays the development speed of new software products is a key to success and it is not important whether the aim is to make customer's urges satisfied or get ahead of one's competitors and fill the market gap. Because of the increase of development speed the demands on the saving process of software quality are increasing. There are two types of tools that are supporting the process of software quality assurance. Firstly, we talk about comprehensive testing tools of commercial character that usually include many functions, but their purchase is extremely expensive. On the other hand there are open-source tools that are available for free, they function on many kinds of operating systems and it is possible to modify them. Unfortunately their functions are basically focused on a certain subset of controlling the software quality assurance. Company TRASK solution a.s. has decided to change this current situation, so it asked competence centre Software Quality Assurance at the University of Economics in Prague in order to create Integrated Testing Node (ITN) that would combine the advantages of open-source tools. Moreover, it would offer broad range of functions as commercial solution. The purpose of this thesis is to describe relevant phases of the process of creating the Integrated Testing Node from the factual and methodical point of view. This aim is divided into partial aims included task analysis and the proposal of solving system, open-source products portfolio analysis, choice of the most convenient tools for following integration, choosing the method of information system building, evaluating the feedback from a client and the proposal of future development of this tool. As far as the biggest contribution of this thesis is concerned, it is the realisation of ITN project that can be used during information classes at the University of Economics in Prague. Furthermore, it can be used as the control of software quality in commercial companies.

This thesis deals with project management competence center in Software Quality Assurance, which operates the University of Economics in Prague. The first part of this thesis is focused on basic terminology management projects and projects aimed at testing. The second part focuses on project management competence center in Software Quality Assurance, which describes a modified project life cycle according to the PMBOK and project life cycle testing. All phases of the lifecycle contain sub-activities and the person responsible for the activity. The last part of this thesis is focused on management competency center Software Quality Assurance tool available for cooperation IBM Connections, which is available for students and staff of the University of Economics in Prague. The thesis is a complex material intended primarily for manager competency center, its teams and includes guides on how to manage the very center and its projects.