HAL/SM system software requirements specification

For abstract, see N76-14843

NSSC-2 operating system design requirements specification

The design requirements and implementation standards for an NSSC-2 operating system are defined. An operating system diagram is presented along with system concepts and terminology

Project report : Requirements specification

The SAMRISK project “Sharing incident and threat information for common situational understanding“ (INSITU) commenced in May 2019. The INSITU project develops solutions for establishing a common situational understanding in complex operations requiring collaboration between several agencies. This involves systematic analysis of existing information sources and defining the information elements that are critical to share in different phases of a crisis situation. In addition, the project will develop procedures and related tool support for efficient collection and integration of information. As part of this work, the project contributes to harmonisation of terminology across agencies to secure effective communication. A map-based interface for display of information from different digital map resources will be developed, as a basis for a common operational picture (COP). This solution will also support evaluation and learning from incidents and emergency exercises. Based on a review of related research, the report briefly summarises the state of the art for the areas focused in the project. Through interviews and discussions with emergency stakeholders, field observation during an exercise, and field visits at operations centres, current practice for information sharing and establishing a COP is analysed. Based on the expressed needs from the emergency stakeholders and our analysis of current practice, the report specifies a set of requirements for information sharing, harmonisation of terminology, use of common map resources, and technology support for evaluation and learning from incidents.publishedVersio

Completeness, robustness, and safety in real-time software requirements specification

This paper presents an approach to providing a rigorous basis for ascertaining whether or not a given set of software requirements is internally complete, i.e., closed with respect to questions and inferences that can be made on the basis of information included in the specification. Emphasis is placed on aspects of software requirements specifications that previously have not been adequately handled, including timing abstractions, safety, and robustness

An analysis of the requirements traceability problem

In this paper1, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability, to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature. We report how the majority of the problems attributed to poor requirements traceability are due to inadequate pre-RS traceability and show the fundamental need for improvements here. In the remainder of the paper, we present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which advances have been (or can be) made, and make recommendations for research