Analyzing Requirements—Evolution In Engineering Design Using The Method Of Problem-Reduction  

Oleh:

Eodice, Michael T. ; Leifer, Larry J. ; Fruchter, Renate

Jenis: Article from Journal - ilmiah internasional
Dalam koleksi: Concurrent Engineering vol. 8 no. 2 (Jun. 2000), page 104-114.
Topik: design theory; requirements; needs-analysis; product design; problem-reduction; information modelling.
Fulltext: 104.pdf (1.09MB)

Isi artikel

Traditional requirements definition activities begin with the engineer or design team performing a needs-analysis to identify user requirements [5]. While recent studies have focused on Conceptual Design activities, research into the requirements-definition process has for the most part been lacking. Needs-analysis is generally subjective, and varies according to the composition and experience of the design team. Systematic procedures for defining and ranking requirements could consolidate the foundation on which the design process is predicated and enhance its outcome by providing the designer with a consistent, reliable approach to product development [1]. Before such systematic procedures could be developed, it would be necessary to establish an understanding of the existing process by which requirements evolve, and to create a model for evaluating this process. Therefore, a pilot study was conducted at Stanford University using empirical data from an actual spaceflight experiment, sponsored by NASA Ames Research Center (ARC), and flown aboard the Space Shuttle. A large body of empirical evidence was examined, and on the basis of this evidence, the method of problem-reduction using AND/OR graphs proved to be an effective framework for analyzing requirements-evolution.

Opini Anda

Klik untuk menuliskan opini Anda tentang koleksi ini!

Kembali