What This Document Is
This document is a presentation outlining the architectural approach for the ICO Payload Control System (PCS). It details the rationale and methodology behind building this system using object-oriented principles. Created for a Ground Stations Architecture Workshop at Hughes in 1988, it provides a snapshot of the software development strategy for a complex global mobile telephony system. The presentation focuses on the design choices made during the initial phases of development, including tool selection and analysis techniques.
Why This Document Matters
This resource is valuable for students and professionals involved in software engineering, particularly those interested in the historical application of object-oriented design in large-scale systems. Individuals studying telecommunications systems, ground station architecture, or software development methodologies will find the context and reasoning presented here insightful. It’s especially relevant for those researching early implementations of object-oriented programming in a commercial setting and the challenges of integrating custom software with Commercial Off-The-Shelf (COTS) components. Understanding the design decisions made in this project can offer valuable lessons for modern software projects.
Common Limitations or Challenges
This document presents a high-level overview of the design process. It does *not* provide detailed code examples, specific implementation details, or a complete system specification. It focuses on the ‘why’ behind the design choices, rather than the ‘how’. Users should be aware that the technologies and tools discussed are from the late 1980s and may have been superseded by more modern alternatives. It also doesn’t cover the operational aspects of the ICO system beyond the payload control function.
What This Document Provides
* An overview of the ICO system and its Payload Control System.
* The justification for adopting an object-oriented architecture.
* Discussion of the analysis methodology employed (Integrated Systems Design Methodology).
* Criteria used for selecting a Computer-Aided Software Engineering (CASE) tool.
* A glossary of key acronyms related to the project and its technologies.
* Insights into the considerations for balancing custom software development with COTS components.
