摘要:

AbstractNumerous stakeholders collaborate to develop the system requirements for a complex system. They conceive needs, evaluate risk, cost and benefits, identify tradeoffs, and negotiate priorities over a considerable period of time. Government and industry need a structured approach to requirements elicitation that completely captures stakeholder requirements and supports necessary analysis, tradeoffs, and negotiation. Automated support for this collaborative process is a long term goal of our research1. Our initial goal is to develop a firm foundation for capturing requirements and supporting different views. This paper discusses the need for a structure that supports requirements capture and the advantages of such a structure, identifies problems in developing a structure, and provides a high level description of information that should be captured.

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01684.x

年代:1994

数据来源: WILEY

摘要:

ABSTRACTIn trying to implement requirements management on a project, several roadblocks may be encountered. By knowing the difficulties others have encountered, you will be able to anticipate the roadblocks and plan how to deal with them. This paper is part of a series being developed by the NCOSE Requirements Management Implementation Subcommittee of the Requirements Management Committee. Follow on papers will focus on solutions to the problems outlined.

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01685.x

年代:1994

数据来源: WILEY

摘要:

AbstractSystems engineers are concerned with identifying, allocating, and managing their customer requirements to appropriate design teams. However, as anyone involved with the design process can testify, contractual requirements are only one piece of the requirements management puzzle. Designs as well as requirements evolve and are iterated to very low levels of detail, with each succeeding level offering more complexity and additional requirements. Unless these added requirements are well‐understood and documented, costly mistakes or omissions can be introduced into the completed product. As the reader will see, system requirement definitions can and do go far beyond the initial mandates imposed by the custome

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01686.x

年代:1994

数据来源: WILEY

摘要:

AbstractPoor requirements can lead to cost and schedule overruns and are therefore a source of low quality products and stressful work environments. This paper introduces a “responsive constructivist” paradigm for use by systems engineers to address these concerns. The paradigm is “responsive” to stakeholder statements in a nonlinear but methodological manner. “Constructivist” refers to the abstract construction of problem space based on a linguistic understanding of the various stakeholder's worldview of the problem, not necessarily upon the “preordinate positivist” beliefs of science. This paradigm asserts the necessity of approaching requirements such that the human component is more formally embraced. This challenges requirements engineers to evaluate their own stance of curiosity and neutrality. Additionally, questioning types and patterns aid to gather different views of the problem. This responsive constructivist systems engineering paradigm can improve the quality of interpersonal communications, thereby resulting in higher quality requirements and alternate probl

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01687.x

年代:1994

数据来源: WILEY

摘要:

AbstractA requirements management system forms the natural framework for a systems engineering environment (SEE). Requirements control the whole system, and cover the whole lifecycle. Requirements are the means of communication between systems engineers and all the specialist disciplines. A SEE based on requirements allows control at any required level of detail. This approach allows an incremental approach to developing a complete project toolset. This paper defines a SEE, in relationship to a commercial requirements management tool, DOORS.Systems engineering covers systems‐level tasks, such as the creation of requirements, technical management, and verification management. Tools used for specialist tasks remain outside the SEE although it will need to communicate with thos

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01688.x

年代:1994

数据来源: WILEY

摘要:

AbstractUsing rapid prototypes for early validation can accelerate product development in all phases of the development life cycle. The most obvious benefit is the ability to evaluate requirements for applicability and unanticipated errors early in the development life cycle. However, additional benefits can also be realized during the follow‐on phases of the development life cycle. These benefits are often not considered as a part of the planning and decision making process regarding systems modeling tools. During the development of the 777 Autopilot Flight Director System (AFDS), system engineers at Collins Air Transport Division (CATD) evaluated both a conventional approach and a rapid prototyping approach in the development of two complex system functions. The lessons learned from this exercise could significantly change the way CATD system engineering teams approach system development in future project

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01689.x

年代:1994

数据来源: WILEY

摘要:

AbstractThis paper presents a process for generating capability requirements based upon intended/needed operations and mission objectives. The process addresses the uncertainties associated with:Understanding the customer/user problemSelecting analysis and documentation methods best suited to the problem.The uncertainty associated with the customer/user problem is addressed by having the process stringently separate the analysis phase from the requirements (“shall”) statements documentation phase.The uncertainty associated with analysis and documentation methods is addressed by having the process include an early phase in which one typical capability is analyzed in depth and then abstracted into requirements statements. The objective is to select and tailor methods prior to addressing the full range of capabilities that need to be specified.This paper also identifies the value that the current system modeling methods bring to the proc

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01690.x

年代:1994

数据来源: WILEY

摘要:

AbstractThe mid‐stream integration of a formal Requirements Management (RM) process into an existing Department of Defense (DOD) program with a traditional approach to design&development poses special challenges. A number of compromises are necessary to avoid disrupting the design processes that are in place and functioning on the program, while changing the traditional view of the design community on identifying and verifying proper implementation of requirements. Experience on a follow‐on development program, the F/A‐18E/F, illustrates some of the benefits and difficulties inv

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01691.x

年代:1994

数据来源: WILEY

摘要:

AbstractCompetitive advantage in an industry can be achieved by strategically entering a marketplace at the right time with a product that has the appropriate cost and operational capability to match the needs and maturity of the marketplace. In products (such as software‐based products) where the cost and time‐to‐market are primarily a function of the “intellectual” engineering process, the product development function is the source of competitive advantage.This paper introduces a system engineering framework that describes the relationship between product operational capability, development cost, and development cycle‐time (time‐to‐market). Analysis of this relationship yields four strategies for achieving and sustaining competitive advantage through prod

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01692.x

年代:1994

数据来源: WILEY

摘要:

AbstractEnd‐user involvement in the requirement specification phase is essential for the success of a software product. Software developers and architects must be able to easily and accurately translate the requirements to software codes; visualize interdependencies among different functions, objects and rules; and understand system limitations.Using the rapid prototyping technique in the requirement analysis and specification phase is one way of achieving the goals of high quality software, lower development cost, on‐time delivery and user satisfaction.This paper discusses the use of the rapid prototyping technique in the requirements phase of a software development cycle. It describes the advantages of using prototyping in all applications, especially in the design and development of systems which have complex user interfaces. The paper explores the user‐centered approach in relation to the rapid prototyping technique.The rapid prototyping technique has been successfully used in several AT&T software projects. This paper also includes the authors' experiences in applying the technique to software pro

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1994.tb01693.x

年代:1994

数据来源: WILEY