ably ▁or ▁for ▁developing ▁human ly ▁functional ▁and ▁a est het ically ▁ple asing ▁products . ▁ ▁Arch itect s ▁are ▁expected ▁to ▁understand ▁human ▁needs ▁and ▁develop ▁human ly ▁functional ▁and ▁a est het ically ▁ple asing ▁products . ▁A ▁good ▁architect ▁is ▁a ▁transl ator ▁between ▁the ▁user / sp ons or ▁and ▁the ▁engine ers — and ▁even ▁among ▁just ▁engine ers ▁of ▁different ▁special ties . ▁ ▁A ▁good ▁architect ▁is ▁also ▁the ▁principal ▁ke eper ▁of ▁the ▁user ' s ▁vision ▁of ▁the ▁end ▁product — and ▁of ▁the ▁process ▁of ▁der iving ▁requirements ▁from ▁and ▁implementing ▁that ▁vision . ▁ ▁Det erm ining ▁what ▁the ▁users / sp ons ors ▁actually ▁want , ▁rather ▁than ▁what ▁they ▁say ▁they ▁want , ▁is ▁not ▁engineering — it ▁is ▁an ▁art . ▁ ▁An ▁architect ▁does ▁not ▁follow ▁an ▁exact ▁procedure . ▁ ▁S / he ▁communic ates ▁with ▁users / sp ons ors ▁in ▁a ▁highly ▁interactive ▁way — t ogether ▁they ▁extract ▁the ▁true ▁requirements ▁necessary ▁for ▁the ▁engine ered ▁system . ▁ ▁The ▁hardware ▁architect ▁must ▁remain ▁constantly ▁in ▁communication ▁with ▁the ▁end ▁users ▁( or ▁a ▁systems ▁architect ). ▁ ▁Therefore , ▁the ▁architect ▁must ▁be ▁familiar ▁with ▁the ▁user ' s ▁environment ▁and ▁problem . ▁ ▁The ▁engineer ▁need ▁only ▁be ▁very ▁knowledge able ▁of ▁the ▁potential ▁engineering ▁solution ▁space . ▁ ▁High - level ▁requirements ▁The ▁user / sp ons or ▁should ▁view ▁the ▁architect ▁as ▁the ▁user ' s ▁representative ▁and ▁provide