This instructional guide provides learners with an example operational context for use in the spe... more This instructional guide provides learners with an example operational context for use in the specification, design, testing and analysis of a Tactical Disc Clearance System (TDCS), a fictitious system concept to address the problem of identifying and clearing hazardous objects from a designated area. A notional customer has provided expectations for the TDCS in the form of a Design Reference Mission (DRM). A DRM establishes an operational context, descriptions of the environment and situations in which solution concepts are expected to operate, an operational narrative of expected behavior including a sequence of operational activities and interactions between systems in an environment, and sample measures for establishing goals for mission success. This instructional DRM also provides an example of how to separate short and long term goals for prototype and production ready systems, respectively. This DRM is intended to serve as an underpinning for lessons in decision making using...
During the last half of this century, the Department of Defense (DoD) has made an enormous invest... more During the last half of this century, the Department of Defense (DoD) has made an enormous investment in computer-based systems. To control the cost, timeliness and quality of automated defense systems, DoD established a framework of military standards and specifications. A recent policy change (Perry, 1994) removed the requirement for DoD program managers to adhere to this framework; nonetheless, the necessity remains for applying effective contractual software development standards. This paper describes the purpose and intent of the current military standard (DOD-STD-2167A) dealing with software development, and presents a model of the contractual process required to implement the standard. It also outlines the process which has been used to update and issue software standards. It concludes that the proper application of any DoD software development standard will continue to be a difficult task which depends primarily on the capability of government program managers and which must accommodate the range of capabilities of individual software development contractors.
An effective systems engineering process will provide the framework to enable the complex technic... more An effective systems engineering process will provide the framework to enable the complex technical endeavor of railgun system design and development to transition from a set of research projects to a viable acquisition program. The detailed formulation and application of the railgun systems engineering process will be defined by government acquisition agents and the selected private sector contractors in accordance with United States (US) Department of Defense policy and regulation and in keeping with best systems engineering practices. Three factors that are critical to the success of the US Navy’s Railgun Program include integrated product teams, risk management, and early systems engineering planning and commitment.
During the last half of this century, the Department of Defense (DoD) has made an enormous invest... more During the last half of this century, the Department of Defense (DoD) has made an enormous investment in computer-based systems. To control the cost, timeliness and quality of automated defense systems, DoD established a framework of military standards and specifications. A recent policy change (Perry, 1994) removed the requirement for DoD program managers to adhere to this framework; nonetheless, the necessity remains for applying effective contractual software development standards. This paper describes the purpose and intent of the current military standard (DOD-STD-2167A) dealing with software development, and presents a model of the contractual process required to implement the standard. It also outlines the process which has been used to update and issue software standards. It concludes that the proper application of any DoD software development standard will continue to be a difficult task which depends primarily on the capability of government program managers and which must accommodate the range of capabilities of individual software development contractors.
A software safety analysis approach for distributed systems, based on a technique called componen... more A software safety analysis approach for distributed systems, based on a technique called component-message fault analysis, is presented. This technique checks the safety-critical logic, using the safety specification for different categories of component fault events, to uncover ambiguous safety requirements or design deficiencies. To demonstrate the power of this technique, a dual-purpose missile system is introduced and analyzed with regard
2008 IEEE International Conference on System of Systems Engineering, 2008
The next generation of military capabilities will hinge on systems of systems. Such systems can i... more The next generation of military capabilities will hinge on systems of systems. Such systems can introduce emergent hazards that must be adequately dealt with before the system of systems can be employed. Traditional hazard analysis techniques do not address the complexity and size of systems of systems. In this paper we describe a technique for conducting interface hazard analysis for systems of systems. The technique is compatible with current system safety processes.
This instructional guide provides learners with an example operational context for use in the spe... more This instructional guide provides learners with an example operational context for use in the specification, design, testing and analysis of a Tactical Disc Clearance System (TDCS), a fictitious system concept to address the problem of identifying and clearing hazardous objects from a designated area. A notional customer has provided expectations for the TDCS in the form of a Design Reference Mission (DRM). A DRM establishes an operational context, descriptions of the environment and situations in which solution concepts are expected to operate, an operational narrative of expected behavior including a sequence of operational activities and interactions between systems in an environment, and sample measures for establishing goals for mission success. This instructional DRM also provides an example of how to separate short and long term goals for prototype and production ready systems, respectively. This DRM is intended to serve as an underpinning for lessons in decision making using...
During the last half of this century, the Department of Defense (DoD) has made an enormous invest... more During the last half of this century, the Department of Defense (DoD) has made an enormous investment in computer-based systems. To control the cost, timeliness and quality of automated defense systems, DoD established a framework of military standards and specifications. A recent policy change (Perry, 1994) removed the requirement for DoD program managers to adhere to this framework; nonetheless, the necessity remains for applying effective contractual software development standards. This paper describes the purpose and intent of the current military standard (DOD-STD-2167A) dealing with software development, and presents a model of the contractual process required to implement the standard. It also outlines the process which has been used to update and issue software standards. It concludes that the proper application of any DoD software development standard will continue to be a difficult task which depends primarily on the capability of government program managers and which must accommodate the range of capabilities of individual software development contractors.
An effective systems engineering process will provide the framework to enable the complex technic... more An effective systems engineering process will provide the framework to enable the complex technical endeavor of railgun system design and development to transition from a set of research projects to a viable acquisition program. The detailed formulation and application of the railgun systems engineering process will be defined by government acquisition agents and the selected private sector contractors in accordance with United States (US) Department of Defense policy and regulation and in keeping with best systems engineering practices. Three factors that are critical to the success of the US Navy’s Railgun Program include integrated product teams, risk management, and early systems engineering planning and commitment.
During the last half of this century, the Department of Defense (DoD) has made an enormous invest... more During the last half of this century, the Department of Defense (DoD) has made an enormous investment in computer-based systems. To control the cost, timeliness and quality of automated defense systems, DoD established a framework of military standards and specifications. A recent policy change (Perry, 1994) removed the requirement for DoD program managers to adhere to this framework; nonetheless, the necessity remains for applying effective contractual software development standards. This paper describes the purpose and intent of the current military standard (DOD-STD-2167A) dealing with software development, and presents a model of the contractual process required to implement the standard. It also outlines the process which has been used to update and issue software standards. It concludes that the proper application of any DoD software development standard will continue to be a difficult task which depends primarily on the capability of government program managers and which must accommodate the range of capabilities of individual software development contractors.
A software safety analysis approach for distributed systems, based on a technique called componen... more A software safety analysis approach for distributed systems, based on a technique called component-message fault analysis, is presented. This technique checks the safety-critical logic, using the safety specification for different categories of component fault events, to uncover ambiguous safety requirements or design deficiencies. To demonstrate the power of this technique, a dual-purpose missile system is introduced and analyzed with regard
2008 IEEE International Conference on System of Systems Engineering, 2008
The next generation of military capabilities will hinge on systems of systems. Such systems can i... more The next generation of military capabilities will hinge on systems of systems. Such systems can introduce emergent hazards that must be adequately dealt with before the system of systems can be employed. Traditional hazard analysis techniques do not address the complexity and size of systems of systems. In this paper we describe a technique for conducting interface hazard analysis for systems of systems. The technique is compatible with current system safety processes.
Uploads
Papers by Paul Shebalin