Phase III activities are where the actual development of the EA occurs in the form of documentation artifacts. Phase II enables this work. The work involves analyzing and documenting the current strategy, business, information, services, and infrastructure of the enterprise. It also involves the development of artifacts that reflect changes in resources in the short-term and the development of a group of long-term future scenarios to identify possible courses of action and resource changes that would be needed in response to different internal and external influences. The activities in this phase of the EA documentation methodology conclude with the development of an EA Management Plan that summarizes the current and future views of the architecture and provides a transition and sequencing plan for short term and long term changes. \nCompare and contrast the purpose of Phase II and Phase IV activities. \nPhase II activities take place when the initial set of EA documentation is developed. This begins with the selection of an EA documentation framework that will identify the scope of the architecture, guide the techniques for the modeling of current views, develop future scenarios and associated modeling, and establish an on-line EA repository that will archive all of the EA documentation artifacts . Phase IV is an ongoing set of activities that promotes the use of EA information by all stakeholders, and establishes an annual cycle for updates. This is where the value of the EA Program is realized, as planning and decisionmaking throughout the enterprise are supported. This value is maintained through regular updates of the current and future views of the architecture. Value is also gained in the maintenance of the EA repository and the maintenance of all associated software licenses for modeling and archiving.