Functional Architecting Techniques - Applications to Space Operations Design
Notice bibliographique
Résumé
Historically, space systems have been developed using a physical architecture as the primary basis for design; structured functional architectures were the purview of network and software systems designers. Space operations design has thus frequently followed a hardware operations-centric thread. After Mobile Satellite Ventures (MSV) selected Boeing Space and Intelligence Systems to build and operate a Space Based Network (SBN) for their next generation Mobile Satellite System, Boeing determined that functional architecting techniques could bring added benefits to the system and operations development program. Boeing’s MSV SBN is a large scale space system that when deployed will provide ubiquitous 4G mobile coverage to the entire North American continent and beyond. The SBN features two large Boeing 702 GeoMobile satellites as well as 4 ground based beamforming-equipped dual gateway stations located across the US and Canada. This system and operations design effort and the relatively short time frame allowed by the customer’s business plan has called for rapid implementation of the functional architecture development process. Functional decomposition was performed on the MSV system, allowing development of a functional architecture for a system that had no previous architectural precedence. Additionally, the MSV program elected to use both the IDEF0 modeling method and the integration of DOORS® (for requirements management) with SLATE FI (functional architecture definition) for formalization of the functional architecture. This enabled the ability to import system requirements into SLATE FI to achieve an integrated architecture. This integration allowed the functional architecting process to rapidly support both the system and systems operations design processes, adding to the robustness and quality of derived program requirements and operational concepts. Derived from explicit operational scenarios, systems operations functions were explicitly defined and linked to the system architecture, with clear mapping to system functions and requirements, as well as allocated to hardware and software elements. Operational products for the Space Based Network, such as procedures, tools and training, could thus be built up around the operations aspects of the functional architecture in a straightforward manner. Boeing’s MSV program has been a pathfinder for the application of functional architecting to space systems and operations design. The functional architecture developed for the MSV program has provided many benefits to the overall system engineering process. Boeing has also integrated the customer’s outer shell network architecture and CONOPS into the SBN architecture and operations model which has significantly reduced program risk. While the MSV SBN is a space-based communications system, the operations architecting techniques demonstrated are fully applicable to other space applications; these methods can benefit future system developments in both the commercial and civil space operations arenas.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,006 | 0,008 |
| Méta-épidémiologie (sens strict) | 0,002 | 0,001 |
| Méta-épidémiologie (sens large) | 0,001 | 0,002 |
| Bibliométrie | 0,003 | 0,003 |
| Études des sciences et des technologies | 0,001 | 0,003 |
| Communication savante | 0,003 | 0,003 |
| Science ouverte | 0,002 | 0,002 |
| Intégrité de la recherche | 0,002 | 0,003 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,010 | 0,003 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».