Enterprise architecture best practices. The following best practices are recommended for overcoming the IT fiefdom challenge and building a successful EA program. Otherwise, strategic SOA deployment across the enterprise will be impossible. • Business driven—EA methodologies and tools all start with business definitions, so ensure your EA program is completely business driven. • Business process expertise—Integrate any BPM, modeling, and continuous improvement initiatives within your company. • Experienced team—Build, motivate, and retain a respected EA team that can communicate effectively at all levels of business and IT, plus act as the scribe with EA methodologies and tools. • Speak business language—Do not use IT jargon. • Start to break down IT fiefdoms—Facilitate tough decisions on policies, specifications, and standards, including vendors, across these fiefdoms. • Understand application packages—As well as own developments, standard packages predefine many of their own IT standards. • Understand SAP’s standard software tools—Many can integrate and assist your EA initiative, especially SAP EA framework, SAP Solution Manager, SAP Solution Landscape Directory, and SAP NetWeaver Enterprise Services Repository. • Use a partner company—Consider using one of the SAP Consulting partner companies to help initiate your EA initiative if your company lacks experienced enterprise architects, provided that the partner can demonstrate a solid EA track record with previous SAP customers, such as Capgemini and Infosys. • Evaluate ISV EA software tools—Use enabling tools of the trade to make it easier to maintain your EA blueprint models, artifacts, and documentation.
Posted on: Tue, 12 Aug 2014 05:52:21 +0000
Trending Topics
Recently Viewed Topics
© 2015