5 Matching Results

Search Results

Advanced search parameters have been applied.

What is systems engineering?

Description: Systems Engineering is an interdisciplinary process that ensures that the customers` needs are satisfied throughout a system`s entire life cycle. This process includes: understanding customer needs; stating the problem; specifying requirements; defining performance and cost measures, prescribing tests, validating requirements, conducting design reviews, exploring alternative concepts, sensitivity analyses, functional decomposition, system design, designing and managing interfaces, system integration, total system test, configuration management, risk management, reliability analysis; total quality management; project management; and documentation. Material for this paper was gathered from senior Systems Engineers at Sandia National Laboratories.
Date: August 1, 1995
Creator: Bahill, A.T.
Partner: UNT Libraries Government Documents Department

Application of fuzzy technology to risk-based design and decision problems

Description: A study was undertaken to assess the impact of employing fuzzy technologies in areas of complex weapon system design. The technology was examined for use in a life-cycle cost exercise with the objective of providing a foundation from which to make service life assessments and recommendations on future weapon systems. The issues associated with this problem can be highly subjective and often exhibit a high degree of functional as well as variable uncertainty, ambiguity and noise. The study demonstrated that there is a potential role for the technology, but only in a hybridized environment not as a stand-alone solution methodology.
Date: February 1, 1995
Creator: Senglaub, M.E. & Bahill, A.T.
Partner: UNT Libraries Government Documents Department

Discovering system requirements

Description: Cost and schedule overruns are often caused by poor requirements that are produced by people who do not understand the requirements process. This report provides a high-level overview of the system requirements process, explaining types, sources, and characteristics of good requirements. System requirements, however, are seldom stated by the customer. Therefore, this report shows ways to help you work with your customer to discover the system requirements. It also explains terminology commonly used in the requirements development field, such as verification, validation, technical performance measures, and the various design reviews.
Date: July 1, 1996
Creator: Bahill, A.T.; Bentz, B. & Dean, F.F.
Partner: UNT Libraries Government Documents Department

A road map for implementing systems engineering

Description: Studies by academia, industry, and government indicate that applying a sound systems engineering process to development programs is an important tool for preventing cost and schedule overruns and performance deficiencies. There is an enormous body of systems engineering knowledge. Where does one start? How can the principles of systems engineering be applied in the Sandia environment? This road map is intended to be an aid to answering these questions.
Date: February 1, 1997
Creator: Dean, F.F.; Bentz, B. & Bahill, A.T.
Partner: UNT Libraries Government Documents Department

The requirements discovery process

Description: Cost and schedule overruns are often caused by poor requirements that are produced by people who do not understand the requirement process. This paper provides a high-level overview of the requirements discovery process.
Date: February 1, 1997
Creator: Bahill, A.T. & Dean, F.F.
Partner: UNT Libraries Government Documents Department