V této diplomové práci se zabývám problematikou návrhu business architektury s důrazem na možnost její implementace v reálném tržním subjektu. Práce obsahuje teoretickou část, která poskytuje metodická východiska, a část praktickou, ve které nejprve konstruuji vlastní metodiku návrhu a podle této metodiky pak provádím návrh business architektury subjektu realitního trhu za využití nástroje ProVison. Součástí práce jsou grafické výstupy a jejich popis.

Práce se snaží zhodnotit možnosti využití metodiky RUP při realizaci projektu vývoje konkrétního informačního systému s danými parametry. Těmito parametry jsou malý rozsah, webová platforma a technologické prostředí PHP 5. V úvodu se práce zaobírá úlohou metodik při vývoji software, následuje představení metodiky RUP. Dále je probírána metodická podpora specifických charakteristik projektů. Vlastním přínosem práce je vytvoření vlastní instance metodiky RUP vhodné pro definovaný projekt a na základě zkušeností s metodikou pak zhodnocení využitelnosti metodiky RUP pro daný projekt a návrh změn metodiky.

In this diploma thesis, I focus on the application integration. Main goal of this thesis is comparison of integration platforms of the biggest vendors on the market, there are products of companies Microsoft, IBM, Oracle and SAP. I compare these products according criteria, which I had chosen. I use mainly own experiences with the products to achieve a goal. These products I compare with respect to general, technological and possibility of using point of view. My work can be as a source for decision, which of the integration platforms is optimal to use. Then I describe one of them - Microsoft Biztalk Server with simple example. The next goal of this work is to summarize the theory of application integration, where I describe the possibilities of integration's application from the simplest till the most complicated. The next goal of this work is making a methodology in Biztalk Server, which will contain concrete solutions and techniques in different situations. This methodology can help developers and analysts to make better proposals, more convenient solutions and beware of needless problems.

The principle aim of this thesis is to create an unified methodical framework for a smaller Software Testing Department. Furthermore, its aim is to define and describe an important element of testing - the software mistake, define the way of its reporting and finally with the view of it to specify the troubleshooting areas of web applications. The last aim is to find a solution of how to publish this methodology. The aims of this thesis were reached by studying available theoretical findings and applications of principles that are known from notorious and approved methodologies which complexly focus on the software development. These principles were confronted with author's practical experience. Based on these processes, the methodology described above has been originated The contribution of the thesis is in the inner structure of the methodology, summarization of the most important information, application of practical personal experiences and adapting some elements of the methodology according to its usage in a small team. Other strong points are the proposals and recommendations of how to improve the situation on the testing department of a particular company, how to publish the methodology and how to maintain it in the future. The thesis is composed of three main parts. In the first chapter, the essential characteristics of testing, models of the life cycle of software development, sorts and levels of tests are given. The second chapter is the crucial part of the thesis. It describes the whole methodology - the main workflow and its details (processes), activities made during these processes, roles occurring in the methodology and the description of its responsibility (for activities and artefacts), artefacts made on the testing department, full description of mistake and its reporting and finally the summary of mistakes appearing in the web applications environment. The last chapter attends to the way of putting the methodology into operation - technical coverage of particular parts of the methodology in the present time, suggestion of improvement the testing in the future and possibilities of the publication of the methodology.

My thesis is aimed at the problems of Configuration Management. Configuration Management is part of managing of information science management. Being part of it, it is very well described in different methodologies aimed at management of information science. Configuration Management is concerned with monitoring of company assets. In information technology it means mainly hardware and software equipment which is being used by the company. Knowledge of exact configurations of all these assets is very important mainly for providing user support, deploying new implementations or running audits. Situation in companies dealing with IT is, that many of such companies do not use Configuration Management at all, on a limited scale or are using some substitute method. Management of these companies usually realizes that it would be good to somehow align problems aligned with using of larger quantities of hardware and software. Often it is a situation when company does not use any methodologies for IT management and thus does not know that something like Configuration Management even exists. Goal of my thesis is to help future users of Configuration Management. I am trying to achieve this goal by analyzing particular components of Configuration Management complemented by my work experiences - I have been engaged in Configuration and Change Management during the majority of the last three years.

The diploma thesis defines questions of multi level marketing. This business method still expands very fast among people, who look for new ways of growing their revenue. This thesis identifies reasons for long-term expansion especially in this branch. Simultaneously in the diploma thesis I describe way of communication during dealing with particular distributors. More this thesis involves manual for starting distributors in the branch of multi level marketing.

The thesis compares main widespread project management methodologies (PMBOK, PRINCE2) and Czech methodology tailored for specific turbulent environment in Czech Republic (EPMS). The philosophies, structures and approaches of all project management methodologies are described in this thesis. Main pros and cons of methodologies are briefly shown and important issues of their implementation are described in the thesis. The process-driven approach, which have all methodologies in common, is mapped to demanded processes of ČSN ISO 10006:2004.

The main objective of this thesis is to map some of the business process management, business process reengineering methodologies and compare it according to several criteria. Part of this thesis is survey of the state of business process management in Czech Republic and Hungary.

The main objective of this work is to critically evaluate a sufficient portion of the circuit problem of software piracy and to propose solutions of sub-problems, to use the interpretation of all relevant laws and all other available resources and create a comprehensive picture of the case. The practical part should be primarily a manual for ordinary computer users, which should help them. At the same time I present a preview of the methods of the executive law enforcement authority - Police of the Czech Republic, which deals with the investigation of software piracy. Range of the methods used in my work is not wide, which is partly due to reluctance of companies to cooperate because it is a relatively sensitive information, but it fully covers the needs of work and make it possible to have a final vision of the subject.

This diploma thesis defines the issue of software requirements engineering and the implementation of software requirement into IS/ICT projects. One of the aims is to highlight the importance of systematic requirements management to successful IS/ICT projects. The theoretical part of thesis includes requirements definition, requirements typology and qualitative parameters of good requirement and actors, that are involved into the process of requirements management. The practical part of this thesis defines the process of requirements management general accepted methodologies of as it is specified in the internationally recognizable methodologies. Author's own contribution is the definition of a methodological process for managing requirements specifications, based on rigorous methodologies and extended to reflect author's practical experience. Methodological approach is tailored to the needs of smaller software companies and small to medium scale IS / ICT projects, and, if necessary, is further extendable. Another practical benefit of this thesis is the recommended methodology for change management requirements. Proposal process is based on the ITIL set of best practices; sub-threads are adapted to be able to meet the change management requirements and the broader business environment infrastructure. This methodology emphasizes an individual approach to the requirement. There is a recommendation of appropriate software tools for development and management requirements support divided into partial ITIL processes.