IT Business Standards as an Ontology Domain

Czarnecki, Adam; Orłowski, Cezary

doi:10.1007/978-3-642-23935-9_57

Cited by 9 publications

(4 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…IT projects are unique by definition and they can determine a number of different decisions, depending on a variety of external conditions (e.g., client maturity, requirements regarding the scope of work, budget constraints) as well as internal ones (available resources, experience) (Czarnecki and Orłowski 2011). For some of these variables, it is impossible to obtain a quantitative sample to calculate probability because they have a qualitative character.…”

Section: The Application Of Soeks In the Processes Of Constructing Dementioning

confidence: 99%

Experience-Driven Model of Decision-Making Processes in Project Teams

Orłowski

Sarzynski

Sitek

et al. 2015

Cybernetics and Systems

Self Cite

View full text Add to dashboard Cite

Section: The Application Of Soeks In the Processes Of Constructing Dementioning

confidence: 99%

Experience-Driven Model of Decision-Making Processes in Project Teams

Orłowski

Sarzynski

Sitek

et al. 2015

Cybernetics and Systems

Self Cite

View full text Add to dashboard Cite

“…The scope of the enterprise architecture includes the people, processes, information and technology of the enterprise, and their relationships to one another [4]. The Open Group Architecture Framework document specifies a detailed method and a set of supporting tools for developing Enterprise Architecture and authors have chosen TOGAF as an example of the standard that combines business and technical threads [7]. TOGAF defines three architecture domains: business architecture, information systems architecture and technology architecture [6].…”

Section: Enterprise Architecture Core Requirementsmentioning

confidence: 99%

“…The TOGAF content metamodel introduces the relevant concepts of the architecture represented in entities and key relationships that support architectural traceability [7]. These entities incorporate most of the enterprise architecture components and the content metamodel shows the relations between them.…”

Section: Enterprise Architecture Core Requirementsmentioning

confidence: 99%

See 1 more Smart Citation

Cities as Enterprises: A Comparison of Smart City Frameworks Based on Enterprise Architecture Requirements

2017

View full text Add to dashboard Cite

Abstract. There is a significant challenge in the smart cities implementation because it is not straightforward to align the smart city strategy with the impact on the life of quality. Stakeholders' concerns are multiple and diverse, and there are a high interdependency and heterogeneity of technologies and solutions. To tackle this challenge, cities can be understood as enterprises. Enterprise Architecture (EA) approach can be applied to support its development and transformation. This approach specifies core requirements on business, information, and technology domains, which are essential to model architecture components and to establish relations between these domains. Existing smart cities frameworks describe different components and domains. However, the main domain requirements and the relations between them are still missing. This paper identifies essential requirements of enterprise architecture in smart cities. These requirements will be used to review and compare current smart city frameworks.

show abstract