One trend in software development is rapid deployment of plug-ins and updated components. A challenge is proving correctness of quality attributes. An assurance case that is automated with an ontology can potentially detect inconsistencies across resource types. A second challenge is translation of end-to-end requirements into resource properties.
Coordination of automated recovery processes can be approached from different perspectives such as how well specific service requirements will be delivered during a failure. Another perspective is from the infrastructure that is available to perform recovery from a network failure.
To institutionalize advance material solution analysis processes such as condition-based maintenance plus, it is important to develop a transition plan. This plan describes how to get from a current to a future state.
One question is whether there are executable versions that implement the semantics of the IDEAS ontology that is the basis of the DoDAF Meta-Model. With representations such as the Unified Modeling Language, it may be not be easy to perform formal verification of a system model. It may be interesting to see what implementations of IDEAS become available in the next few months.
To validate provisioning information, the dependability assessment process builds a transformation from an XML data model to a logical model.
I have been researching a dependability assessment process that checks whether configuration settings in network devices are provisioned in a consistent manner.