The present diploma thesis aims at introducing the Enterprise Architecture and creating an abstract model of a company. The primary focus is on application and process layers as defined in the architecture framework TOGAF. The thesis is divided into theoretical and practical part. The theoretical chapter starts with a business model analysis which means to describe mission vision and companys values as a part of the strategy framework. Furthermore the business processes are described in the latter part of this section. This chapter attempts to explain how to map a business process and to categorize it by nature and maturity level. Penultimate chapter introduces the Enterprise Architecture in general. This section includes arguments as to why the companies should be concerned with the Enterprise Architecture advantages of the Enterprise Architecture implementation into the companys documentation relationship of companys core business and IT and examples of the Enterprise Architecture frameworks. The last chapter deals with the TOGAF framework where Architecture Development Method is described. This means how Enterprise Architecture model is created and how to implement changes into the layers according to the TOGAF framework. Simultaneously the last section of this chapter describes the reference models which provide graphical overview of all abstractions layers. The practical part of the thesis elaborates on the theoretical part using the Architecture Development Method process in order to create the Enterprise Architecture model according to TOGAF framework. Same as the theoretical part it only focuses on the application and process layer. Firstly the business model is decomposed into vision mission and companys values to the companys strategy and business goals in order to grasp further understanding of business processes detailed description. Subsequently the abovementioned aspects are recomposed to create process map which provides the management overview. The application layer undergoes the same process; nonetheless the process map is replaced by information system description and reference model creation. Once the models are created the thesis compares them with the business and strategic goals. The benefit brought by this thesis is critical evaluation of current status to propose changes to achieve target architacture according business and strategic goals established by management.

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)