Endre søk
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Consistent enterprise software system architecture for the CIO: a utility-cost based approach
KTH, Skolan för elektro- och systemteknik (EES), Industriella informations- och styrsystem.ORCID-id: 0000-0003-3922-9606
KTH, Skolan för elektro- och systemteknik (EES), Industriella informations- och styrsystem.ORCID-id: 0000-0002-3293-1681
KTH, Skolan för elektro- och systemteknik (EES), Industriella informations- och styrsystem.
KTH, Skolan för elektro- och systemteknik (EES), Industriella informations- och styrsystem.
Vise andre og tillknytning
2004 (engelsk)Inngår i: Proceedings of the 37th Annual Hawaii International Conference on System Sciences, 2004, 2004Konferansepaper, Publicerat paper (Fagfellevurdert)
Abstract [en]

Previously, business operations of most large companies were supported by a number of isolated software systems performing diverse specific tasks, from real-time process control to administrative functions. In order to better achieve business goals, these systems have in recent years been extended, and more importantly, integrated into a company-wide system in its own right, the enterprise software system. Due to its history, this system is composed of a considerable number of heterogeneous and poorly understood components interacting by means of equally diverse and confusing connectors. To enable informed decision-making, the Chief Information Officer (CIO), responsible for the overall evolution of the company's enterprise software system, requires management tools. This paper proposes enterprise software system architecture (ESSA) as a foundation for an approach for managing the company's software system portfolio. In order to manage the overwhelming information amounts associated with the enterprise software system, this approach is based on two concepts. Firstly, the approach explicitly relates the utility of knowledge to the cost of its acquisition. The utility of knowledge is derived from the increased value of better-informed decision-making. The cost of knowledge acquisition is primarily related to the resources spent on information searching. Secondly, the approach focuses on ensuring the consistency of the architectural model.

sted, utgiver, år, opplag, sider
2004.
Serie
Proceedings of the Hawaii International Conference on System Sciences, ISSN 1060-3425
Emneord [en]
Companies, Computer architecture, Connectors, Costs, Decision making, History, Portfolios, Process control, Real time systems, Software systems
HSV kategori
Identifikatorer
URN: urn:nbn:se:kth:diva-5350DOI: 10.1109/HICSS.2004.1265519Scopus ID: 2-s2.0-12344280935ISBN: 0-7695-2056-1 (tryckt)OAI: oai:DiVA.org:kth-5350DiVA, id: diva2:9423
Konferanse
Hawaii International Conference on System Sciences; Big Island, HI, USA, 5-8 January 2004
Merknad

QC 20141211

Tilgjengelig fra: 2004-10-28 Laget: 2004-10-28 Sist oppdatert: 2018-01-10bibliografisk kontrollert
Inngår i avhandling
1. Enterprise architecture for IT management: a CIO decision making perspective on the electrical power industry
Åpne denne publikasjonen i ny fane eller vindu >>Enterprise architecture for IT management: a CIO decision making perspective on the electrical power industry
2004 (engelsk)Doktoravhandling, med artikler (Annet vitenskapelig)
Abstract [en]

Within the electric power industry, the average company's enterprise system - i.e. the overall system of IT related entities - is today highly complex. Technically, large organizations posses hundreds or thousands of extensively interconnected and heterogeneous single IT systems performing tasks that varies from enterprise resource planning to real-time control and monitoring of industrial processes. Moreover are these systems storing a wide variety of sometimes redundant data, and typically they are deployed on several different platforms. IT does, however, not execute in splendid isolation. Organizationally, the enterprise system embraces business processes and business units using as well as maintaining and acquiring the IT systems. The interplay between the organization and the IT systems are further determined by for instance business goals, ownership and governance structures, strategies, individual system users, documentation, and cost.

Lately, Enterprise Architecture (EA) has evolved with the mission to take a holistic approach to managing the above depicted enterprise system. The discipline's presumption is that architectural models are the key to succeed in understanding and administrating enterprise systems. Compared to many other engineering disciplines, EA is quite immature in many respects. This thesis identifies and elaborates on some important aspects that to date have been overlooked to a large extent. Firstly, the lack of explicit purpose for architectural models is identified. The thesis argues that the concerns of a company's Chief Information Officer (CIO) should guide the rationale behind the development of EA models. In particular, distribution of IT related information and knowledge throughout the organization is emphasized as an important concern uncared for. Secondly, the lack of architectural theory is recognized. The thesis provides examples of how theory, or analysis procedures, could be incorporated into the Enterprise Architecture approach and hereby concretely drive the development of the architectural models. Due to the nature of enterprise systems, EA theories inevitable will be of an indicative character. Finally, in relation to the models as such, three aspects are highlighted. Firstly, the cost of collecting information from the organization to populate models is routinely neglected by the EA community. This expense should be evaluated in relation to the utility of analyses that the information can provide in terms of better informed decision making by the CIO. Secondly, models (and meta-models) must be kept consistent. And thirdly, the design of models is restricted by the limited mental capabilities of the minds of the model users. CIO concerns must consequently be easy to extract from the Enterprise Architecture models.

Key words: Enterprise Architecture, Enterprise System, Chief Information Officer (CIO), Information Technology (IT) Management, Architectural Theory, Electric Power Industry

sted, utgiver, år, opplag, sider
Stockholm: Elektrotekniska system, 2004
Serie
TRITA-ICS, ISSN 1104-3504 ; 0402
Emneord
Electronics, Enterprise architecture, Enterprise system, Chief information officer, Information technology management, Architectural theory, Electric power industry, Elektronik
HSV kategori
Identifikatorer
urn:nbn:se:kth:diva-36 (URN)
Disputas
2004-10-28, Kollegiesalen, KTH, Valhallvägen 79, Stockholm, 10:00
Opponent
Veileder
Tilgjengelig fra: 2004-10-28 Laget: 2004-10-28 Sist oppdatert: 2014-07-17bibliografisk kontrollert

Open Access i DiVA

Fulltekst mangler i DiVA

Andre lenker

Forlagets fulltekstScopus

Personposter BETA

Ekstedt, MathiasJohnson, Pontus

Søk i DiVA

Av forfatter/redaktør
Ekstedt, MathiasJohnson, PontusLindström, ÅsaGammelgård, MagnusJohansson, ErikPlazaola, LeonelSilva, EnriqueLiliesköld, Joakim
Av organisasjonen

Søk utenfor DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric

doi
isbn
urn-nbn
Totalt: 565 treff
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf