The document summarizes an enterprise architecture design project for Council of 100. The group selected the TOGAF framework. It describes the baseline architecture including the business, application, data, and technology architectures. It then describes the target architecture with improvements like a multi-tenancy portal, centralized database, and hybrid cloud. It includes sequencing and implementation plans. Diagrams depict the baseline and target organization structures and target data/technology architectures.

1. Council of 100
ISIT903 - ENTERPRISE ARCHITECTURE DESIGN
MAJOR ASSIGNMENT - GROUP 4
Anggun Darumoyo - 4864876
Achmad Hambali - 4965577
Aris Suhada Mian - 4960075
Denny Setiarika Pirhadi - 4960105
Ima Apriany - 4647890

2. Selected Framework  TOGAF
1. Cloud enablement (Mohamed et al.,2012)
2. The Open Group (2013) is quite active in integrating the TOGAF standards with Cloud
standards
3. Comprehensive process (business requirement, applications, infrastructure)
4. The highest score than the others (Sessions, 2007)
• Process Completeness
• Business focus
• Vendor neutrality
• Information availability
• Time to value
5. Provides guidance for Co100 on establishing high-level and detailed definitions for both the
baseline (starting) architecture and target (desired) architecture

3. Baseline Architecture
Business
Architecture
• Attract business that will add value to the county
• Business of information (match between business needs & local resources)
• Simple organization (Board, Senior Management & operational/supporting staffs)
Application
Architecture
• We figure out that Co100 manually search information from computer within library to
government database.
• It seems the employee did not equipped with applications. We assume that they only use
word processor or spreadsheets in creating reports for business reports.
Data Architecture • Limited logical data for making documentation & reporting
• Telephone number contact roster & simple client’s information in archives as physical
data
• Manual search for data & information from the Boards & publicly available sources
• Goal driven data & information search
Technology
Architecture
• IT Infrastructure (Printer, Photocopy machines, Fax machine)
• No internet connectivity to the federal database information,
• Communication only relies on telephone technology
• A few microcomputers, each machine has two megabytes of RAM, means limited storage
space and insufficient processor.

4. Baseline Architecture (cont’d)
Figure 1 : Baseline Organization Structure

5. Target Architecture
Business
Architecture
• The evolution of the existing local enterprise into international range
• Optimized capital investments, responsive agility to the environment change
• There is need of business governance to ensure the organisation’s business continuity
• Needs steering committee to lead and ensure that the IT transformation align with EA
Application
Architecture
• Multi-tenancy portal implementation to extends a high level of reuse capabilities of
Co100
• Standardization and delegated administration across single portal infrastructure
• Compute-intensive business analytics and dynamically configurable cloud services
• Inbound and outbound contact center
Data Architecture • Designed to be accessible from inbound and outbound of the organisation
• Organisation’s data is stored in centralized Database Management System (DBMS)
• Data security through access control mechanism
Technology
Architecture
• Client side: thin pc / laptop + internet browser
• Corporate Data Center: virtualization, network protection mechanisms, middleware
• Cloud Environment: Hybrid Cloud (Private + Public), Software as a Service (SaaS)

6. Target Architecture (cont’d)
Figure 2 : Target Organization Structure

7. Target Architecture (cont’d)
Figure 3 : Target Data Architecture Diagram

8. Target Architecture (cont’d)
Figure 4 : Target Technology Architecture Diagram

9. Sequencing Plan

10. Sequencing Plan (cont’d)

11. References
• Avram, M. G. 2014. Advantages and Challenges of Adopting Cloud Computing from an Enterprise
Perspective. Procedia Technology, 12, 529-534.
• Chelliah, P. R. 2014. Elucidating the Cloud Enterprise Architecture for Smarter Enterprises. IT Professional,
16, 33-37.
• Iyer, B. & Henderson, J. C. 2010. Preparing for the Future: Understanding the Seven Capabilities Cloud
Computing. MIS Quarterly Executive, 9, 117-131.
• Li, Q., Wang, Z. Y., Li, W. H., Li, J., Wang, C. & Du, R. Y. 2013. Applications integration in a hybrid cloud
computing environment: modelling and platform. Enterprise Information Systems, 7, 237-271.
• Pearson, S. & Benameur, A. Privacy, Security and Trust Issues Arising from Cloud Computing. Cloud
Computing Technology and Science (CloudCom), 2010 IEEE Second International Conference on, Nov. 30
2010-Dec. 3 2010 2010. 693-702.
• Tritsiniotis, E. D. 2013. Get ready for the cloud: tailoring enterprise architecture for cloud ecosystems
• Zhang, Q., Cheng, L. & Boutaba, R. 2010. Cloud computing: State-of-the-art and research challenges.
Journal of Internet Services and Applications, 1, 7-18 .
Thank You

12. The Roles of each member
• Achmad Hambali – prepares the presentation slide
• Aris Suhada Mian & Ima Apriany – contribute to content
of the powerpoint
• Anggun Darumoyo & Denny S.P – presenters