28,461 research outputs found

    A survey of software development practices in the New Zealand software industry

    Get PDF
    We report on the software development techniques used in the New Zealand software industry, paying particular attention to requirements gathering. We surveyed a selection of software companies with a general questionnaire and then conducted in-depth interviews with four companies. Our results show a wide variety in the kinds of companies undertaking software development, employing a wide range of software development techniques. Although our data are not sufficiently detailed to draw statistically significant conclusions, it appears that larger software development groups typically have more well-defined software development processes, spend proportionally more time on requirements gathering, and follow more rigorous testing regimes

    Tools reference manual for a Requirements Specification Language (RSL), version 2.0

    Get PDF
    This report describes a general-purpose Requirements Specification Language, RSL. The purpose of RSL is to specify precisely the external structure of a mechanized system and to define requirements that the system must meet. A system can be comprised of a mixture of hardware, software, and human processing elements. RSL is a hybrid of features found in several popular requirements specification languages, such as SADT (Structured Analysis and Design Technique), PSL (Problem Statement Language), and RMF (Requirements Modeling Framework). While languages such as these have useful features for structuring a specification, they generally lack formality. To overcome the deficiencies of informal requirements languages, RSL has constructs for formal mathematical specification. These constructs are similar to those found in formal specification languages such as EHDM (Enhanced Hierarchical Development Methodology), Larch, and OBJ3

    Design as conversation with digital materials

    Get PDF
    This paper explores Donald Schön's concept of design as a conversation with materials, in the context of designing digital systems. It proposes material utterance as a central event in designing. A material utterance is a situated communication act that depends on the particularities of speaker, audience, material and genre. The paper argues that, if digital designing differs from other forms of designing, then accounts for such differences must be sought by understanding the material properties of digital systems and the genres of practice that surround their use. Perspectives from human-computer interaction (HCI) and the psychology of programming are used to examine how such an understanding might be constructed.</p

    Comparative analysis of copyright assignment and licence formalities for Open Source Contributor Agreements

    Get PDF
    This article discusses formal requirements in open source software contributor copyright assignment and licensing agreements. Contributor agreements are contracts by which software developers transfer or license their work on behalf of an open source project. This is done for convenience and enforcement purposes, and usually takes the form of a formal contract. This work conducts a comparative analysis of how several jurisdicitons regard those agreements. We specifically look at the formal requirements across those countries to ascertain whether formalities are constitutive or probative. We then look at the consequences of the lack of formalities for the validity of those contributor agreements

    Using ontologies to support and critique decisions

    No full text
    Supporting decision making in the working environment has long being pursued by practitioners across a variety of fields, ranging from sociology and operational research to cognitive and computer scientists. A number of computer-supported systems and various technologies have been used over the years, but as we move into more global and flexible organisational structures, new technologies and challenges arise. In this paper, I argue for an ontology-based solution and present some of the early prototypes we have been developing, assess their impact on the decision making process and elaborate on the costs involved
    corecore