Fire3: Architecture Refinement for A-posteriori Integration

Haase, Thomas; Meyer, Oliver; Böhlen, Boris; Gatzemeier, Felix H.

doi:10.1007/978-3-540-25959-6_37

Cited by 6 publications

(3 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Approaches to the step-wise refinement of software architecture evolution are presented in [30] and [31]. They assume refinements to be a set of changes that need to be made to the representation of an application or a system after a new feature is introduced or an (external) system is integrated.…”

Section: Architecture Refinementmentioning

confidence: 99%

“…They assume refinements to be a set of changes that need to be made to the representation of an application or a system after a new feature is introduced or an (external) system is integrated. For example, in [31] the authors describe Fire3, an architecture design tool that supports integration of external applications or systems. It starts form a coarse-grained integration architecture and refines it into more detailed component architecture.…”

Section: Architecture Refinementmentioning

confidence: 99%

See 1 more Smart Citation

MADCAT: A Methodology for Architecture and Deployment of Cloud Application Topologies

Inzinger

Nastić

Sehic

et al. 2014

2014 IEEE 8th International Symposium on Service Oriented System Engineering

View full text Add to dashboard Cite

Abstract-The cloud computing paradigm introduces new possibilities and challenges for application design and deployment. On-demand resource provisioning, as well as resource and cost elasticity, need to be considered when realizing largescale distributed applications for cloud environments. Current approaches do not sufficiently address the challenges of efficiently architecting and deploying cloud applications in a holistic manner and do not deal with the specific challenges encountered in cloud infrastructures. In this paper we introduce a methodology tackling the practical problems encountered when designing and deploying cloud applications. It enables the structured creation of cloud-native applications, addressing the complete application development lifecycle, from architectural design to concrete deployment topologies provisioned and executed on cloud infrastructure. By using iterative refinement and seamless provenance documentation of decisions made in the process, the methodology eases communication with relevant stakeholders and enables efficient design and deployment of distributed cloud applications.

show abstract

Section: Architecture Refinementmentioning

confidence: 99%

Section: Architecture Refinementmentioning

confidence: 99%

MADCAT: A Methodology for Architecture and Deployment of Cloud Application Topologies

Inzinger

Nastić

Sehic

et al. 2014

2014 IEEE 8th International Symposium on Service Oriented System Engineering

View full text Add to dashboard Cite

show abstract

“…Please note that we have actually implemented this approach, i.e., we have realized both the tools used for the tool development process and the integration tool between Comos PT and Aspen Plus [HMBG03b,BHWW02,Haa03].…”

Section: Tool Development Processmentioning

confidence: 99%

Model-based a-posteriori integration of engineering tools for incremental development processes

2005

Self Cite

View full text Add to dashboard Cite

A-posteriori integration of heterogeneous engineering tools supplied by different vendors constitutes a challenging task. In particular, this statement applies to incremental development processes where small changes have to be propagated -potentially bidirectionally -through a set of inter-dependent design documents which have to be kept consistent with each other. Responding to these challenges, we have developed an approach to tool integration which puts strong emphasis on software architecture and model-driven development. Starting from an abstract description of a software architecture, the architecture is gradually refined down to an implementation level. To integrate heterogeneous engineering tools, wrappers are constructed for abstracting from technical details and for providing homogenized data access. On top of these wrappers, incremental integration tools provide for inter-document consistency. These tools are based on graph models of the respective document classes and graph transformation rules for maintaining inter-document consistency. Altogether, the collection of support tools and the respective infrastructure considerably leverage the problem of composing a tightly integrated development environment from a set of heterogeneous engineering tools.

show abstract