This paper identifies and documents the major characteristics of well defined requirements for both individual requirements and aggregates of requirements such as those found in specifications. Characteristics exhibited by well defined requirements are described. The descriptions are followed by a brief discussion of the characteristics. A few examples of well defined requirements are provided. Some supporting characteristics of requirements are also described. These supporting characteristics are not properties of the requirements themselves but are attributes assigned to individual requirements to assist in managing the requirements through the life cycle. The paper was written and reviewed by members of the requirements working group of the INCOSE.

No abstract

Interfacing requirements management software tools with other tools can facilitate the requirements management process by allowing people to exchange requirements more easily, to use the optimum tools in their work, and to adapt to tool changes. In this exploratory paper we attempt to provide some useful information to requirement tool users and developers who need to specify or devise requirement tool interfaces. Examination of a simple hierarchical requirement data flow model suggests major interfaces of Document import / parsing Derivation analyses Publication (electronic and / or paper) Flowdown to lower level Database import / export Companion programs (e.g. graphics editors) The model presented suggests the type of data that should flow across these interfaces. Twelve commercial requirements management tools are identified in this paper, and a couple of interface file formats are illustrated. Some generalizations are made, such as that each data item should be entered once and reside in a single master location where possible. Several examples of actual implementations illustrate accomplishments and practical difficulties encountered. Also eight commercial / consortium tool integration efforts are summarized with lists of the major tools involved, and a couple of standardization efforts are described, including a major European effort, SEDRES. Some work by INCOSE in identifying requirements data is recommended in this paper. Not all of the topics in this paper are covered in detail, but we think that a significant amount of useful information is provided.

The complexity of modern hardware/software systems, the reduction in defense funding levels, and the desire of DoD (US Department of Defense) to reduce the acquisition cycle using Simulation Based Acquisition have significantly impacted the manner in which new weapon systems are concepted, designed, integrated, tested, produced, and supported throughout their life cycles. The traditional approaches for engineering systems are no longer adequate for rapid developments and must be modernized in an integrated methodology to take advantage of the significant advancements in computer technologies. Many efforts using computer technology up to this point in time have been fragmented and lacked a systematic approach to make full use of the technologies. By taking advantage of the advances in microprocessors and software to create a System Integration Environment (SIE), a Simulation ‐ Emulation ‐ Stimulation (SES) Process can be developed that handles all aspects of the life cycle including system analysis, design, documentation, test and evaluation (T&E), integration and training. This paper reports on some of the advances that have been made thus far in developing such a System Integrated Environment for use in Army and Navy Combat System Developments.

This paper describes the system definition and integration approach adopted for the Bradley Fighting Vehicle (BFV) M2A3 Engineering and Manufacturing Development (EMD) program at United Defense LP. The BFV A3 Upgrade program incorporates lessons learned in the Desert Storm Operation. Upgrades are primarily in the area of fire control, electronics and software.Modern electronics and software systems are relatively complex. Subsystems have to be integrated so that they perform cohesively to implement sophisticated system functions with minimal supervision from human operators. This cohesive implementation, or system integration, requires special discipline, knowhow, facility, and organization. This paper describes a systems engineering approach that allows an understanding of the system early in the program, identifies problem areas and generates candidate solutions before commencement of system design.It also describes the advantages of this approach.The approach described was used on the BFV A3 program. A System Integration Laboratory (SIL) was constructed and a rapid prototyping methodology was adopted to generate a simulation, emulation, and stimulation (SES) early in the program to allow for a better understanding of the overall system. The SIL also created an incremental integration environment that allowed the system to be integrated using the philosophy of "build-alittle, test-a-little, and integrate-a-little" to simplify the integration tasks and reduce program risk.