▁problems ▁and ▁solutions ▁in ▁the ▁user ' s ▁world . ▁ ▁It ▁is ▁princip ally ▁captured ▁in ▁the ▁computer – human ▁interfaces ▁( CH I ) ▁of ▁the ▁engine ered ▁system . ▁ ▁The ▁engine ered ▁system ▁represents ▁the ▁engineering ▁solutions — how ▁the ▁engineer ▁propos es ▁to ▁develop ▁and / or ▁select ▁and ▁combine ▁the ▁components ▁of ▁the ▁technical ▁infrastr ucture ▁to ▁support ▁the ▁CH I . ▁ ▁In ▁the ▁absence ▁of ▁an ▁architect , ▁there ▁is ▁an ▁un fortun ate ▁t endency ▁to ▁conf use ▁the ▁two ▁architect ures , ▁since ▁the ▁engineer ▁thinks ▁in ▁terms ▁of ▁hardware , ▁but ▁the ▁user ▁may ▁be ▁thinking ▁in ▁terms ▁of ▁solving ▁a ▁problem ▁of ▁getting ▁people ▁from ▁point ▁A ▁to ▁point ▁B ▁in ▁a ▁reasonable ▁amount ▁of ▁time ▁and ▁with ▁a ▁reasonable ▁exp end iture ▁of ▁energy , ▁or ▁of ▁getting ▁needed ▁information ▁to ▁customers ▁and ▁staff . ▁A ▁hardware ▁architect ▁is ▁expected ▁to ▁combine ▁knowledge ▁of ▁both ▁the ▁architecture ▁of ▁the ▁user ' s ▁world ▁and ▁of ▁( all ▁potentially ▁useful ) ▁hardware ▁engineering ▁architect ures . ▁ ▁The ▁former ▁is ▁a ▁joint ▁activity ▁with ▁the ▁user ; ▁the ▁latter ▁is ▁a ▁joint ▁activity ▁with ▁the ▁engine ers . ▁ ▁The ▁product ▁is ▁a ▁set ▁of ▁high ▁level ▁requirements ▁reflect ing ▁the ▁user ' s ▁requirements ▁which ▁can ▁be ▁used ▁by ▁the ▁engine ers ▁to ▁develop ▁hardware ▁systems ▁design ▁requirements . ▁ ▁Because ▁requirements ▁evol ve ▁over ▁the ▁course ▁of ▁a ▁project , ▁especially ▁a ▁long ▁one , ▁an ▁architect ▁is ▁needed