The Requirements Discovery Process

Self Cite

Section: Systems Engineering Consensussupporting

confidence: 88%

No Matter What The Application, It Is Still Systems Engineering

Bahill

Gissing²

1997

Self Cite

“…(Archer, 1965) defined design as "a goal-directed problem solving activity". (Fielden, 1963) (Bahill and Dean, 1997) in discussing the requirements in the 'systems engineering process' call it the 'system design process' and use the terms 'design' and 'solution' interchangeably. And, (Hari, et al, 2004) provided an example of the various activities performed in new product design that overlap those of systems engineering.…”

Section: Discipline Campmentioning

confidence: 98%

“…(Fielden, 1963) defined 'engineering design' as "the use of scientific principles, technical information and imagination in the definition of a mechanical structure, machine or system to perform prespecified functions with the maximum economy and efficiency" and (Matchett and Briggs, 1966) defined 'design' as "the optimum solution to the sum of the true needs of a particular set of circumstances". (Bahill and Dean, 1997) in discussing the requirements in the 'systems engineering process' call it the 'system design process' and use the terms 'design' and 'solution' interchangeably. And, (Hari, et al, 2004) provided an example of the various activities performed in new product design that overlap those of systems engineering.…”

Section: Discipline Campmentioning

confidence: 99%

3.4.1 Yes systems engineering, you are a discipline

Kasser

Hitchins

2012

Systems engineering is currently characterized by conflicting and contradictory opinions on its nature. The paper begins by describing the evolution of systems engineering in the National Council on Systems Engineering (NCOSE)/ International Council on Systems Engineering (INCOSE) and the difficulty in defining and differentiating systems engineering as a discipline. The paper then identifies and discusses six different and somewhat contradictory camps or perspectives of systems engineering. After identifying the cause of the contradictions the paper suggests one way to reconcile the camps is to dissolve the problem to distinguish between the activity known as systems engineering and the role of the systems engineer with a return to the old pre-NCOSE systems engineering paradigm. The paper then continues by testing the hypothesis and shows that systems engineering is a discipline that can be differentiated from other disciplines. However, it is not a traditional engineering discipline.

“…Such methods as quality function deployment (QFD), prototyping (which is especially powerful for user interfaces), surveys, etc. are available to derive stakeholder requirements, whether the stakeholder is the customer (acquirer), user, maintainer, disposer, or just a "neighbor" (Boehm, et al 1997;Bahill and Dean 1997).…”

Section: Step One: Define the Problemmentioning

confidence: 99%

1.6.4 Requirements Completeness: A Deterministic Approach

Carson

1998

Abstract.A process for determining requirements completeness is developed. The method is comprised of three steps: (1) defining the problem to be solved by identifying and quantifying all system interfaces associated with the system development, operational, and maintenance concepts, (2) producing the requirements by analyzing the system interfaces to determine requirements under all conditions, and (3) verifying requirements completeness using the method of complementary antecedents (Carson 1995). The process allows one to demonstrate that requirements are complete for the associated mission (problem) statement(s).