ADM 2372 Lecture 11: Ch.11-Enterprise-Architectures-and-Ch.-12-Networks-Telecommunications-and-Mobile-Technology-2

• School: University of Ottawa
• Department: Administration
• Course: ADM 2372
• Professor: Mirou Jaana

Document Summary

Enterprise architecture (ea) plans for how an org. builds, uses and shares its data, processes, and it assets. If unified, provides standardization of enterprise-wide hardware and software systems. Right ea can make it cheaper, strategic (reuse it assets), and more responsive (dev. new syst. faster) Goals: improve productivity, customer satisfaction, growth, new rev. streams, optimize the supply chain. Components: data architecture, infrastructure architecture, application architecture. Enterprise architect: grounded in technology, fluent in business, patient diplomat and provides the important bridge between it and business. Data architecture: identifies where and how important data, like customer records, are maintained and secured. Three primary areas that should be focused on: backup and recovery minimize the damage of a system crash. *if org. deals w/ large volumes of critical data require daily/hourly backups to storage servers. Otherwise, weekly should be fine. (although there is still a risk)