Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library

Javascript is currently disabled for your browser. For an optimal search experience, please enable javascript.

Advanced Search

Basic Search

Content Type

Topics

Publication Date

Technical Report

The Software Technical Review Process

  • July 1988
  • By Mario R. Barbacci
  • This 1988 report describes MasterTask, a program that can emulate any task in an application by interpreting the timing expression describing the behavior of the task, performing the input and output port operations in the proper sequence and at the prope
  • Publisher: Software Engineering Institute
    CMU/SEI Report Number: CMU/SEI-88-TR-020
  • Abstract

    Durra is a language designed to support the construction of distributed applications using concurrent, coarse-grain tasks running on networks of heterogeneous processors. An application written in Durra describes the tasks to be instantiated and executed as concurrent processes, the types of data to be exchanged by the processes, and the intermediate queues required to store the data as they move from producer to consumer processes.

    The tasks and types available to an application developer are described by a collection of Durra task descriptions and type declarations stored in a library. One of the components of a task description is a specification of the external timing behavior of the task. It describes the sequence of input and output port operations and the amount of processing time spent between port operations.

    This report describes MasterTask, a program that can emulate any task in an application by interpreting the timing expression describing the behavior of the task, performing the input and output port operations in the proper sequence and at the proper time.

    MasterTask is useful to both application developers and task developers. Application developers can build early prototypes of an application by using MasterTask as a substitute for task implementations that have yet to be written. Task developers can experiment with and evaluate proposed changes in task behavior or performance by rewriting and reinterpreting the corresponding timing expression. 

  • Download

Cite This Report

SEI

Barbacci, Mario. The Software Technical Review Process. CMU/SEI-88-TR-020. Software Engineering Institute, Carnegie Mellon University. 1988. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=60789

IEEE

Barbacci. Mario, "The Software Technical Review Process," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Report CMU/SEI-88-TR-020, 1988. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=60789

APA

Barbacci, Mario. (1988). The Software Technical Review Process (CMU/SEI-88-TR-020). Retrieved August 21, 2017, from the Software Engineering Institute, Carnegie Mellon University website: http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=60789

CHI

Mario Barbacci. The Software Technical Review Process (CMU/SEI-88-TR-020). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1988. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=60789

MLA

Barbacci, Mario. 1988. The Software Technical Review Process (Technical Report CMU/SEI-88-TR-020). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=60789

BibTex

@techreport{BarbacciTheSoftware1988,
title={The Software Technical Review Process},
author={Mario Barbacci},
year={1988},
number={CMU/SEI-88-TR-020},
institution={Software Engineering Institute, Carnegie Mellon University},
address={Pittsburgh, PA},
url={http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=60789} }