Architecture amp; Standards for e-Government.pptVIP

  1. 1、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。。
  2. 2、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  3. 3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
  4. 4、该文档为VIP文档,如果想要下载,成为VIP会员后,下载免费。
  5. 5、成为VIP后,下载本文档将扣除1次下载权益。下载后,不支持退款、换文档。如有疑问请联系我们
  6. 6、成为VIP后,您将拥有八大权益,权益包括:VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
  7. 7、VIP文档为合作方或网友上传,每下载1次, 网站将根据用户上传文档的质量评分、类型等,对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档
查看更多
Architectureamp;amp;Standardsfore-Government.ppt

Architecture Standards for e-Government J Satyanarayana CEO, NISG Contents Architecture for e-Government Open Standards What are open Standards? Why Open Standards? Role of Open Standards in National Action Plan Open Source Software What is OSS? Open Standards Open Source Interoperability Building Standards for eGov Why Architect ? Scope of Architecture Architecture is not about Technology alone We need architectures in other areas too Process Architecture People Architecture Resource Architecture In this session we deal mainly with Technology Architecture Levels of Architecture Architecture can be at different levels Project Level Program Level Enterprise Level State level National Level We need increasing care detail in architecting as we go up the level. How does Architecture help? Helps align different components of eGov Technology Architecture to meet business needs Process Architecture to exploit technology People Architecture to use technology new processes Resource Architecture to use technology process in providing cost-effective services Promotes interoperability Ensures Scalability Enables planning the degrees of security and reliability Insulates against disruptive changes in technology, process and people Enterprise Architecture bridges Strategy Implementation Value of EA Provides business with a systematic approach to describing their business: common language (e.g., “client”, “service”, “goal”) to describe the business identify gaps in service delivery Highlights the interdependencies in service delivery across organisation boundaries: across ministries within ministries across traditional service delivery boundaries Identifies gaps in business requirements early in design cycle Lays foundation for re-use of data, applications and technology Introduces discipline in developing, documenting and disseminating standards (data, applications, technology, security) Facilitates cross-project communications US Federal Enterprise Archite

文档评论(0)

jykt + 关注
实名认证
文档贡献者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档