“Enterprise architecture (EA) is the practice of analyzing, designing, planning and implementing enterprise analysis to successfully execute on business strategies. EA helps businesses structure IT projects and policies to achieve desired business results and to stay on top of industry trends and disruptions using architecture principles and practices, a process also known as enterprise architectural planning (EAP).
EA began in the 1960s, born from “various architectural manuscripts on Business Systems Planning (BSP) by Professor Dewey Walker,” according to the Enterprise Architecture Book of Knowledge (EABOK). John Zachmann, one of Walker’s students, helped formulate those documents into the more structured format of EA. Both men also worked for IBM during this time, and that’s when Zachman published the framework in the IBM Systems Journal in 1987.
The EA framework came as a response to the increase of business technology, especially in the 1980s when computer systems were just taking hold in the workplace. Companies soon realized they would need a plan and long-term strategy to support the rapid growth of technology and that remains true today.
Modern EA strategies now extend this philosophy to the entire business, not just IT, to ensure the business is aligned with digital transformation strategies and technological growth. EA is especially useful for large businesses going through digital transformation, because it focuses on bringing legacy processes and applications together to form a more seamless environment.”
Our take: Building enterprise networks requires strategy, patience and observation of trends – how are you growing, where are your customers going, and how are your customer communicating with you. All these can be used as building blocks when planning your next network build.