Software Design and Architecture The once and future focus of software engineering

Taylor, Richard N.; Hoek, André van der

doi:10.1109/fose.2007.21

Cited by 61 publications

(37 citation statements)

References 53 publications

(47 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…According to Taylor and van der Hoek [10], as well as Jansen and Bosch [11], software architecture is a set of principal design decisions governing a system. During a software system's design phase, architects have to make numerous decisions for organizational and business issues, for matters of broad and detailed design, and for technologies [12].…”

Section: Reusable Architectural Decision Modelsmentioning

confidence: 99%

Reusable Architectural Decision Model for Model and Metadata Repositories

Mayr

Zdun

Dustdar

2009

Formal Methods for Components and Objects

View full text Add to dashboard Cite

Abstract. Models are gaining importance in software development, for instance in the MDD field, as well as in other disciplines such as biology and physics. Hence, tool support is needed to manage these models and metadata about the models. Model repositories support this trend by managing these model artifacts. While setting up model and metadata repositories, architects have to make several fundamental design decisions and balance various forces. In this paper we describe reusable knowledge in form of reusable architectural decisions for ITarchitects in setting-up, planning, and developing model and metadata repositories, as well as the main decision drivers. Our decisions are documented in a reusable architectural decision model that can be instantiated for a concrete system. It also supports a lightweight approach to architecture documentation. A case study illustrates the decisions made when setting up our own data access object model repository by walking through the reusable architectural decision model.

show abstract

Section: Reusable Architectural Decision Modelsmentioning

confidence: 99%

Reusable Architectural Decision Model for Model and Metadata Repositories

Mayr

Zdun

Dustdar

2009

Formal Methods for Components and Objects

View full text Add to dashboard Cite

show abstract

“…Then, models that comply with the selected notation can be effectively used to convey domain details to system designers, as input to model-driven software development tools [21,29], and for documenting the domain for future reference [17]. This central importance of notations is emphasized for instance in [70]:…”

Section: Introductionmentioning

confidence: 99%

“…Many characteristics have been proposed to study and compare notations, including expressive power [62], formal analysis capabilities [32], terseness [71], aesthetics [73], and usability [70,26]. The understandability of process models is of particular relevance for process-oriented design.…”

Section: Introductionmentioning

confidence: 99%

Making sense of business process descriptions: An experimental comparison of graphical and textual notations

Ottensooser

Fekete

Reijers

et al. 2012

Journal of Systems and Software

110

View full text Add to dashboard Cite

“…Curiosity about the nature of design in general, even though it may not have an immediate connection to practice, must be not simply tolerated, but encouraged and nourished. In that regard, it seems important to note that this volume itself contains a paper that explores the nature of software design, and its relation to the larger issue of design in general [24]. Papers dealing with curiosity-driven research of this kind must not be restricted only to the pages of special volumes such as this, but should become a staple of mainstream software engineering research venues, such as the proceedings of meetings such as the Foundations of Software Engineering and International Conference on Software Engineering as well.…”

Section: Question: What Is Design (The Noun)? and How Should It Be Pementioning

confidence: 99%

A Future for Software Engineering?

Osterweil

2007

Future of Software Engineering (FOSE '07)

View full text Add to dashboard Cite

Preamble"...we recognize that a practical problem of considerable difficulty and importance has arisen: The successful design, production and maintenance of useful software systems. The importance is obvious and the more so since we see only greater growth in demands and requirements in the future. The consequences of poor performance, poor design, instability and mismatching of promise and performance are not going to be limited to the computing fraternity, or even their nearest neighbors, but will affect considerable sections of our society whose ability to forgive is inversely proportional to their ignorance of the difficulties we face. The source of difficulty is distributed through the whole problem, easy to identify, and yet its cure is hard to pinpoint so that systematic improvement can be gotten.Our problem has arisen from a change of scale which we do not yet know how to reduce to alphabetic proportions. Furthermore we must assume that additional magnification of goal will take place without necessarily being preceded by the emergence of a satisfactory theory or an organized production of tools that will permit work and costs to fall on growth curves which lie significantly below those which now exist. For example, we can see coming the need for systems which permit cooperation, e.g., between engineering and management information. Not only must we know how to build special purpose systems, but how to combine them into larger ones." A.J. Perlis, 1968 [17].

show abstract

Software Design and Architecture The once and future focus of software engineering

Abstract: Abstract

Cited by 61 publications

References 53 publications

Reusable Architectural Decision Model for Model and Metadata Repositories

Reusable Architectural Decision Model for Model and Metadata Repositories

Making sense of business process descriptions: An experimental comparison of graphical and textual notations

A Future for Software Engineering?

Contact Info

Product

Resources

About