"The booklet presents curated real-world good practice examples that help translate our strategy into concrete actions, and in turn, into the design of education and training programmes that will contribute to skill, upskill, or reskill individuals into high demand professional software roles."
LINK
Author supplied: Teaching software architecture (SA) in a bachelor computer science curriculum can be challenging, as the concepts are on a high abstraction level and not easy to grasp for students. Good techniques and tools that help with addressing the challenging SA aspects in a didactically responsible way are needed. In this tool demo we show how we used the software architecture compliance checking tool HUSACCT for addressing various concepts of SA in our courses on software architecture. The students were introduced to architectural reconstruction and architecture compliance checking, which helped them to gain important insights in aspects such as the relation between architectural models and code and the specification of dependency relations between architecture elements as concrete rules.
DOCUMENT
Many quality aspects of software systems are addressed in the existing literature on software architecture patterns. But the aspect of system administration seems to be a bit overlooked, even though it is an important aspect too. In this work we present three software architecture patterns that, when applied by software architects, support the work of system administrators: PROVIDE AN ADMINISTRATION API, SINGLE FILE LOCATION, and CENTRALIZED SYSTEM LOGGING. PROVIDE AN ADMINISTRATION API should solve problems encountered when trying to automate administration tasks. The SINGLE FILE LOCATION pattern should help system administrators to find the files of an application in one (hierarchical) place. CENTRALIZED SYSTEM LOGGING is useful to prevent coming up with several logging formats and locations. Abstract provided by the authors. Published in PLoP '13: Proceedings of the 20th Conference on Pattern Languages of Programs ACM.
DOCUMENT
My research investigates the concept of permacomputing, a blend of the words permaculture and computing, as a potential field of convergence of technology, arts, environmental research and activism, and as a subject of future school curricula in art and design. This concept originated in online subcultures, and is currently restricted to creative coding communities. I study in what way permacomputing principles may be used to redefine how art and design education is taught. More generally, I want to research the potential of permacomputing as a critical, sustainable, and practical alternative to the way digital technology is being taught in art education, where students mostly rely on tools and techniques geared towards maximising productivity and mass consumption. This situation is at odds with goals for sustainable production and consumption. I want to research to what degree the concept of permacomputing can be broadened and applied to critically revised, sustainable ways of making computing part of art and design education and professional practice. This research will be embedded in the design curriculum of Willem de Kooning Academy, focused on redefining the role of artists and designers to contribute to future modes of sustainable organisation and production. It is aligned with Rotterdam University of Applied Sciences sectorplan masters VH, in particular managing and directing sustainable transitions. This research builds upon twenty years of experience in the creative industries. It is an attempt to generalise, consolidate, and structure methods and practices for sustainable art and design production experimented with while I was course director of a master programme at WdKA. Throughout the research I will be exchanging with peers and confirmed interested parties, a.o.: Het Nieuwe Instituut (NL), RUAS Creating 010 kenniscentrum (NL), Bergen Centre for Electronic Arts (NO), Mikrolabs (NO), Varia (NL), Media Arts department at RHU (UK), Media Studies at UvA (NL).
