Untitled Quiz
72 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the first step of the design process?

Identify a need.

What are the requirements you specify that will be used to make decisions about how to build and evaluate the product called?

Design criteria

What is the purpose of evaluating alternative designs?

To research into possible solutions, discover where knowledge and science limit solutions, find ways to improve previous solutions, and identify different approaches to meet design objectives.

What is the goal of prototyping?

<p>To actually build a product based on the detailed design.</p> Signup and view all the answers

What is the purpose of testing and evaluating the prototype?

<p>To show how well the product meets the identified need.</p> Signup and view all the answers

What will disclose some deficiencies in your design?

<p>Testing</p> Signup and view all the answers

What is the base of the design process?

<p>Creating a satisfactory solution to a need.</p> Signup and view all the answers

Engineering is all about achieving a desired outcome using knowledge and know-how.

<p>True</p> Signup and view all the answers

Designing is not a form of problem solving.

<p>False</p> Signup and view all the answers

Engineers are not applications specialists.

<p>False</p> Signup and view all the answers

What are the necessary attributes defined for a system before and during design called?

<p>Requirements</p> Signup and view all the answers

What is the ultimate system requirement from which all other requirements flow?

<p>The customer's need.</p> Signup and view all the answers

What should requirements state?

<p>What the system is to do.</p> Signup and view all the answers

Which of the following are types of system requirements?

<p>Mandatory</p> Signup and view all the answers

What do mandatory requirements specify?

<p>The necessary and sufficient conditions for a minimal system to be acceptable.</p> Signup and view all the answers

Mandatory requirements are usually expressed with "shall" and "must".

<p>True</p> Signup and view all the answers

Mandatory requirements must use scoring functions.

<p>False</p> Signup and view all the answers

Mandatory requirements are susceptible to trade-offs.

<p>False</p> Signup and view all the answers

What do preference requirements state?

<p>Conditions that would make the customer happier.</p> Signup and view all the answers

Preference requirements are often expressed with "should" and "want".

<p>True</p> Signup and view all the answers

Preference requirements should use scoring functions.

<p>True</p> Signup and view all the answers

Preference requirements should be evaluated with a multicriteria decision technique.

<p>True</p> Signup and view all the answers

What does the term "customer" include?

<p>Anyone who has a right to impose requirements on the system.</p> Signup and view all the answers

The customer is only the end user who will utilize the system.

<p>False</p> Signup and view all the answers

What is one of the most important tasks for a Systems Engineer?

<p>Stating the problem clearly and unambiguously.</p> Signup and view all the answers

The problem should be stated in terms of preconceived solutions.

<p>False</p> Signup and view all the answers

What is a better way to state the problem?

<p>In terms of the deficiency that must be ameliorated.</p> Signup and view all the answers

What are two dozen of the most common sources of requirements?

<p>Input-Output, Technology, Performance, Cost, Trade-off, System test, Company Policy, Business Practices, Systems Engineering, Project Management, Marketing, Manufacturing Processes, Design Engineers, Reliability, Safety, The Environment, Ethics, Intangibles, Common Sense, Laws or Standards, The Customer, Legacy Requirements, Data Collection Activities, and Other Sources.</p> Signup and view all the answers

Wymore (1993) suggests that only the first six sources of requirements are necessary.

<p>True</p> Signup and view all the answers

What does the technology requirement specify?

<p>The set of components, such as hardware, software, and bioware, that is available to build the system.</p> Signup and view all the answers

What do performance requirements include?

<p>Quantity, quality, coverage, timeliness, and readiness.</p> Signup and view all the answers

What is the purpose of the system test?

<p>To verify that the design and the system satisfy the requirements.</p> Signup and view all the answers

What is one way in which company policy can be used to state requirements?

<p>By dictating specific components to be manufactured in-house and other components to be purchased from external sources.</p> Signup and view all the answers

What might business practices require?

<p>Work Breakdown Structures, PERT Charts, Quality Manuals, Environmental Safety and Health Plans, or a certain return on investment.</p> Signup and view all the answers

Access to source code for all software is not a project management requirement.

<p>False</p> Signup and view all the answers

What are features that customers did not know they wanted called?

<p>Exciters</p> Signup and view all the answers

What might manufacturing processes require?

<p>A specific manufacturing process or environment.</p> Signup and view all the answers

Design engineers impose requirements on the system in terms of "build to," "code to," and "buy to" requirements for products, and "how to execute" requirements for processes.

<p>True</p> Signup and view all the answers

Reliability can be a performance requirement, or it can be broken out separately.

<p>True</p> Signup and view all the answers

What is a good example of a requirement that comes from safety consideration?

<p>How the item should behave under both normal and abnormal conditions.</p> Signup and view all the answers

Ethics can require physicians to obtain informed consent before experimenting on human subjects.

<p>True</p> Signup and view all the answers

What are some examples of intangible items that customers might desire?

<p>These intangible aspects are subjective and difficult to quantify, yet can significantly influence customer satisfaction and business outcomes.</p> Signup and view all the answers

Common sense requirements are usually stated explicitly.

<p>False</p> Signup and view all the answers

What can requirements specify compliance with?

<p>Laws or standards.</p> Signup and view all the answers

Requirements that come from the customer are not based on statements of fact and assumptions.

<p>False</p> Signup and view all the answers

The customer's need is rarely considered during requirements gathering and analysis.

<p>False</p> Signup and view all the answers

What are legacy requirements?

<p>Definite requirements that are not stated but are based on previous experiences with similar systems.</p> Signup and view all the answers

Data collection activities can help discover system requirements because each piece of data collected should be traceable to a specific system requirement.

<p>True</p> Signup and view all the answers

What are some examples of other sources of system requirements?

<p>Human factors, the environment, the end user, the operator, potential victims, management, company vision, future expansion, schedule, logistics, politics, public opinion, business partners, past failures, competitive intelligence, liability, religion, culture, government agencies.</p> Signup and view all the answers

One or more of the designs must be fabricated before thorough testing can be done to ensure the product meets performance specifications.

<p>True</p> Signup and view all the answers

Based on the results of the testing, the design might not be finalized.

<p>False</p> Signup and view all the answers

It is not important to ensure that each test explicitly links to a specific requirement.

<p>False</p> Signup and view all the answers

Describing the system tests does not inform the producers how the system will be tested.

<p>False</p> Signup and view all the answers

Validating a system involves building the system, making sure it does what it is supposed to do, and ensuring the system meets the customer's needs.

<p>True</p> Signup and view all the answers

Validating a system determines completeness of the system.

<p>True</p> Signup and view all the answers

Validating requirements involves ensuring that the set of requirements is consistent, that a real-world solution can be built, and that such a system can be proven.

<p>True</p> Signup and view all the answers

If systems engineering discovers that a customer has requested a perpetual-motion machine, the project should be continued.

<p>False</p> Signup and view all the answers

Verifying a system involves building the system right, ensuring the system complies, and verifying the conformance.

<p>True</p> Signup and view all the answers

Verifying a system determines the conformance of the system to its design requirements.

<p>True</p> Signup and view all the answers

Verifying a system guarantees the consistency at the end of each phase.

<p>True</p> Signup and view all the answers

Verifying a system guarantees a smooth transition from model to prototype to preproduction.

<p>True</p> Signup and view all the answers

Verifying requirements involves examination, analysis, test, or documentation.

<p>False</p> Signup and view all the answers

The process of verifying requirements is linear and not iterative.

<p>False</p> Signup and view all the answers

Requirements should be verified with respect to the model, the prototype, and the production.

<p>True</p> Signup and view all the answers

For Systems Engineers, validating requirements involves proving that it is possible to satisfy them.

<p>True</p> Signup and view all the answers

System verification is a process of proving that a system does not meet its requirements.

<p>False</p> Signup and view all the answers

ISO-9000 tells you to verify that a design meets the requirements and validate the product.

<p>True</p> Signup and view all the answers

If you did a good job and accurately documented the design, prototyping should be complicated.

<p>False</p> Signup and view all the answers

If you find yourself continuing to work out the details of the solution, you should go back to detailed design and make corrections.

<p>True</p> Signup and view all the answers

What are the three purposes of prototypes?

<p>To demonstrate function, to understand look and feel, and to give a sense of usability.</p> Signup and view all the answers

A look and feel prototype is used to understand the form and appearance of a design.

<p>True</p> Signup and view all the answers

Role prototypes are used to show how and under what contexts a product might be used.

<p>True</p> Signup and view all the answers

Study Notes

Engineering Design Process

  • The core of the design process is finding a solution to a need.
  • Needs can involve improving current conditions, fixing problems, or deriving uses for new ideas.
  • Engineering is about gaining a desired outcome, achieved through methodical problem-solving.
  • Engineers are seen as problem-solving specialists using established concepts, experiments, and previous discoveries.

Design Steps

  • Stage 1: Identifying the design problem.
  • Stage 2: Developing problem-solving concepts and ideas.
  • Stage 3: Creating a compromise solution.
  • Stage 4: Producing prototypes or models.
  • Stage 5: Constructing working drawings.

Step 1: Identifying a Need

  • Needs, or problems to be solved, are often discovered by the product users (customers).
  • Customers can be retail consumers or other teams in a product development process.

Step 2: Establishing Design Criteria and Constraints

  • Design criteria define the requirements for the product.
  • Criteria are derived from user needs and explain physical and functional characteristics.
  • Examples of criteria include shape, size, weight, speed, ruggedness, and ease of manufacturing.

Step 3: Evaluating Alternative Designs

  • Researching past solutions helps identify limitations and potential avenues for improvement.
  • Evaluate at least two to three alternative designs, considering available technology, revisions to existing designs, or novel solutions.

Development of Alternative Designs

  • The process involves creativity use of engineering tools, Computer-Aided Design (CAD), and computer modeling
  • The development process includes stress analysis, material science, and manufacturing processes.
  • All constraints—available materials, personnel, and facilities—must be taken into account.

Step 4: Building a Prototype of the Best Design

  • Select the design that best fulfills the criteria and constraints.
  • A prototype is a functional small-scale representation of a new type or design.
  • Cost limitations may lead to partial or reduced-scale models. Prototype definitions:
    • An original model upon which something is patterned
    • A standard or typical example
    • A full-scale, functional form of a new type or design

Step 5: Testing and Evaluating the Prototype

  • Develop a test plan to evaluate the prototype against established design criteria.
  • Test the prototype under actual or simulated operational conditions.
  • Customer feedback is crucial in the product testing phase.

Step 6: Analyzing Test Results, Making Design Changes, and Retesting

  • Evaluate test results to identify design flaws.
  • Implement corrections and repeat the testing process.
  • Document all analyses, adjustments, and testing in a project journal.

Design Requirements

  • Requirements delineate the necessary features of a system.

  • These characteristics are specified before and during the design.

  • User/customer needs are the foundation of all other system requirements.

  • Requirements identify the essential needs of a system for it to be functional and valuable.

  • Requirements clarify a common understanding of desired system properties.

  • Two types of requirements: Mandatory and preference.

  • Mandatory requirements specify essential conditions for system acceptability, often stated using "shall" and "must."

  • Preference requirements describe desired characteristics to improve user experience, usually using "should" or "want."

Defining the Customer

  • The customer encompasses anyone with the right to impose requirements on the design.
  • This includes end-users, operators, bill payers, owners, regulatory agencies, victims, and sponsors.
  • Systems Engineering considerations must account for both the product itself and how it's made, and therefore must also include testing customer of the process.

Stating the Problem

  • Clearly and unambiguously define the problem.
  • State the desired state if the problem did not exist, rather than focusing on preconceived solutions.
  • Alternatively, focus on the deficiency to be rectified, stimulating more design options.

Sources of Requirements

  • A list of potential factors that necessitate requirements for the design.
  • Examples: Input-Output, Technology, Performance, Cost, Trade-offs, and System Test.
  • Other factors include Functional, Performance, Constraints, Verification, and Programmatic.
  • The EIA/ANSI-632 standard lists only three criteria: Functional, Performance, and Constraints.

Input-Output

  • Requirements relating inputs and outputs of a system—example for an electronic amplifier.

Technology

  • Characteristics of hardware, software, or both that limit or enable the system design.

Performance

  • Requirements for quantity, quality, coverage area, timeliness, and readiness.

Cost

  • Manpower, resources, and monetary factors. Cost limitations may affect design parameters.

Trade-off

  • Different relative values of performance and cost criteria. Example, assigning weights (0.6 for performing characteristics and 0.4 for cost).

System Testing

  • Ensures design and system satisfy the specified requirements. Example with electronic amplifier (audio input).

Company Policy

  • Corporate policies can define the requirements relating to the design.

Business Practices

  • Corporate policies may include work breakdown structures, PERT charts, safety procedures, risk assessment, and investment return requirements.

Systems Engineering

  • Systems and software design requirements may include mandatory Readme files for hardware and software.

Project Management

  • Access to source code for software needs may be a prerequisite.

Marketing

  • Focus on exciting and delighting the customer. Features that meet previously unstated customer needs are included here (e.g., customer need for portability was unknown in the 1970s).

Manufacturing Processes

  • Requirements relating to the manufacturing process (e.g., the need for a clean room for semiconductor manufacture).

Design Engineers

  • Design engineers specify "build-to," "code-to," and "buy-to" requirements for products and "how-to-execute" requirements for processes.

Reliability

  • Design reliability can be a performance metric or a separate category.

Safety

  • Safety requirements concerning behavior under normal and abnormal conditions.

The Environment

  • Impact of environmental factors such as banning ozone-depleting chemicals or other regulations.

Ethics

  • Ethical considerations regarding testing on human subjects may form requirements.

Intangibles

  • Requirements for factors that are difficult to quantify, such as customer preferences, aesthetics, company prestige, technology leadership, or business expansion.

Common Sense

  • Unstated requirements assumed to be common knowledge; for instance, certain design characteristics about humans (e.g., they have two hands).

Laws and Standards

  • Laws, standards (e.g., building codes), and regulations may define system requirements.

The Customer

  • Statements of fact, assumptions, and expectations of end-users create specific requirements. These may arise from documented needs, acquisition, or mission analyses.

Legacy Requirements

  • Customer requirements may be implicitly understood based on prior systems' design experiences (e.g., a new system must be as durable as an old one).

Data Collection Activities

  • To understand existing systems, apply existing data collection methods to determine system requirements.

Other Sources

  • Further system requirements can come from varied factors such as human factors, environment, user, operator, potential victims, management, company goals, schedule, and other factors.

Validating a System

  • Confirming building the right system that has the expected outcome, meeting customer needs, and completeness.

Validating Requirements

  • Consistency, realistic construction from requirements, and verification that the created system meets the requirements.

Verifying a System

  • Checking that the built components match the design requirements, guaranteeing reliable development phases and a smooth transition from design to production.

Verifying Requirements

  • Processes of examination, testing, or demonstration to prove a requirement's fulfillment. Ensuring that validated requirements are capable of being implemented (e.g., ensuring there is no technological limitation). This is an ongoing process. ISO-9000 guidance also exists.

Prototyping

  • Prototyping represents the practical building of a product based on the detailed design. The goal is producing a working item that follows all the described parameters. Any needed revisions are identified during this process.

Prototypes: Purposes

  • Functional prototypes demonstrate the system's ability to operate in a specified manner.
  • Look-and-feel prototypes showcase system aesthetic quality (appearance).
  • Role prototypes illustrate usability for the end-user by identifying practical use-cases.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Quiz Team

Related Documents

5 Design Steps PDF

More Like This

Untitled Quiz
37 questions

Untitled Quiz

WellReceivedSquirrel7948 avatar
WellReceivedSquirrel7948
Untitled Quiz
55 questions

Untitled Quiz

StatuesquePrimrose avatar
StatuesquePrimrose
Untitled Quiz
50 questions

Untitled Quiz

JoyousSulfur avatar
JoyousSulfur
Untitled Quiz
48 questions

Untitled Quiz

StraightforwardStatueOfLiberty avatar
StraightforwardStatueOfLiberty
Use Quizgecko on...
Browser
Browser