|
|||||||||||||
Home | Services | Working with ACF | Policy/Planning | About ACF | ACF News | Search | ||||||||||||
You are here: NHSITRC Home » Guides » Prog Plan Guide |
NHSITRC Site Search |
Technical Evolution Guide
|
|||||||||
|
IntroductionThis guide defines the key activities, artifacts, and roles that are necessary to create and maintain an IT Evolution Plan (IEP) for the HS Agency. The HS Agency's IT Evolution Plan guides the migration to the Agency's Technical Architecture (ATA), aligning individual IT projects with the HS IT Strategic Plan. It divides the IT evolution into a series of IT Plateaus. Each Plateau contains a collection of projects. Projects may implement new initiatives for the HS Agency, provide application upgrades for existing HS programs, or update the IT infrastructure enabling the evolution of the HS IT. The activities in this guide rely on two major work products: the HS IT Strategic Plan and the A-TARS as defined in the Strategic IT Planning and Management and the Develop and Maintain the Technical Architecture IT Planning and Management Guides. Once the HS IT organization has completed its Strategic Plan, the organization will develop the plan to evolve to the Technical Architecture. The initial IT Evolution Plan is developed in parallel with the initial Technical Architecture. See the Organization of the IT Planning and Management Guides for the relationship of the processes described in this guide with those of the other guides. To customize guidance, check information contained in the Application of the IT Planning and Management Guides. ProcessesThis guide defines the key activities, artifacts, and roles for the HS Agency technology planning and management processes. Two top-level processes contain sets of activities as shown in the Figure and described below. The key activities are:
PDF Available
Return to top of page |
||||||||
Questions? Comments? Contact
statesystems@acf.hhs.gov.NO_SPAM
General and legal information: About This Site Site Map Note: To obtain valid email addresses, remove the .NO_SPAM text. |