NATIONAL ICT COMPETENCY STANDARD FOR ENTERPRISE ARCHITECT

DEFINITION OF TERMS Enterprise An aggregation of all establishments owned by a parent company. An enterprise can consist of a single, independent establishment or it can include subsidiaries or other branch establishments under the same ownership and control. Architect A person who designs and guides a plan or an undertaking. The deviser, maker, or creator of anything. Enterprise Architect An individual responsible for the alignment of IT and Business realm of an enterprise. He/She maintains and governs the enterprises strategy, processes, information, and information technology assets. Enterprise Architecture An enterprise architecture (EA) is a conceptual tool that assists organizations with the analyzing of their own structure and the way they work. It provides a map of the enterprise and is a route planner for business and technology change. Business/IT Alignment is a desired state in which a business organization is able to use information technology (IT) effectively to achieve business objectives - typically improved financial performance or marketplace competitiveness. Standard Conventionally, a standard is defined as an accepted or approved example or technique against of which other things are judged or measured, or which set out a set of criteria that serves as a guideline for how something should be done; accepted level and scope of attainment of proficiency; a reference point against which other things are judged or measured. In the handbook, the term is used to refer to concise statements that describe the key area competency. Competency Knowledge, skill, ability or characteristic associated with high performance on a job. Some definitions of competency include motives, beliefs, and values. Competencies can also help distinguish high performance from average and low performance; a desirable quality or behavior; a performance indicator.

NICS-EA (02-09-10)

Page 1 of 4

NATIONAL ICT COMPETENCY STANDARD FOR ENTERPRISE ARCHITECT The National Competency Standard for Enterprise Architect (NICS-EA) defines the fundamental set of knowledge and skills that are required of Enterprise Architects in governing the enterprises strategy, processes, information and information technology assets. SKILL SET DIVISION (A)
A1. Business

CONTENT SCOPE (B)

B1. Environmental

Scanning
B2. Business Process

Management
B3. Business

Requirement Analysis

PERFORMANCE INDICATOR Knowledge in the following Ability to do the following (D) (E) C1. Identify requirements D1. Total Quality Management E1. Scan environment and align through benchmarking business processes with D2. Business Roles mission and vision C2. Explain business D3. Different Business Entities and objectives and principles Relationships E2. Contribute to the creation of the business strategic road C3. Construct business D4. Business Workflow and maps for the whole requirements based on Lifecycle enterprise various interests and D5. Change Management stakeholders D6. Knowledge Management E3. Capture organizational and perspectives business requirements of D7. Risk Management architecture. D8. Audit Principles and Practices D9. Business Strategic Planning E4. Translate business strategy into technical vision and D10. Performance Management strategy D11. Capability Maturity Models D12. SWOT Analysis E5. Define steps to institute changes D13. Business Modeling D14. Business Process Notation E6. Manage business continuity Standards and disaster recovery C4. Intepret business and E7. Create business models technical strategy to that support decisioncome up with the right making enterprise architectural E8. Get updates with the latest approach business models for a more efficient business analysis C5. Manage human resource E9. Readjust current system design based on changes on business processes E10. Design systems that is flexible to changes E11. Analyze customer and market trends STANDARD (C)
Page 2 of 4

NICS-EA (02-09-10)

Analyze business operations E13. Analyze business information and structure E14. Capture customer, organizational, and business requirements of architecture E15. Prepare architectural documents and presentations E16. Analyze competitors E17. Comply with regulatory standards
E12. A2. Technical B4. Technical Domain C6. Exhibit expert

and Pertinent Technologies B5. Technical Issues B6. Modeling Techniques and Methods

knowledge of underlying technology solution, its functions, components, strengths, and weaknesses

D15. D16. D17. D18. D19. D20.

Information Systems Basics of Programming Information Security Knowledge Management Case Tools Strategic Planning

C7. Develop modeling

techniques suitable to the organization

A3. Professional

B7. Organizational

C8. Collaborate with the key

Politics

players in the organization

D21. Organizational Structure D22. Stakeholders Business and

Personal Preferences
D23. Cultural Analysis

Gain enough/adequate knowledge of technology trends within the industry E19. Examine technologies and vendor platforms and determine strengths and weaknesses E20. Analyze technology trends E21. Identify optimized solutions to technical issues based on analysis from gathered data E22. Keep the confidentiality of the system design and sensitive materials within the required specification E23. Create prototypes, experiment, and simulate E24. Listen, network, and influence E25. Keep the vision alive E26. Determine the preferences of those who influence the architecture
E18.
Page 3 of 4

NICS-EA (02-09-10)

B8. Leadership

C9. Motivate the whole team

in pursuing architectural goals

D24. D25. D26. D27.

Teamwork Interpersonal Skills Conflict Management Communication Skills

project Communicate effectively to the lower echelon and with the upper echelon E28. Set team context E29. Make a decision and stand by it E30. Build and motivate teams
E27.

B9. Communication

C10.

Communicate effectively

D28. Written Communication D29. Oral Communication

Predict others' responses and respond appropriately to the situation E32. Communicate complex technical information to all stakeholders of the project E33. Share information honestly and tactfully E34. Communicate accurately, clearly, and timely, and verbally. E35. Write clear and accurate reports, letters and documents E36. Effectively write architectural documents and presentations E37. Prepare enterprise-wide communication plan for the development and implementation of the architecture
E31.

NICS-EA (02-09-10)

Page 4 of 4