By Topic

Software Engineering Journal

Issue 6 • Date Nov. 1992

Filter Results

Displaying Results 1 - 6 of 6
  • Viewpoints for requirements definition

    Publication Year: 1992, Page(s):375 - 387
    Cited by:  Papers (22)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1053 KB)

    This paper is a survey of the current viewpoint-oriented requirements approaches and a description of an alternative object-oriented viewpoint-based approach. The paper sets out a case for a multiple viewpoint-oriented approach in requirements definition and, using a simple case study, examines the viewpoint approach adopted by three requirements methodologies. The paper concludes by proposing an ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • To prototype or not to prototype? That is the question

    Publication Year: 1992, Page(s):388 - 392
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (454 KB)

    The paper describes an experiment carried out at the Cranfield Institute of Technology to compare the prototyping approach with that of the structured approach for KBS development. The components and constraints imposed on the exercise are presented to provide the background of the experiment. The project's stages of development are described, and the conclusions drawn from the experiment are pres... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • High-level language extensions for user-interface programming

    Publication Year: 1992, Page(s):409 - 424
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1260 KB)

    Many user-interface toolkits, screen management facilities and user-interface management systems (UIMS) have been developed for creating user interfaces. These systems, however, normally require the user to learn a new programming language or set of techniques. Extending conventional programming languages has the advantage that the same language can be used for describing both the application and ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Transformations using a meta-system approach to software development

    Publication Year: 1992, Page(s):425 - 437
    Cited by:  Papers (3)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1094 KB)

    A transformational approach based on a specification environment definition facility is proposed. The authors illustrate this approach through the development of a set of transformation rules expressed in a transformational language. The rules demonstrate how a formal description of a data-flow diagram in a structure analysis environment can be automatically converted, with possible design interve... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An environment for initial software engineering teaching

    Publication Year: 1992, Page(s):438 - 444
    Cited by:  Papers (3)
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (584 KB)

    The teaching of software engineering skills is traditionally seen as an activity which follows the acquisition of the ability to 'program'. It is proposed that initial software engineering skills can be taught in conjunction with the development of programming skills, by providing a problem-oriented curriculum based on the use of notations to describe 'things'. This approach is enhanced if a high ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Towards a formal specification of revisable CORE: allowing for change

    Publication Year: 1992, Page(s):393 - 408
    IEEE is not the copyright holder of this material | Click to expandAbstract | PDF file iconPDF (1136 KB)

    Many requirements analysis tools, techniques and methods exist to help in the development of consistent, complete and valid requirements specifications. However, few, if any, of these methods recognise and take sufficient notice of the iterative nature of eliciting and specifying requirements. The author proposes the development of revisable methods, which reflect the significance of change in evo... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.