11th Asia-Pacific Software Engineering Conference
DOI: 10.1109/apsec.2004.2
|View full text |Cite
|
Sign up to set email alerts
|

A Comparative Analysis of Architecture Frameworks

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
71
0
15

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 76 publications
(87 citation statements)
references
References 9 publications
1
71
0
15
Order By: Relevance
“…Leading examples include: Zachman's Framework [Zachman, 1999]; The Reference Model for Open Distributed Processing (RM-ODP) and the Open Group's framework TOGAF and derivatives [Wisnosky andVogel, 2004, MoD, 2008]. Regardless of the specifics of the framework, as Tang et al note there are common deficiencies such as: (1) the level of detail required in an architecture model is not generally specified; (2) support, specification and management of non-functional requirements is lacking and (3) software configuration modeling is also generally lacking [Tang et al, 2004].…”
Section: Related Workmentioning
confidence: 99%
“…Leading examples include: Zachman's Framework [Zachman, 1999]; The Reference Model for Open Distributed Processing (RM-ODP) and the Open Group's framework TOGAF and derivatives [Wisnosky andVogel, 2004, MoD, 2008]. Regardless of the specifics of the framework, as Tang et al note there are common deficiencies such as: (1) the level of detail required in an architecture model is not generally specified; (2) support, specification and management of non-functional requirements is lacking and (3) software configuration modeling is also generally lacking [Tang et al, 2004].…”
Section: Related Workmentioning
confidence: 99%
“…Todas las arquitecturas analizadas incluyen en su marco de modelado la vista de información y sus relaciones con otras vistas (Tang et al, 2004;Cuenca et al, 2005;Boza et al, 2007). En algunas ocasiones se distingue entre el modelado de procesos de negocio y sus técnicas asociadas (Diagramas de flujo de proceso, IDEF0, Redes de Petri) y el modelado de sistemas de información (Diagramas de Flujo de datos, Diagramas Entidad Relación, UML), distinguiendo por tanto entre integración de la información e integración de procesos (Giaglis, 2001;Ni et al 2007).…”
Section: Introductionunclassified
“…EA is a coherent set of principles, methods and models used in the design of an enterprise's organisational structure, business processes, information systems and infrastructure (Lankhorst 2004). EA is the outcome, albeit an evolving one, of a strategic planning and management process to which an EA framework is applied to describe both the current (as-is) and future (to-be) states (Tang et al 2004).…”
Section: Enterprise Engineering and Enterprise Architecturementioning
confidence: 99%