Software Requirements Engineering Methodology

SREM is an acronym for software requirements engineering methodology and is also a shorthand name for the technology for specifying and designing systems resulting from a series of research efforts that started with SREM. The SREM approach is characterized by the following features: The use of an executable graphic notation to describe system and software behavior (e.g., RNETs and FNETs). The use of a user-extensible element-relation-attribute (ERA) language to describe the various system requirements and design characteristics, including traceability and decisions. The use of automated tools to accept the above information, perform static and dynamic consistency–completeness checking, validate the specifications by executing them, and generate required specification documents. The definition of a method for using the language and tools described as a sequence of steps, each of which adds a specific subset of the ERA and executable information and then uses the tools to check a subset of the consistency–completeness conditions. An intent to provide a smooth transition from system requirements and design through software requirements and design and testing. The SREM technology was developed over a 25-year period, with alternate periods of research, development, and prototype application to validate the concepts. Its research results were at the edge of the state of the art for more than 15 yr. It is unique in its breadth of coverage, and focuses on providing a smooth transition between the different phases of system design. Keywords: SREM; SYSREM; distributed computing design system (DCDS); use; requirements driven design; technology assessment