Enterprise Architecture – goals and scope of analysis and modeling

Enter­prise Archi­tec­ture – goals and scope of ana­lyzes and mod­el­ing­Pur­pose and bene­fit­sThe primary goal of ana­lyz­ing and mod­el­ing the entire com­pany, at a pre­de­ter­mined level of detail (or rather the level of gen­er­al­ity), is to determ­ine the con­text for spe­cif­ic loc­al, domain-spe­cif­ic pro­jects. The whole mod­el con­tains inform­a­tion about the doc­u­ment flow and the IT sys­tems sup­port­ing it. The key bene­fit of hav­ing a doc­u­mented Enter­prise Archi­tec­ture is an even sev­er­al-fold reduc­tion in the costs of ongo­ing man­age­ment and devel­op­ment of the IT sys­tem, The key bene­fit of hav­ing a doc­u­mented Enter­prise Archi­tec­ture is even a sev­er­al-fold reduc­tion in the costs of cur­rent com­pany man­age­ment and the costs of IT sys­tem devel­op­ment. Giv­en mod­els we have:possibility to make organ­iz­a­tion­al decisions imme­di­ately and without risk: doc­u­mented inform­a­tion about mech­an­ism of the oper­a­tion of each busi­ness ser­vice (busi­ness pro­cesses), means the abil­ity to per­form imme­di­ate ana­lys­is the impact of each such decision on the rest of the com­panythe abil­ity to imme­di­ately make decisions about intro­du­cing neces­sary changes to the IT sys­tem, doc­u­mented inform­a­tion about the oper­a­tion mech­an­ism and archi­tec­ture of the IT sys­tem, allows for imme­di­ate imple­ment­a­tion of the specification​“to-be” of this sys­tem, and send it to sup­pli­ers as a require­ment (no need to do any pre-imple­ment­a­tion analyses),possibility of imple­ment­ing busi­ness con­tinu­ity management,possibility of imple­ment­ing a con­trolling and activ­ity-based cost man­age­ment sys­tem (ABC meth­od of cost man­age­ment). See also Tar­get oper­at­ing mod­el (TOM).

Source: Enter­prise Archi­tec­ture – goals and scope of ana­lyzes and mod­el­ing – Jarosław Żeliński IT-Consulting