Real time systems/software methodologies for large aerospace systems

@article{Patel1991RealTS,
  title={Real time systems/software methodologies for large aerospace systems},
  author={Bhadresh K. Patel and V. P. Litchfield and D. Tamanaha and Annette Davis},
  journal={1991 IEEE Aerospace Applications Conference Digest},
  year={1991},
  pages={2/1-2/9}
}
An overview of three proven and two emerging real-time methodologies currently available commercially is presented. The methods are described and compared based on criteria relevant to large aerospace projects. These methods are then compared against a typical US DoD system engineering lifecycle to show where individual projects have to enhance these methods with inhouse concepts to be practical. The study was undertaken by Hughes at Fullerton to determine a standardized way of training its… 
2 Citations

REFINEMENT OF THE REQUIREMENTS DEFINITION (RD) CONCEPT IN SYSTEM DEVELOPMENT: DEVELOPMENT OF THE RD AREAS

To alleviate problems in performing the definition of requirements, it is necessary to review and understand the practice of requirements definition (RD). Refinement of RD is necessary in order to

References

SHOWING 1-7 OF 7 REFERENCES

Strategies for Real-Time System Specification

The Hatley-Pirbhai techniques, now widely used in major avionics and electronics companies worldwide, are automated by most major CASE tools, including TurboCASE/Sys by StructSoft, Inc.

Comparative Evaluations of Four Specification Methods for Real-Time Systems

An objective evaluation of four methods, identified as ESML, Harel, Hatley-Pirbhai, and Ward-Mellor, from identification through detailed assessment, and the resulting recommendations and conclusions focus on method selection criteria, and on the large-grained impact of using these methods on a given project.

Embedded behavior pattern languages: a contribution to a taxonomy of case languages

  • P. Ward
  • Computer Science
    [1988] Proceedings of the Twenty-First Annual Hawaii International Conference on System Sciences. Volume II: Software track
  • 1988

The transformation schema: An extension of the data flow diagram to represent control and timing

  • P. Ward
  • Computer Science
    IEEE Transactions on Software Engineering
  • 1986
An extension of the data flow diagram called the transformation schema is described, which provides a notation and formation rules for building a comprehensive system model, and a set of execution rules to allow prediction of the behavior over time of a system modeled in this way.

How to integrate object orientation with structured analysis and design

  • P. Ward
  • Computer Science
    IEEE Software
  • 1989
The author argues that while object-oriented languages are popular, many developers mistakenly believe that to use them means they must stop using structured analysis and design. He shows that there

Real time