Un bel giorno rickman digitò:
>>> I believe his question is about the general safety requirement implying
>>> a hipot test. Not everything about a design has to be explicitly stated
>>> as a requirement.
>>
>> In the aerospace sector, it does! :-)
>
> You misunderstand. When engineers are given requirements for a project,
> or are asked to develop requirements, they start with the requirements
> derived from user "wants". These are top level requirements which are
> further refined. Many requirements are derived from the general
> requirement for the craft to be safe.
>
>> Of course, if you are developing on your own a "catalog" product (to be
>> sold to anyone who wants to buy it), it's up to you to decide which
>> standards to comply. But if you are answering to a specific RFI/RFQ or in
>> general you have to develop a product based on a requirement, it is
>> uncommon to add further requirements.
>
> That is *exactly* the situation I am describing. If a requirement is
> that the unit not catch fire when plugged into 220 volts even though it
> is designed only for 120 volt, this will generate requirements on
> specific parts of the design for specific ways of meeting the higher
> level requirement.
Well, of course. By following this reasoning, each engineering choice (like
selecting a capacitor with a specific voltage instead of another) may be
considered a requirement derived from another requirement and so on. I was
just referring to top-level requirements, which in the aerospace sector
have two very distinct characteristics:
(1) The customer gives you *all* the top-level requirements (functional,
environmental, EMC, electrical, mechanical etc etc, usually some hundreds
page of documents). Along with them, usually the customer gives you also
the general requirements for the equipments that have to be installed on
that specific aircraft(s). Usually some other thousand pages of documents.
You have plenty of informations and don't have to assume or add anything.
(2) You have to demonstrate the compliance only for the top-level
requirements, and report the verification method on the compliance matrix
(analysis, test, similarity etc). How you do achieve this compliance, is up
to you.
Hipot testing is by all means a top-level requirement. Like I said, it's
the manufacturer that decides whether it is required or not, based on the
equipment position on the aircraft, on the others equipments connected to
it, and so on. You usually don't have this kind of informations, and
therefore it's not up to you to decide.