20 research outputs found
Constraints for behavioural specifications
Get PDFBehavioural specifications with constraints for the incremental development of algebraic specifications are presented. The behavioural constraints correspond to the completely defined subparts of a given incomplete behavioural specification. Moreover, the local observability criteria used within a behavioural constraint could not coincide with the global criteria used in the behavioural specification. This is absolutely needed because, otherwise, some constraints could involve only non observable sorts and therefore have trivial semantics. Finally, the extension operations and completion operations for refining specifications are defined. The extension operations correspond to horizontal refinements and build larger specifications on top of existing ones in a conservative way. The completion operations correspond to vertical refinements, they add detail to an incomplete behavioural specification and they do restrict the class of models.Postprint (published version
Ordocoordinación: cómo organizar 700 estudiantes en un nuevo campus (y no morir en el intento)
Get PDFSince Autumn Term 2017 the Department of Computer Science of the Universitat Politecnica de Catalunya UPC-BarcelonaTech is in charge of teaching ”Fundamentals of Programming” in the new DiagonalBeso ´s Campus, at EEBE School. This new endeavour had to face two particular challenges: First, due to organizing constraints, it had to be organized at the same time it was being first taught. Second, all the numbers involved were large. In effect, in Autumn Term 2017, 686 students enroled, with a teaching staff of 18 instructors, and 108 laboratory tests being prepared. To deal with these challenges, we agreed to coordinate ourselves in a particular way which we name ordocoordination. We define ordocoordation as a flexible and quick particular way of coordination in which teachers generate and agree on a minimum set of rules. It is a bottom-up procedure, requiring taking quick decisions. As a consequence of applying this particular coordination, the number of sent emails has been a large one: in Autumn Term 2017: 350 ×18 = 6300 emails were interchanged. We believe that this approach deserves to be reported, and also that it is relevant to other subjects.A partir del Q1 de 2017 el Departamento de CS de la UPC se ocupa de la docencia de Informática I en el nuevo campus de la EEBE. Dicha docencia ha sido singular en dos aspectos. Primero, hubo que organizarla al mismo tiempo que se impartía. Segundo, todos los números son grandes. En el Q1 de 2017, hubo 686 estudiantes matriculados, 18 docentes y se prepararon 108 exámenes de laboratorio. Para tratar con estas singularidades hemos adoptado una forma de coordinación a la que hemos llamado ordocoordinación. Es una coordinación flexible y rápida en la que los docentes generan y consensúan un conjunto mínimo de reglas. Es de abajo a arriba y requiere una toma de decisiones ágil, por lo que el número de emails ha sido importante. En Q1 de 2017: 350 x 18 = 6300 emails. Creemos que esta aproximación merece ser explicada y que puede ser aplicada a otras asignaturas.Peer ReviewedPostprint (published version
Anotaciones de Merlín, comportamiento de universos y semántica algebraica
No full textEn este trabajo se presentan las ideas básicas seguidas para el diseño de un lenguaje de anotaciones para el lenguaje de programación Merlín. En concreto, las anotaciones se prevén en forma de especificaciones ecuacionales ligadas a los universos (construcción modular básica de Merlín), tanto a su componente de interfaz como a su componente de implementación. De cara a definir la semántica del lenguaje de anotaciones se ha optado por una semántica algebraica de comportamiento, en la que ciertas componentes son interpretadas inicialmente.The basic ideas for the design of an annotation language for the programming language Merlin are presented. A new semantics based on behaviour is introduced to formally define annotations.Postprint (published version
A module concept within the initial behaviour framework
No full textA module concept is defined which anables the description of the whole design of software systems, that is, not only the specifications of problem requirements but also the specification of the process of implementation design. Moreover, this concept encapsulates (like in packages and similar constructions) both the interface and implementation parts. This module concept is based on a behaviour approach where the notion of implementation coincides with realization of the behaviour, that is, an abstract data type implements another if reproduces its behaviour. For that a special kind of signature morphism, called implementation morphism, is introduced in order to formalize this realization of a behaviour idea and it is shown that implementation defined in this way is compatible with parameter passing
