An Empirical Investigation of the Utility of ‘pre-CIM’ models

that, by allowing a variety of stakeholders to take part in modelling, projects will be both more efficient than traditional approaches and will produce software that meets the needs of those stakeholders. This will be facilitated by transforming initial (CIM), models to design (PIM) and implementation (PSM). However, it follows that to gain fully from this strategy the initial models, which are the major driver for communication and validation of requirements and business needs, must be appropriate to this usage. The VIDE project was an EC funded project which produced a successful model driven development tool-set, incorporating a variety of modelling capabilities, at each stage of the MDA process. Aside from support for model transformations, one of the motivations for VIDE was to provide accessible models for those stakeholders representing the client (or business) who may not share the modelling perspective and experience of software engineers. This paper reports upon an empirical study which attempts to assess whether our proposed ‘pre-CIM’ models provide a more palatable starting point for users. In brief, our results suggest that the pre-CIM notation provides an accessible starting point for modelling, and enhance the modeller’s experience whilst also suggesting that the use of the notation may have a positive impact on the quality of subsequent models

Critical comments on the constancy of the speed of light

Criticisms on the theory of the constancy of the speed of light are answered. It is shown that the new theory is not logically inconsistent for the reasons expressed

Comprehension, Use Cases and Requirements

Within requirements engineering it is generally accepted that in writing specifications (or indeed any requirements phase document), one attempts to produce an artefact which will be simple to comprehend for the user. That is, whether the document is intended for customers to validate requirements, or engineers to understand what the design must deliver, comprehension is an important goal for the author. Indeed, advice on producing ‘readable’ or ‘understandable’ documents is often included in courses on requirements engineering. However, few researchers, particularly within the software engineering domain, have attempted either to define or to understand the nature of comprehension and it’s implications for guidance on the production of quality requirements. In contrast, this paper examines thoroughly the nature of textual comprehension, drawing heavily from research in discourse process, and suggests some implications for requirements (and other) software documentation. In essence, we find that the guidance on writing requirements, often prevalent within software engineering, may be based upon assumptions which are an oversimplification of the nature of comprehension. Furthermore, that these assumptions may lead to rules which detract from the quality of the requirements document and, thus, the understanding gained by the reader. Finally the paper suggests lessons learned which may be useful in formulating future guidance for the production of requirements documentation

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

The Double Slit Experiment With Polarizers

The double slit experiment provides a standard way of demonstrating how quantum mechanics works. We consider modifying the standard arrangement so that a photon beam incident upon the double slit encounters a polarizer in front of either one or both of the slits.Comment: 6 page