By Topic

IEEE Transactions on Software Engineering

Issue 2 • Date Feb. 1986

Filter Results

Displaying Results 1 - 19 of 19
  • Guest editors' prologue special issue on software design methods

    Publication Year: 1986, Page(s):185 - 191
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1959 KB)

    We describe why these papers were chosen, and categorize them in terms of major contribution, underlying model of the software life-cycle, and applicability to various types of system. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Data structured programming: Program design without arrays and pointers

    Publication Year: 1986, Page(s):192 - 197
    Cited by:  Papers (17)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1387 KB)

    Structured programming introduced a new discipline for accessing the instructions of a program. In suitable programming languages, this discipline can be described in terms of program design without gotos. It can be shown, for example, that any functional result achievable in a programming language with gotos can be achieved in that same language without gotos if sequence, selection, and iteration... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The transformation schema: An extension of the data flow diagram to represent control and timing

    Publication Year: 1986, Page(s):198 - 210
    Cited by:  Papers (63)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2484 KB)

    The data flow diagram has been extensively used to model the data transformation aspects of proposed systems. However, previous definitions of the data flow diagram have not provided a comprehensive way to represent the interaction between the timing and control aspects of a system and its data transformation behavior. An extension of the data flow diagram called the transformation schema is descr... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Object-oriented development

    Publication Year: 1986, Page(s):211 - 221
    Cited by:  Papers (201)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2975 KB)

    Object-oriented development is a partial-lifecycle software development method in which the decomposition of a system is based upon the concept of an object. This method is fundamentally different from traditional functional approaches to design and serves to help manage the complexity of massive software-intensive systems. The author examines the process of object-oriented development as well as ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An overview of JSD

    Publication Year: 1986, Page(s):222 - 240
    Cited by:  Papers (32)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3626 KB)

    The Jackson System Development (JSD) method addresses most of the software lifecycle. JSD specifications consist mainly of a distributed network of processes that communicate by message-passing and read-only inspection of each other's data. A JSD specification is therefore directly executable, at least in principle. Specifications are developed middle-out from an initial set of `model' processes. ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Functional programming, formal specification, and rapid prototyping

    Publication Year: 1986, Page(s):241 - 250
    Cited by:  Papers (26)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2209 KB)

    Functional programming has enormous potential for reducing the high cost of software development. Because of the simple mathematical basis of functional programming, it is easier to design correct programs in a purely functional style than in a traditional imperative style. It is argued that functional programs combine the clarity required for the formal specification of software designs with the ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A rational design process: How and why to fake it

    Publication Year: 1986, Page(s):251 - 257
    Cited by:  Papers (97)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1705 KB)

    Many have sought a software design process that allows a program to be derived systematically from a precise statement of requirements. It is proposed that, although designing a real product in that way will not be successful, it is possible to produce documentation that makes it appear that the software was designed by such a process. The ideal process and the documentation that it requires are d... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A recommended practice for describing software designs: IEEE standards project 1016

    Publication Year: 1986, Page(s):258 - 263
    Cited by:  Papers (3)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1558 KB)

    The method outlined presumes that a design is completely described when the information needs of each design user are satisfied. The minimum set of design users and their specific information requirements are discussed. An information model is used to describe the needed design information through a set of 15 standard design entity attributes. To simplify the access and assimilation of design info... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An empirical study of software design practices

    Publication Year: 1986, Page(s):264 - 271
    Cited by:  Papers (15)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1692 KB)

    Results of an empirical study of software design practices in one specific environment are reported. The practices examined affect module size, module strength, data coupling, descendant span, unreferenced variables, and software reuse. Measures characteristic of these practices were extracted from 887 Fortran modules developed for five flight dynamics software projects monitored by the Software E... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A metaprogramming method and its economic justification

    Publication Year: 1986, Page(s):272 - 277
    Cited by:  Papers (9)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (1474 KB)

    Metaprogramming, defined as creating application programs by writing programs that produce programs, is presented as the basis of a method for reducing software costs and improving software quality. The method starts with a rapid prototyping phase in which selected representative parts of the application are prototyped; this is followed by a tooling up phase, during which the metaprogramming occur... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Constrained expressions: Adding analysis capabilities to design methods for concurrent software systems

    Publication Year: 1986, Page(s):278 - 292
    Cited by:  Papers (18)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3716 KB)

    An approach to the design of concurrent software systems based on the constrained expression formalism is described. This formalism provides a rigorous conceptual model for the semantics of concurrent computations, thereby supporting analysis of important system properties as part of the design process. This approach allows designers to use standard specification and design languages, rather than ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SARA (System ARchitects Apprentice): Modeling, analysis, and simulation support for design of concurrent systems

    Publication Year: 1986, Page(s):293 - 311
    Cited by:  Papers (25)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4260 KB)

    An environment to support designers in the modeling, analysis, and simulation of concurrent systems is described. It is shown how a fully nested structure model supports multilevel design and focuses attention on the interfaces between the modules which serve to encapsulate behavior. Using simple examples, it is shown how a formal graph model can be used to model behavior in three domains: control... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Salient features of an executable specification language and its environment

    Publication Year: 1986, Page(s):312 - 325
    Cited by:  Papers (28)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (3205 KB)

    The executable specification language PAISLey and its environment are presented as a case study in the design of computer languages. It is shown that PAISLey is unusual (and for some features unique) in having the following desirable features: (1) there is both synchronous and asynchronous parallelism free of mutual-exclusion problems, (2) all computations are encapsulated, (3) specifications in t... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Developing interactive information systems with the User Software Engineering methodology

    Publication Year: 1986, Page(s):326 - 345
    Cited by:  Papers (14)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (4236 KB)

    User software engineering (USE) is a methodology, supported by automated tools, for the systematic development of interactive information systems. The USE methodology gives particular attention to effective user involvement in the early stages of the software development process, concentrating on external design and the use of rapidly created and modified prototypes of the user interface. The USE ... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Process-translatable Petri nets for the rapid prototyping of process control systems

    Publication Year: 1986, Page(s):346 - 357
    Cited by:  Papers (66)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (2364 KB)

    A methodology for the rapid prototyping of process control systems which is based on an original extension to classical Petri nets is presented. The proposed nets, called PROT nets, provide a suitable framework to support the following activities: building an operational specification model; evaluation, simulation, and validation of the model; and automatic translation into program structures. PRO... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Real-time software life cycle with the model system

    Publication Year: 1986, Page(s):358 - 373
    Cited by:  Papers (1)
    Request permission for commercial reuse | Click to expandAbstract | PDF file iconPDF (886 KB)

    The use of an assertive specification language for real-time software development and maintenance is considered. The language is used for asserting the acts or relations inherent in the problem to be solved; this is in contrast to conventional programming languages, which are used to express the computer solution. Expressing a problem in Model consists of declaring array variables and defining the... View full abstract»

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

    Publication Year: 1986, Page(s): 374
    Request permission for commercial reuse | PDF file iconPDF (64 KB)
    Freely Available from IEEE
  • Ada™ applications and environments

    Publication Year: 1986, Page(s): 1
    Request permission for commercial reuse | PDF file iconPDF (355 KB)
    Freely Available from IEEE
  • Call for papers

    Publication Year: 1986, Page(s): 1
    Request permission for commercial reuse | PDF file iconPDF (193 KB)
    Freely Available from IEEE

Aims & Scope

The IEEE Transactions on Software Engineering is interested in well-defined theoretical results and empirical studies that have potential impact on the construction, analysis, or management of software. The scope of this Transactions ranges from the mechanisms through the development of principles to the application of those principles to specific environments. Specific topic areas include: a) development and maintenance methods and models, e.g., techniques and principles for the specification, design, and implementation of software systems, including notations and process models; b) assessment methods, e.g., software tests and validation, reliability models, test and diagnosis procedures, software redundancy and design for error control, and the measurements and evaluation of various aspects of the process and product; c) software project management, e.g., productivity factors, cost models, schedule and organizational issues, standards; d) tools and environments, e.g., specific tools, integrated tool environments including the associated architectures, databases, and parallel and distributed processing issues; e) system issues, e.g., hardware-software trade-off; and f) state-of-the-art surveys that provide a synthesis and comprehensive review of the historical development of one particular area of interest.

Full Aims & Scope

Meet Our Editors

Editor-in-Chief
Matthew B. Dwyer
Dept. Computer Science and Engineering
256 Avery Hall
University of Nebraska-Lincoln
Lincoln, NE 68588-0115 USA
tse-eic@computer.org