▁( hard ware ) ▁requirements ▁into ▁discrete ▁hardware ▁partitions ▁such ▁that ▁a ▁minimum ▁of ▁communic ations ▁is ▁needed ▁among ▁partitions , ▁and ▁between ▁the ▁user ▁and ▁the ▁system . ▁ ▁Part ition ing ▁large ▁hardware ▁systems ▁into ▁( success ive ▁layers ▁of ) ▁sub system s ▁and ▁components ▁each ▁of ▁which ▁can ▁be ▁handled ▁by ▁a ▁single ▁hardware ▁engineer ▁or ▁team ▁of ▁engine ers . ▁Ens uring ▁that ▁maxim ally ▁robust ▁hardware ▁architecture ▁is ▁developed . ▁Gener ating ▁a ▁set ▁of ▁accept ance ▁test ▁requirements , ▁together ▁with ▁the ▁design ers , ▁test ▁engine ers , ▁and ▁the ▁user , ▁which ▁determine ▁that ▁all ▁of ▁the ▁high ▁level ▁hardware ▁requirements ▁have ▁been ▁met , ▁especially ▁for ▁the ▁computer - human - interface . ▁Gener ating ▁products ▁such ▁as ▁sketch es , ▁models , ▁an ▁early ▁user ' s ▁manual , ▁and ▁pro tot ypes ▁to ▁keep ▁the ▁user ▁and ▁the ▁engine ers ▁constantly ▁up ▁to ▁date ▁and ▁in ▁agreement ▁on ▁the ▁system ▁to ▁be ▁provided ▁as ▁it ▁is ▁evol ving . ▁ ▁Background ▁Lar ge ▁systems ▁architecture ▁was ▁developed ▁as ▁a ▁way ▁to ▁handle ▁systems ▁too ▁large ▁for ▁one ▁person ▁to ▁conce ive ▁of , ▁let ▁alone ▁design . ▁ ▁Systems ▁of ▁this ▁size ▁are ▁rapidly ▁becoming ▁the ▁norm , ▁so ▁architect ural ▁approaches ▁and ▁architect s ▁are ▁increasing ly ▁needed ▁to ▁solve ▁the ▁problems ▁of ▁large ▁systems . ▁ ▁Users ▁and ▁spons ors ▁Engine ers ▁as ▁a ▁group ▁do ▁not ▁have ▁a ▁reputation ▁for ▁understanding ▁and ▁respond ing ▁to ▁human ▁needs ▁comfort