A CASE Tool for Software Architecture Design

Ng, Keng; Kramer, Jeff; Magee, Jeff

doi:10.1007/978-1-4613-1439-4_5

Cited by 10 publications

(3 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this context, so-called software architecture design assistants (e.g., [18,17,16,13]) provide architects with a toolbased, (semi-)automated support in their engineering tasks. Compared to manual engineering, the main promise of such a support is that architects can create high-quality architectural designs more efficiently.…”

Section: Introductionmentioning

confidence: 99%

Software Architecture Design Assistants Need Controlled Efficiency Experiments

Lehrig

Becker

2015

Proceedings of the 1st International Workshop on Future of Software Architecture Design Assistants

View full text Add to dashboard Cite

Software architects use so-called software architecture design assistants to get tool-based, (semi-)automated support in engineering software systems. Compared to manual engineering, the main promise of such a support is that architects can create high-quality architectural designs more efficiently. Yet, current practice in evaluating whether this promise is kept is based on case studies conducted by the original authors of respective design assistants. The downside of such evaluations is that they are neither generalizable to thirdparty software architects nor can be used for quantitative efficiency comparisons between competing design assistants.To tackle this problem, we investigate how researchers can apply controlled experiments for evaluating the impact of software architecture design assistants on the efficiency of architects. For our investigation, we survey related controlled experiments. Based on this survey, we derive lessons learned in terms of best practices and challenges for such experiments.

show abstract

Section: Introductionmentioning

confidence: 99%

Software Architecture Design Assistants Need Controlled Efficiency Experiments

Lehrig

Becker

2015

Proceedings of the 1st International Workshop on Future of Software Architecture Design Assistants

View full text Add to dashboard Cite

show abstract

“…The Software Architect's Assistant [14] (SAA) is another example of a support tool for software architects. SAA main concern is composition of distributed architectures using component libraries.…”

Section: Reactive Architecture Toolmentioning

confidence: 99%

Reactive architectures with architectural agents

Anderson

Lennartsson²

Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Ful

View full text Add to dashboard Cite

This paper discusses dynamic reconfiguration of applications at the architectural level. Current work on dynamic aspects of software architectures has focused on planned reconfigurations controlled from the outside. In this paper we present a different approach, using architectural agents. The agent-enabled architecture descriptions will be executable and have a mechanism to describe reconfiguration events. The agents can be used during design and directly reused in the implementation phase. We also describe the properties of an initial implementation of the Reactive Architecture Tool, which provides support for design and implementation of reactive architectures.

show abstract

“…For modeling our case study, we used the ADL Darwin [9], [10]. Darwin is a declarative language, which supports the modeling of a system as a set of loosely coupled, context-independent software components, which communicate to achieve an overall goal.…”

Section: Architecture Description Languages (Adls)mentioning

confidence: 99%

Describing software architectures by system structure and properties

Eixelsberger

Gall²

Proceedings. The Twenty-Second Annual International Computer Software and Applications Conference (Compsac '98) (Cat. No.98CB 3

View full text Add to dashboard Cite

To support architecture-based development, different modeling notations and languages, so-called architecture description languages (ADLs), have been designed. To be of help in the development process, software architectures must be described in a complete and consistent manner but without being overloaded with information provided to the system stakeholders. Current architecture description languages provide information about software architectures in a domain independent way. This may lead to inappropriate and incomplete descriptions of software architectures. In this paper, we introduce a flexible and extensible language called Architecture Structure Description Language (ASDL) developed for describing structural aspects of software architectures and their properties. We thereby focus on the domain of embedded real-time systems that have to meet certain timing and safety constraints. The language was developed in an architecture recovery process of a realworld Train Control System (TCS) and has been used to describe and reason about TCS's architecture.

show abstract

A CASE Tool for Software Architecture Design

Cited by 10 publications

References 12 publications

Software Architecture Design Assistants Need Controlled Efficiency Experiments

Software Architecture Design Assistants Need Controlled Efficiency Experiments

Reactive architectures with architectural agents

Describing software architectures by system structure and properties

Contact Info

Product

Resources

About