Open Access. Powered by Scholars. Published by Universities.®

Software Engineering Commons™

Open Access. Powered by Scholars. Published by Universities.®

Air Force Institute of Technology

Discipline
Keyword
Publication Year
Publication
Publication Type

Articles 121 - 124 of 124

Full-Text Articles in Software Engineering

Mapping An Object-Oriented Requirements Analysis To A Design Architecture That Supports Design And Component Reuse, Kelly L. Spicer Dec 1990

Mapping An Object-Oriented Requirements Analysis To A Design Architecture That Supports Design And Component Reuse, Kelly L. Spicer

Theses and Dissertations

Design reuse has more potential for increasing the productivity of software development and maintenance than do traditional approaches to software reuse that emphasize reuse of smaller components. Current software development methods do not promote design reuse. The literature contains limited documented research on the subject, but enough that some design reuse principles can be gleaned. Among these principles are that reusable designs should be applicable within some domain of application, have a consistent structure, provide a method for instantiating the design, avoid object nesting, and promote reuse of smaller components as well. A design mapping method from an object-oriented requirements …


The Development Of A Graphical Notation For The Formal Specification Of Software, Gene A. Place Dec 1990

The Development Of A Graphical Notation For The Formal Specification Of Software, Gene A. Place

Theses and Dissertations

The program tranformations lifecycle model, proposed by Balzer in 1984, may hold the key to dramatic leap in software engineer productivity necessitated by the tremendous growth in the world's demand for software. This leap in productivity is made possible by the program transformation lifecycle's reliance on formal specifications rather than programs as the primary vehicle for the creation and maintenance of software systems. Because formal specifications are concerned only with system behaviors and not implementation details, formal specifications tend to present critical system characteristics much more concisely than programs. The major disadvantage of using formal specifications in a software development …


An Abstract Data Model For The Idef0 Graphical Analysis Language, Gerald R. Morris, Thomas C. Hartrum, Mark A. Roth Jan 1990

An Abstract Data Model For The Idef0 Graphical Analysis Language, Gerald R. Morris, Thomas C. Hartrum, Mark A. Roth

AFIT Documents

IDEF0 is the United States Air Force's ICAM (Integrated Computer Aided Manufacturing) Definition Method Zero graphical analysis language, a subset of Ross' Structured Analysis (SA) language. The language is also an excellent methodology for performing a requirements-phase analysis for any software development project. We present an abstract data model for IDEF0 using entity-relationship diagrams. This model helps to mitigate some of the ambiguities inherent in IDEF0. The model is divided into two parts representing the analysis data (the essential data model) and the graphical data (the drawing data model). This dual modeling approach allows for the …


Software Simulation Of The D17b Computer, Bruce Chatterton Mar 1972

Software Simulation Of The D17b Computer, Bruce Chatterton

Theses and Dissertations

A software program has been written which simulates the functions of the Minuteman D17B computer at the register transfer level. The simulation program is written in the FORTRAN Extended language to be used on the Intercom System (teletype) of a CDC 6600 computer system. The simulation program consists of a main program and eight subroutines. A programming language for the D17B simulation was formed which contains numbers and load codes, switches, and miscellaneous commands. Example programs run on the simulated computer have been included to show the types of output available.