Considerations on Language interpretation for microprocessor systems

Mackrodt, W.

doi:10.1016/0165-6074(81)90089-2

Cited by 2 publications

(1 citation statement)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…* translate the complete program and execute it later ('compilation'; Rechenberg, 1993); or * translate one statement (a 'minimally meaningful expression of the language'), execute it and then translate the next statement ('interpretation'; Mackrodt, 1981).…”

Section: Pre Hoc Versus Hocmentioning

confidence: 99%

The empty chair: uncertain futures and systemic dichotomies

Chroust¹

2004

Syst. Res.

View full text Add to dashboard Cite

One of the outstanding characteristics of Bela H. Banathy was his deep concern for designing better systems for future generations. In plenary meetings often an empty chair reminded us of our responsibility to the coming generations in designing the systems for a world to come. Systems designers often have a problem in making basic a priori assumptions about system choices without having sufficient information. We describe socalled systemic dichotomies: design decisions that have to choose between basic conflict pairs (like immediate or delayed enactment, optimistic versus pessimistic approaches). For each class we give several examples, mostly from software engineering. In concluding we show that certain of these dichotomies also have a meaning in social systems. This paper could be a starting point for the next generation of system scientists, for a closer investigation of such dichotomic dimensions, a study of their properties and a research into the interdependence of various such dichotomies.

show abstract

Section: Pre Hoc Versus Hocmentioning

confidence: 99%

The empty chair: uncertain futures and systemic dichotomies

Chroust¹

2004

Syst. Res.

View full text Add to dashboard Cite

show abstract

Choosing Basic Architectural Alternatives

Chroust

Schoitsch²

2009

Designing Software-Intensive Systems

View full text Add to dashboard Cite

When designing a complex software-intensive system it is unavoidable to make some a-priori basic assumptions about its architecture. We introduce so-called basic architectural alternatives as a means to guide these decisions and to understand their effects. These alternatives are classified according to five fundamental dimensions (enactment time, location, granularity, control, and automation and task distribution). For each dimension we describe some six typical, real examples of such an alternative. For each example we indicate fundamental properties of that alternative: elasticity with respect to later compromises, reversability of the choice (with resonable effort), uniformity requirements with respect to the different elements of in the system, and applicability of the chosen method accross the dimension. Finally, we discuss synergistic or contradictive effects of alternatives with respect to others. We hope that this analysis, together with the specific examples and their key properties, provide some insight for novices and seasoned designers and guides them during the early phases of system design.

show abstract

Considerations on Language interpretation for microprocessor systems

Cited by 2 publications

References 8 publications

The empty chair: uncertain futures and systemic dichotomies

The empty chair: uncertain futures and systemic dichotomies

Choosing Basic Architectural Alternatives

Contact Info

Product

Resources

About