▁and ▁much ▁engineering ▁talent . ▁ ▁If ▁the ▁engine ered ▁system ▁is ▁large ▁and ▁complex ▁enough , ▁the ▁chief ▁hardware ▁systems ▁architect ▁may ▁de fer ▁to ▁sub ordinate ▁architect s ▁for ▁parts ▁of ▁the ▁job , ▁although ▁they ▁all ▁may ▁be ▁members ▁of ▁a ▁joint ▁architect ural ▁team . ▁ ▁But ▁the ▁architect ▁must ▁never ▁be ▁viewed ▁as ▁an ▁engineering ▁super visor . ▁ ▁The ▁architect ▁should ▁sub - alloc ate ▁the ▁hardware ▁requirements ▁to ▁major ▁components ▁or ▁sub system s ▁that ▁are ▁within ▁the ▁scope ▁of ▁a ▁single ▁hardware ▁engineer , ▁or ▁engineering ▁manager ▁or ▁sub ordinate ▁architect . ▁ ▁Ide ally , ▁each ▁such ▁hardware ▁component / sub system ▁is ▁a ▁sufficiently ▁stand - alone ▁object ▁that ▁it ▁can ▁be ▁tested ▁as ▁a ▁complete ▁component , ▁separate ▁from ▁the ▁whole , ▁using ▁only ▁a ▁simple ▁test bed ▁to ▁supply ▁sim ulated ▁inputs ▁and ▁record ▁outputs . ▁ ▁That ▁is , ▁it ▁is ▁not ▁necessary ▁to ▁know ▁how ▁an ▁air ▁traffic ▁control ▁system ▁works ▁in ▁order ▁to ▁design ▁and ▁build ▁a ▁data ▁management ▁sub system ▁for ▁it . ▁ ▁It ▁is ▁only ▁necessary ▁to ▁know ▁the ▁constraints ▁under ▁which ▁the ▁sub system ▁will ▁be ▁expected ▁to ▁operate . ▁ ▁A ▁good ▁architect ▁ens ures ▁that ▁the ▁system , ▁however ▁complex , ▁is ▁built ▁upon ▁relatively ▁simple ▁and ▁" clean " ▁concepts ▁for ▁each ▁( sub ) ▁system ▁or ▁layer — e as ily ▁understand able ▁by ▁everyone , ▁especially ▁the ▁user , ▁without ▁special ▁training . ▁The ▁architect ▁will ▁use ▁a ▁minimum