▁systems ▁architect ▁or ▁client ▁st ake hold ers . ▁ ▁It ▁is ▁extra ordin arily ▁rare ▁now ad ays ▁for ▁sufficiently ▁large ▁and / or ▁complex ▁hardware ▁systems ▁that ▁require ▁a ▁hardware ▁architect ▁not ▁to ▁require ▁substantial ▁software ▁and ▁a ▁systems ▁architect . ▁The ▁hardware ▁architect ▁will ▁therefore ▁normally ▁interface ▁with ▁a ▁systems ▁architect , ▁rather ▁than ▁directly ▁with ▁user ( s ), ▁spons or ( s ), ▁or ▁other ▁client ▁st ake hold ers . ▁However , ▁in ▁the ▁absence ▁of ▁a ▁systems ▁architect , ▁the ▁hardware ▁systems ▁architect ▁must ▁be ▁prepared ▁to ▁interface ▁directly ▁with ▁the ▁client ▁st ake hold ers ▁in ▁order ▁to ▁determine ▁their ▁( e vol ving ) ▁needs ▁to ▁be ▁realized ▁in ▁hardware . ▁ ▁The ▁hardware ▁architect ▁may ▁also ▁need ▁to ▁interface ▁directly ▁with ▁a ▁software ▁architect ▁or ▁engineer ( s ), ▁or ▁with ▁other ▁mechanical ▁or ▁elect rical ▁engine ers . ▁Gener ating ▁the ▁highest ▁level ▁of ▁hardware ▁requirements , ▁based ▁on ▁the ▁user ' s ▁needs ▁and ▁other ▁constraints ▁such ▁as ▁cost ▁and ▁schedule . ▁Ens uring ▁that ▁this ▁set ▁of ▁high ▁level ▁requirements ▁is ▁consistent , ▁complete , ▁correct , ▁and ▁operation ally ▁defined . ▁Perform ing ▁cost – ben ef it ▁anal ys es ▁to ▁determine ▁the ▁best ▁methods ▁or ▁approaches ▁for ▁meeting ▁the ▁hardware ▁requirements ; ▁making ▁maximum ▁use ▁of ▁commercial ▁off - the - sh elf ▁or ▁already ▁developed ▁components . ▁Develop ing ▁partition ing ▁algorithms ▁( and ▁other ▁processes ) ▁to ▁allocate ▁all ▁present ▁and ▁for ese e able