nci enterprise architecture competency standards

8/14/2019 NCI Enterprise Architecture Competency Standards

1/4

NICS-EA (02-09-10) Page 1 of 4

NATIONAL ICT COMPETENCY STANDARD FOR ENTERPRISE ARCHITECT

DEFINITION OF TERMS

EnterpriseAn aggregation of all establishments owned by a parent company. An enterprise can consist of a single, independent establishment or it can includesubsidiaries or other branch establishments under the same ownership and control.

ArchitectA person who designs and guides a plan or an undertaking.The deviser, maker, or creator of anything.

Enterprise ArchitectAn 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 ArchitectureAn enterprise architecture (EA) is a conceptual tool that assists organizations with the analyzing of their own structure and the way they work. It provides amap of the enterprise and is a route planner for business and technology change.

Business/IT Alignmentis a desired state in which a business organization is able to use information technology (IT) effectively to achieve business objectives - typically improvedfinancial performance or marketplace competitiveness.

StandardConventionally, a standard is defined as an accepted or approved example or technique against of which other things are judged or measured, or which setout 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 pointagainst 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.

CompetencyKnowledge, 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.


2/4


3/4


E12. Analyze businessoperations

E13. Analyze businessinformation and structure

E14. Capture customer,organizational, andbusiness requirements ofarchitecture

E15. Prepare architecturaldocuments andpresentations

E16. Analyze competitorsE17. Comply with regulatory

standards

C6. Exhibit expertknowledge of underlyingtechnology solution, itsfunctions, components,strengths, andweaknesses

E18. Gain enough/adequateknowledge of technologytrends within the industry

E19. Examine technologiesand vendor platforms anddetermine strengths and

weaknessesE20. Analyze technologytrends

A2. Technical B4. Technical Domainand PertinentTechnologies

B5. Technical IssuesB6. Modeling Techniques

and Methods

C7. Develop modelingtechniques suitable tothe organization

D15. Information SystemsD16. Basics of ProgrammingD17. Information SecurityD18. Knowledge ManagementD19. Case ToolsD20. Strategic Planning

E21. Identify optimizedsolutions to technical issuesbased on analysis fromgathered data

E22. Keep the confidentialityof the system design and

sensitive materials withinthe required specificationE23. Create prototypes,

experiment, and simulate

A3. Professional B7. OrganizationalPolitics

C8. Collaborate with the keyplayers in theorganization

D21. Organizational StructureD22. Stakeholders Business and

Personal PreferencesD23. Cultural Analysis

E24. Listen, network, andinfluence

E25. Keep the vision aliveE26. Determine the

preferences of those who

influence the architecture


4/4


projectE27. Communicate

effectively to the lowerechelon and with the upperechelon

B8. Leadership C9. Motivate the whole teamin pursuing architecturalgoals

D24. TeamworkD25. Interpersonal SkillsD26. Conflict ManagementD27. Communication Skills

E28. Set team contextE29. Make a decision and

stand by itE30. Build and motivate

teams

B9. Communication C10. Communicate

effectively

D28. Written Communication

D29. Oral Communication

E31. Predict others'

responses and respondappropriately to the situationE32. Communicate complex

technical information to allstakeholders of the project

E33. Share informationhonestly and tactfully

E34. Communicateaccurately, clearly, and

timely, and verbally.E35. Write clear and accuratereports, letters anddocuments

E36. Effectively writearchitectural documents andpresentations

E37. Prepare enterprise-widecommunication plan for the

development andimplementation of thearchitecture

nci enterprise architecture competency standards

Documents