Prototyping a real-time embedded system in Smalltalk

Authors:
B. M. Barry
Affiliations:
Defence Research Establishment Ottawa, Department of National Defence, Ottawa, Canada
Venue:
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Year:
1989

Citing 7
Cited 5

Actors: a model of concurrent computation in distributed systems

Actors: a model of concurrent computation in distributed systems
Object-oriented development

IEEE Transactions on Software Engineering
No Silver Bullet Essence and Accidents of Software Engineering

Computer
Using prototypical objects to implement shared behavior in object-oriented systems

OOPLSA '86 Conference proceedings on Object-oriented programming systems, languages and applications
Using objects to design and build radar ESM systems

OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
Orwell—a configuration management system for team programming

OOPSLA '88 Conference proceedings on Object-oriented programming systems, languages and applications
Software Engineering Economics

Software Engineering Economics

Actra—an industrial strength concurrent object-oriented programming system

OOPSLA/ECOOP '90 Proceedings of the workshop on Object-based concurrent programming
Highly efficient and encapsulated re-use of synchronization code in concurrent object-oriented languages

OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
DIR/SEE: a Smalltalk environment for developing Ada applications and maintaining legacies

SETA2 Proceedings of the second international symposium on Environments and tools for Ada
Programming languages and systems for prototyping concurrent applications

ACM Computing Surveys (CSUR)
New Complexities in the Embedded World - The OTI Approach

ECOOP '97 Proceedings of the Workshops on Object-Oriented Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper presents a case study of AMEP, a prototype ESM signal processor which has been implemented in Smalltalk using an actor-based design methodology, Arguments for choosing an OOPS for implementing such applications are reviewed. AMEP is a large system which includes both hard real-time and knowledge-based subsystems. Extensive software metrics are presented for each subsystem and used to compare the characteristics of code designed for different purposes. For example, analysis of this data suggests that knowledge-based applications may be more difficult to port to an object-based language such as Ada than hard real-time systems. Team programming, productivity, documentation standards and other software engineering issues are also addressed.