Specifics of projects in the area of Enterprise Architecture development

Abstract

Dmitrij V. Koznov - Associate Professor, Department of Software Engineering, Saint Petersburg State UniversityAddress: 28, Universitetsky Prospect, Stary Peterhof, St. Petersburg, 198504, Russian FederationE-mail: st008149@spbu.ruMaxim Yu. Arzumanyan- Assistant Professor, Department of Information Technologies in Economics,The Bonch-Bruevich Saint Petersburg State University of Telecommunications;Smart Architects Ltd.Address: 22, Prospect Bolshevikov, St. Petersburg, 193232, Russian FederationE-mail: maxim.arzumanyan@gmail.comYury V. Orlov - General Director, Smart Architects Ltd.Address: 61A, Moyka, St. Petersburg, 191186, Russian FederationE-mail: yury.orlov@smartarchitects.ruMaxim A. Derevyanko - Engineer, Department of Information Technologies in Economics, The Bonch-Bruevich Saint Petersburg State University of Telecommunications; Smart Architects Ltd.Address: 22, Prospect Bolshevikov, St. Petersburg, 193232, Russian FederationE-mail: maxim.derevyanko@gmail.comKonstantin Yu. Romanovsky - Senior Lecturer, Department of Software Engineering, Saint Petersburg State UniversityAddress: 28, Universitetsky Prospect, Stary Peterhof, St. Petersburg, 198504, Russian FederationE-mail: k.romanovsky@spbu.ruAnastasia A. Sidorina -Student, Department of Computer Science, Saint Petersburg State UniversityAddress: 28, Universitetsky Prospect, Stary Peterhof, St. Petersburg, 198504, Russian FederationE-mail: sidorina-nastia@mail.ru Enterprise Architecture (EA) is a discipline for business and IT system management, describing the fundamental artifacts of business and IT. Introducing EA activities in a company is done via special projects (referred to as EAMprojects). While much research focuses on EA as is, EAM projects are not yet considered properly. This paper deals with EAM projects as a special kind of IT project. The definition of an EAM project is suggested using the IT solution concept ofthe Microsoft Solution Framework. This is justified, since the EAM-software introduced in a company is the main result of a typical EAM project. Based on the definition of a work product in CMMI, this paper introduces the final delivery of an EAM project. In addition, domain specific modeling is used to describe EAM project delivery, since the most important partof EA is concepts and terms for describing business and IT in a company. To implement the language formed by these termsand concepts, an EAM tool is selected and customized (Mega, IBM System Architects, Aris, etc.), and additional software (i.e. Web-portal, integration scripts, etc.) is implemented. All of the EA principles and methods could be considered as guidelines for this software (EAM tool and additional software). Final delivery of an EAM project is divided into the following parts: method (domain specific language, EA method, EA process, integration, modeling results), technology (EAM tool, additional software, documentation), support and training. Using the concepts introduced in this paper, four EAM projects are analyzed. Lack of support of the EA method is identified as a common problem of these projects.