Most of the time a stakeholder request (individual or governing body) leads to the identification of a need to establish or update a standard. However, there are other ways a need is identified. For example, the Chief IT Architect may initiate an internal project (e.g., development of an information architecture for the extramural business domain) that requires the NIH-wide perspective that domain teams provide. Or, it is possible that the NIH Requests for Comments (NIHRFC) Process is not able to produce a standard, in which case the NIH Chief IT Architect may decide to establish a domain team.
After the need is identified, the NIH Chief IT Architect may determine that a domain team is the most appropriate standards development process to meet the need.
|
Domain Team And Working Group Checklist (DOC) - The purpose of this document is to outline the steps to prepare for and run domain team meetings. The document is organized into a series of checklists to facilitate preparation.
NIHRFC 0001 - Enterprise Architecture Standards Process (PDF). Documents the EA standards process. Defines the stages in the standardization process, the requirements for moving a document between stages, and the types of documents used during this process. |
Exit Criteria:
- NIH Chief IT Architect determines a domain team should be established.
- Stakeholders or Chief IT Architect determine a working group should be established.
Next Step: Establish the team.
