Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Exploring architectural analysis credibility from a developer perspective
KTH, Superseded Departments, Electrical Systems.
KTH, Superseded Departments, Electrical Systems.ORCID iD: 0000-0002-3293-1681
2002 (English)In: Proceedings of the Fourth Australian Workshop on Software and Systems Architecture, 2002Conference paper, Published paper (Refereed)
Place, publisher, year, edition, pages
2002.
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:kth:diva-5349OAI: oai:DiVA.org:kth-5349DiVA: diva2:9422
Conference
Fourth Australian Workshop on Software and Systems Architecture
Note
QC 20100621Available from: 2004-10-28 Created: 2004-10-28 Last updated: 2010-06-21Bibliographically approved
In thesis
1. Enterprise architecture for IT management: a CIO decision making perspective on the electrical power industry
Open this publication in new window or tab >>Enterprise architecture for IT management: a CIO decision making perspective on the electrical power industry
2004 (English)Doctoral thesis, comprehensive summary (Other scientific)
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

Place, publisher, year, edition, pages
Stockholm: Elektrotekniska system, 2004
Series
TRITA-ICS, ISSN 1104-3504 ; 0402
Keyword
Electronics, Enterprise architecture, Enterprise system, Chief information officer, Information technology management, Architectural theory, Electric power industry, Elektronik
National Category
Other Electrical Engineering, Electronic Engineering, Information Engineering
Identifiers
urn:nbn:se:kth:diva-36 (URN)
Public defence
2004-10-28, Kollegiesalen, KTH, Valhallvägen 79, Stockholm, 10:00
Opponent
Supervisors
Available from: 2004-10-28 Created: 2004-10-28 Last updated: 2014-07-17Bibliographically approved
2. Enterprise Software System Integration: An Architectural Perspective
Open this publication in new window or tab >>Enterprise Software System Integration: An Architectural Perspective
2002 (English)Doctoral thesis, comprehensive summary (Other scientific)
Place, publisher, year, edition, pages
Stockholm: KTH, 2002. 125 p.
Series
Trita-ICS, ISSN 1104-3504 ; 0202
Keyword
software archtecture, software integration, enterprise software systems, electric utilties, software engineering
Identifiers
urn:nbn:se:kth:diva-3365 (URN)
Public defence
2002-06-07, 00:00
Note
QC 20100621Available from: 2002-06-05 Created: 2002-06-05 Last updated: 2010-06-21Bibliographically approved

Open Access in DiVA

No full text

Authority records BETA

Johnson, Pontus

Search in DiVA

By author/editor
Johnson, Pontus
By organisation
Electrical Systems
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

urn-nbn

Altmetric score

urn-nbn
Total: 62 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf