By Topic

Software Engineering Journal

Issue 1 • Date Jan 1991

Filter Results

Displaying Results 1 - 3 of 3
  • Software technology transfer

    Page(s): 17 - 23
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (592 KB)  

    The paper puts forward a possible generic model for the process of technology transfer. It describes in a generalised style how the process takes place in typical industrial circumstances, ranging from initial awareness to in-use support. One might image that the example under study is the adoption of a new software engineering method and associated toolset in a company, in a business which makes substantial use of computers embedded in its products. This model relates primarily to the transfer of discrete software process technology, i.e. a new method or toolset. The model is based on experience, gained over the last 15 years View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Analogy as a paradigm for specification reuse

    Page(s): 3 - 15
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (852 KB)  

    Specification reuse by analogy is proposed as an alternative paradigm to support requirements analysis. The paradigm is founded on a descriptive model of analogy in software engineering problems, which suggests critical determinants of software engineering analogies. This model is discussed in terms of two non-simple software engineering analogies, which also suggest the potential of specification reuse by analogy. The requirements of a CASE tool to support reuse of specifications are proposed View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • MOON-modular object-oriented notation

    Page(s): 25 - 33
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (536 KB)  

    Moon is a notation for designing complete systems, addressing the description of subsystems to be executed by both computer and non-computer processors. The design method is object-oriented in approach, based primarily on the Mascot 3 notation and also on the JSP notation. Systems and subsystems are defined as collections of data repositories, related activities and subsystems. It should therefore also be considered as a modular notation. Moon abstracts a system to a hierarchy of networks of activities and data repositories, using an extension of the Mascot 3 notation. A further development of the system uses a more data-oriented approach, describing actions and data items separately using an extension of the JSP notation. The extensions to the two notations ensure that consistency between network and program abstractions can be enforced View full abstract»

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