By Topic

Software Engineering, IEEE Transactions on

Issue 3 • Date March 1994

Filter Results

Displaying Results 1 - 5 of 5
  • Comments on "Language design for program manipulation"

    Publication Year: 1994 , Page(s): 218 - 219
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (259 KB)  

    The paper by E.A.T. Merks et al. (see ibid., vol. 18, p. 19-32, 1992) "Language design for program manipulation" identifies design principles for a procedural or object-oriented language whose programs will be easier to manipulate. However, it neglects to relate these design principles to existing, broader, design principles, and in some instances omits good examples of languages meeting their cri... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Automating output size and reuse metrics in a repository-based computer-aided software engineering (CASE) environment

    Publication Year: 1994 , Page(s): 169 - 187
    Cited by:  Papers (10)  |  Patents (5)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (1640 KB)  

    Measurement of software development productivity is needed in order to control software costs, but it is discouragingly labor-intensive and expensive. Computer-aided software engineering (CASE) technologies-especially repository-based, integrated CASE-have the potential to support the automation of this measurement. We discuss the conceptual basis for the development of automated analyzers for fun... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Specifying transaction-based information systems with regular expressions

    Publication Year: 1994 , Page(s): 207 - 217
    Cited by:  Patents (8)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (952 KB)  

    The work is about the formal specification of transaction-based, interactive information systems. A transaction is a task that the user can execute independently, and the system can be defined as a partially ordered set of transactions. The general framework is the transformational paradigm, based on the classical Waterfall development model (W.W. Royce, 1970). The stages are systems analysis, sof... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software measurement: a necessary scientific basis

    Publication Year: 1994 , Page(s): 199 - 206
    Cited by:  Papers (72)  |  Patents (2)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (864 KB)  

    Software measurement, like measurement in any other discipline, must adhere to the science of measurement if it is to gain widespread acceptance and validity. The observation of some very simple, but fundamental, principles of measurement can have an extremely beneficial effect on the subject. Measurement theory is used to highlight both weaknesses and strengths of software metrics work, including... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Designing an agent synthesis system for cross-RPC communication

    Publication Year: 1994 , Page(s): 188 - 198
    Cited by:  Papers (6)  |  Patents (5)
    Save to Project icon | Request Permissions | Click to expandAbstract | PDF file iconPDF (1052 KB)  

    Remote procedure call (RPC) is the most popular paradigm used today to build distributed systems and applications. As a consequence, the term “RPC” has grown to include a range of vastly different protocols above the transport layer. A resulting problem is that programs often use different RPC protocols, cannot be interconnected directly, and building a solution for each case in a larg... View full abstract»

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

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
tseeicdwyer@computer.org