2012
DOI: 10.1080/17517575.2011.625571
|View full text |Cite
|
Sign up to set email alerts
|

Application and project portfolio valuation using enterprise architecture and business requirements modelling

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
22
0
1

Year Published

2012
2012
2019
2019

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 39 publications
(23 citation statements)
references
References 6 publications
0
22
0
1
Order By: Relevance
“…The evaluation of EA products, architecture trade-off methods or the role for EA products in the IT acquisition and portfolio management processes were not brought up in the case (cf. Babar, Zhu, and Jeffery 2004;Ylimäki 2006;Boyd and Geiger 2010;Clerc, Lago, and Van Vliet 2007;Quartel, Steen, and Lankhorst 2012). Generally, the analysis of EA products was much simpler in practice than suggested by the myriad of complex technical analysis methods presented in the literature.…”
Section: Namementioning
confidence: 98%
See 2 more Smart Citations
“…The evaluation of EA products, architecture trade-off methods or the role for EA products in the IT acquisition and portfolio management processes were not brought up in the case (cf. Babar, Zhu, and Jeffery 2004;Ylimäki 2006;Boyd and Geiger 2010;Clerc, Lago, and Van Vliet 2007;Quartel, Steen, and Lankhorst 2012). Generally, the analysis of EA products was much simpler in practice than suggested by the myriad of complex technical analysis methods presented in the literature.…”
Section: Namementioning
confidence: 98%
“…Within the detailed studies, the use of EA artefacts in IT acquisition management (Boyd and Geiger 2010) and IT portfolio management (Quartel, Steen, and Lankhorst 2012) has been studied. However, the majority of the earlier research has focused on different types of formal EA model analysis methods for either analysing the current state (e.g.…”
Section: Related Researchmentioning
confidence: 99%
See 1 more Smart Citation
“…Usually, application architecture is specified on the basis of business architecture. Compared with business architecture, which possesses various assistant analysis ways and means such as (Glissmann and Sanz 2010) ArchiMate, Business Motivation Model (BMM), Business Process Model And Notation (BPMN) and so on (Quartel, Steen, and Lankhorst 2012), the design of application architecture is more dependent on the experience of the architect and the already-existing reference pattern. However, with the development of new technology such as service-oriented architecture (SOA) (Moshiri and Hill 2011;Longji 2011;Lewis, Smith, and Kontogiannis 2010) and cloud computing (Li et al 2012(Li et al , 2013, in order to meet the increasingly high requirement for agility in application architecture design, proper description framework and the corresponding design method of various architectural models must be developed for this architecting purpose.…”
Section: Introductionmentioning
confidence: 99%
“…A arquitetura de um sistema de informação é relevante pois todos os SI estão inseridos num contexto, assim, as organizações assumem-se como entidades em constante mudança e evolução. Este processo de mudança está inerentemente dependente de um conhecimento da arquitetura que suporta cada um dos SI de uma organização, pois só assim poderemos antecipar os impactos negativos muitas vezes associados à mudança (Quartel, Steen, & Lankhorst, 2012).…”
Section: Introductionunclassified