Five Considerations for Software Architecture, Part 1

Buschmann, Frank; Henney, Kevlin

doi:10.1109/ms.2010.72

Cited by 10 publications

(8 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Patterns represent the collective experience of software experts and allow for the cost effective implementation of software's non-functional requirements reducing development cost from 10%-35%, improving time to market up to 20%, and reducing maintenance costs by 15%-20% [6]. Proven message exchange patterns (MEP) patterns are used similarly in enterprise landscapes to integrate services and applications without harming system runtime (e.g.…”

Section: Integration Patterns and Related Workmentioning

confidence: 99%

Cloud Integration Patterns

Merkel¹,

Santas

Heberle

et al. 2015

Service Oriented and Cloud Computing

View full text Add to dashboard Cite

Section: Integration Patterns and Related Workmentioning

confidence: 99%

Cloud Integration Patterns

Merkel¹,

Santas

Heberle

et al. 2015

Service Oriented and Cloud Computing

View full text Add to dashboard Cite

“…Our proposed architecture is based on a layer structure. The layered architecture makes each layer given different responsibilities available within the group [ 49 ], thereby forming a modular cloud system.…”

Section: Cloud Architecturementioning

confidence: 99%

Usalpharma: A Cloud-Based Architecture to Support Quality Assurance Training Processes in Health Area Using Virtual Worlds

García-Peñalvo

Cruz-Benito

Maderuelo

et al. 2014

The Scientific World Journal

View full text Add to dashboard Cite

This paper discusses how cloud-based architectures can extend and enhance the functionality of the training environments based on virtual worlds and how, from this cloud perspective, we can provide support to analysis of training processes in the area of health, specifically in the field of training processes in quality assurance for pharmaceutical laboratories, presenting a tool for data retrieval and analysis that allows facing the knowledge discovery in the happenings inside the virtual worlds.

show abstract

“…The C4A methodology is an attempt, based on best practices, to address the five architectural concerns presented in [6][7], namely economy, visibility, spacing, symmetry, and emergence.…”

Section: Analysis and Design Processmentioning

confidence: 99%

“…The rendering adjustments adapt the interface to a particular device type or presentation technology, such as mobile, tablet or desktop, browser, Linux or Windows, flash or AJAX, etc. Therefore, this view supports the "View" in the Model-View-Controller design pattern [6] [7], whereas "Model" and "Controller" are part of the Business Logic Layer (see below). User interface and human factors design are part of this layer's best practices.…”

Section: Fig 4 the 4x6 Layout For The "Hello World" Solutionmentioning

confidence: 99%

“…This specification expresses the various components, dependencies and design patterns using a graph-based data model (or "architecture catalog") and blueprint, the latter expressed as both a diagram and XML document. This structured approach enables a software product line assembly [6][7] of reusable patterns and components, with increasing development efficiency over time, and applicable to a whole domain, solution, sub-system, product, or a single component.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

The 4x6 Tiered Architecture Method: An Approach to the Design of Enterprise Solutions

Hadar¹,

Hadar

Silberman³

et al. 2012

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Enterprise architecture software design is all about composing applications to assemble value-added solutions rather than standalone products. Yet, each product and technology may have been designed and developed separately because of software engineering practices, management control over the deliverables, or technology acquisitions. To promote efficient assembly, solutions must be architected in a similar style, adhering to fundamental design principles while leveraging capabilities available in modern environments and relevant platforms. Furthermore, business agility and cost requirements dictate the identification of common capabilities and their development as reusable components across products and solutions. The 4x6 Tiered Architecture Method presented in this paper imposes a structured design, in terms of steps to follow, structure and documentation, for the logical view of an enterprise solution. Application of the 4x6 method to the analysis of an enterprise solution yields a six-tiered architecture structure and an abstract architecture specification. This specification expresses the various components, dependencies and design patterns using a graph-based data model (or "architecture catalog") and blueprint, the latter expressed as both a diagram and XML document. The 4x6 Method has been applied in practice; this experience indicates that this method results in higher quality architecture and requires lower effort for both constructing and reviewing the architecture and its documentation.

show abstract

Five Considerations for Software Architecture, Part 1

Cited by 10 publications

References 2 publications

Cloud Integration Patterns

Cloud Integration Patterns

Usalpharma: A Cloud-Based Architecture to Support Quality Assurance Training Processes in Health Area Using Virtual Worlds

The 4x6 Tiered Architecture Method: An Approach to the Design of Enterprise Solutions

Contact Info

Product

Resources

About