This short note adds some results in parallel to those given in [1] on the random variable height on the set of watermelons with wall. In this paper we prove weak convergence results for the random variables “height” and “range” on the set of watermelons without wall restriction, as well as asymptotics for the moments of the random variable height. The techniques applied are quite similar to th...

This paper focuses on lessons that can be learned from looking at the history of traditional architecture. When architects stayed aloof from the common building activities during the Industrial Revolution, a low standard of building resulted, and the needs of the people were made subservient to the needs of industry. Can we apply lessons from traditional architecture to software? This paper ref...

We present the results of a multiple case study of how architects view and address the issues in transforming requirements into architectures in practice. Specifically we report how they view and address issues of requirements, architecture, and the transformation of requirements into architecture. We then summarize the important lessons learned from these practicing architects about this criti...

ion Organiser n Accuracy Methodical way of working Planning and organizing Interpersoonlijk Communicative competence Sensitivity and empathy

As new market opportunities, technologies, platforms, and frameworks become available, systems require large-scale and systematic architectural restructuring to accommodate them. Today’s architects have few tools and techniques to help them plan this architecture evolution. In particular, they have little assistance in planning alternative evolution paths, trading off various aspects of the dif...

This paper presents a domain-specific dependency constraint language that allows software architects to restrict the spectrum of structural dependencies that can be established in objectoriented systems. The ultimate goal is to provide architects with means to define acceptable and unacceptable dependencies according to the planned architecture of their systems. Once defined, such restrictions ...

TRADITIONALLY, SOFTWARE architects were entrusted with making “decisions that are costly to change.”1 Because these decisions often had to be made early in the project, architects drew on their experience and ability to abstract to get them right. Repeated project cost and timeline overruns have demonstrated, though, that trying to plan all features and decide the system structure early in a pr...