This flexibility is a key aspect needed to address the maturation of operational concepts, to permit ground and crew operators to gain trust in the system and mitigate unpredictability in human spaceflight. A data- driven flight software architecture will provide an evolvable automation capability to sequence through Guidance, Navigation & Control (GN&C) flight software modes and configurations while maintaining the required flexibility and human control over the automation. In particular, the vehicle flight software has requirements to accommodate increasingly automated missions throughout all phases of flight. The Orion Crew Exploration Vehicle (CET) is being designed to include significantly more automation capability than either the Space Shuttle or the International Space Station (ISS). The Orion GN and C Data- Driven Flight Software Architecture for Automated Sequencing and Fault Recovery This paper provides an overview of the GTE team's DSSA approach and then presents our work on automated support for message processing. Our initial work in this area has concentrated in the message handling subdomain we have defined and prototyped an approach that can automate one of the most software-intensive parts of C2 systems development. A major focus of GTE's approach is the automated generation of application components in particular subdomains. Such a capability will significantly reduce the cost of C2 applications development and will lead to improved system quality and reliability through the use of proven architectures and components. The objective of this program is to develop and demonstrate an architecture-driven, component-based capability for the automated generation of command and control (C2) applications. GTE is the Command and Control contractor for the Domain Specific Software Architectures program. Today's software architects, however,…ĭomain specific software architectures: Command and controlīraun, Christine Hatch, William Ruegsegger, Theodore Balzer, Bob Feather, Martin Goldman, Neil Wile, Dave Whatever the causes, architecture evolution is commonplace in real-world software projects. Such changes may be prompted by new feature requests, new quality attribute requirements, changing technology, or other reasons. Many software systems eventually undergo changes to their basic architectural structure. ERIC Educational Resources Information Center
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |