Reusability in software engineering

This paper surveys recent work concerning reusability in software engineering. The current directions in software reusability are discussed, and the two major approaches of reusable building blocks and reusable patterns studied. An extensive bibliography, parts of which are annotated, is included

Requirements for software engineering languages

This paper analyzes the concepts of software construction embodied in the Draco system. The analysis relates specific mechanisms in Draco to particular software engineering (SE) principles and suggests future research needed to extend the approach. The purpose of the analysis is to help researchers understand Draco better and thus be able to direct in productive directions future research on this type of software engineering tool

The SEC-system : reuse support for scheduling system development

Recently, in a joint cooperation of Stichting VNA, SAL Apotheken, the Faculty of Management and Organization, and the University Centre for Pharmacy, University of Groningen in the Netherlands, a Ph.D-study started regarding Apot(he)ek, Organization and Management (APOM). The APOM-project deals with the structuring and steering of pharmacy organization. The manageability of the internal pharmacy organization, and the manageability of the direct environment of pharmacy organization is the subject matter. The theoretical background of the APOM-project is described. A literature study was made to find mixes of objectives. Three mixes of objectives in pharmacy organization are postulated; the product mix, the process mix, and the customer mix. The typology will be used as a basic starting point for the empirical study in the next phase of the APOM-project.

Analysis of the Draco approach to constructing software systems

This paper analyzes the concepts of software construction embodied in the Draco system. The analysis relates specific mechanisms in Draco to particular software engineering (SE) principles and suggests future research needed to extend the approach. The purpose of the analysis is to help researchers understand Draco better and thus be able to direct in productive directions future research on this type of software engineering tool

Improving Introductory Computer Science Education with DRaCO

Today, many introductory computer science courses rely heavily on a specific programming language to convey fundamental programming concepts. For beginning students, the cognitive capacity required to operate with the syntactic forms of this language may overwhelm their ability to formulate a solution to a program. We recognize that the introductory computer science courses can be more effective if they convey fundamental concepts without requiring the students to focus on the syntax of a programming language. To achieve this, we propose a new teaching method based on the Design Recipe and Code Outlining (DRaCO) processes. Our new pedagogy capitalizes on the algorithmic intuitions of novice students and provides a tool for students to externalize their intuitions using techniques they are already familiar with, rather than with the syntax of a specific programming language. We validate the effectiveness of our new pedagogy by integrating it into an existing CS1 course at California Polytechnic State University, San Luis Obispo. We find that the our newly proposed pedagogy shows strong potential to improve students’ ability to program

Generating Requirements Views: A Transformation-Driven Approach

This paper reports the use of transformations based on XML to generate requirements views. A strategy to generate views is defined and scenarios and class diagrams are automatically created from a goal oriented model; the V-graph

Transformational maintenance by reuse of design histories

This thesis provides theory and procedures for modifying software artifacts implemented by a formal transformation process. Installing modifications requires knowing not only what transformations were applied (a derivation history) to construct the artifact, but also why the application sequence ensures that the artifact meets its specification. The derivation history and the justification are collectively called a design history. A Design Maintenance System (DMS), when provided with a formal change called a maintenance delta, revises a design history to guide construction of a new artifact. A DMS can be used to integrate a stream of deltas into a history, providing implementations as a side effect, leading to an incremental-evolution model for software construction.We provide a broadly applicable formal model of transformation systems in which specifications are performance predicates, subsuming the functional specifications which are traditional for transformation systems. Such performance predicates provide vocabulary used in the design history to describe the effect of applying sets of transformations.A nonprocedural, performance-goal-oriented Transformation Control Language (TCL) is defined to control navigation of the design space for a transformation system. Recording the execution of a TCL metaprogram directly provides a design history.A complete classification of, and representation for, the set of possible maintenance deltas is given in terms of the inputs defined by the transformation system model. Such deltas include not only specification changes, but also changes to implementation support technologies. Delta integration procedures for revising derivation histories given functional or support technology deltas are provided, based on rearranging the order of transformations in the design space. Building on these operations, integration procedures that revise the design history for each type of delta are described. An agenda-oriented TCL execution process dovetails smoothly with the integration procedures.Our DMS is compared to a number of other maintenance systems. By using an explicit delta and verified commutativity, our DMS often reuses transformations correctly when others fail

Um estudo sobre assistentes de especificação.

O AEsp é uma ferramenta para auxiliar a captura das especificações informais das aplicações do domínio de Administração Rural e transformá-las, incrementalmente, em uma representação que pode ser traduzida de forma automática para um programa executável. Esta ferramenta está sendo desenvolvida como parte do ambiente FMS ("Farm Management System"). O FMS é um ambiente para a geração automatizada de aplicativos no domínio de Administração Rural. O objetivo deste trabalho é fazer uma revisão bibliográfica dos assistentes de especificação existentes para auxiliar na especificação e dimensionamento do AEsp. Com este intuito foram descritos um conjunto de assistentes e um detalhamento do AEsp. Na seqüência, um conjunto de atributos, que serviram como crivo de comparação, foi proposto. Estes critérios foram aplicados sistematicamente a todos os assistentes.bitstream/item/107613/1/Rel-Tec-2-1997-estudo-assistentes.pd