Skip to main content

Currently Skimming:

4 Basic Research for Air Force Software
Pages 52-59

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 52...
... 4 Basic Research for Air Force Software Network-enabled systems are by definition dependent on complex software because of the great number of possible states of the networks. Building such software is very challenging.
From page 53...
... In many cases, it is more dominant than many of the more narrowly focused issues that receive more attention, such as language, tools, hardware instruction set, architecture, etc. Simply stated, the concept of precedented systems means that the learning curve applies to software development, as it does in all other areas of human endeavor.
From page 54...
... Coevolution of Air Force Evolvability throughout Co-evolutionofAFconcept of Softwareperformance Software behavior Evolvabilitythroughout concepts of operation operationsandsystem envelopes envelopes the life cycle the life cycle and system architecture architecture FIGURE 4-1 Logical flow of software development in support of Air Force operations. That report went on to note that engineering and management techniques have been developed to address the predictability of software and its behaviors, but only in domains that are fairly well understood and where the team developing and acquiring the software-intensive system has worked together on a similar system.
From page 55...
... This model for requirements definition has the additional benefits of building stronger communication between researchers and the user communities and of providing infrastructure to better support team-based problem solving involving humans and automated decision aids, which is particularly valuable for next-generation enterprise systems. Current research in executable architectures and in engineering tools for the design and analysis of functional and nonfunctional attributes provides a basis for enabling this coevolution.
From page 56...
... These analysis methods typically work on static representations. A new approach in the software engineering community, the Model Driven Architecture (MDA)
From page 57...
... To this end, the committee recommends that AFOSR support a new line of research, extending DARPA-funded, model-based software research to explore the concept of a software behavior envelope. Dynamic analysis of nonfunctional attributes based on embedded models could be viewed as the behavior envelope of a network-enabled system.
From page 58...
... Thus, important research areas include methods to infer the architecture of legacy software systems, to identify software components within that architecture, to parallelize legacy system software and applications, and to migrate that architecture and components to new and improved architectures, possibly within a new computing environment. The products of the research outlined in the previous section, for predicting software performance envelopes, could also be applied during such a migration to end users to tailor the software in a new operational environment.
From page 59...
... · Research in security in support of the goal of measurable, avail able, secure, trustworthy, and sustainable network-enabled sys tems. · To attain assured reliability with hard time-deadlines, methods for modeling and analyzing integrated reliability, availability, and schedulability of components and systems in realistic conditions derived from user-specified scenarios.


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.