Editing Web development (section)

=== Analysis ===
Debra Howcraft and John Carroll proposed a methodology in which web development process can be divided into sequential steps. They mentioned different aspects of analysis.<ref name="Howcroft-2000">{{Cite journal |last1=Howcroft |first1=Debra |last2=Carroll |first2=John |date=2000 |title=A proposed methodology for web development. |journal=Ecis 2000 Proceedings |url=https://aisel.aisnet.org/ecis2000/73/}}</ref>

Phase one involves crafting a web strategy and analyzing how a website can effectively achieve its goals. Keil et al.'s research<ref>{{Cite journal |last1=Keil |first1=Mark |last2=Cule |first2=Paul E. |last3=Lyytinen |first3=Kalle |last4=Schmidt |first4=Roy C. |date=November 1998 |title=A framework for identifying software project risks |journal=Communications of the ACM |volume=41 |issue=11 |pages=76–83 |doi=10.1145/287831.287843 |issn=0001-0782|doi-access=free }}</ref> identifies the primary reasons for software project failures as a lack of top management commitment and misunderstandings of system requirements. To mitigate these risks, Phase One establishes strategic goals and objectives, designing a system to fulfill them. The decision to establish a web presence should ideally align with the organization's corporate information strategy.

The analysis phase can be divided into 3 steps:
* Development of a web strategy
* Defining objectives
* Objective analysis

During this phase, the previously outlined objectives and available resources undergo analysis to determine their feasibility. This analysis is divided into six tasks, as follows:

* '''Technology analysis:''' Identification of all necessary technological components and tools for constructing, hosting, and supporting the site.
* '''Information analysis:''' Identification of user-required information, whether static (web page) or dynamic (pulled "live" from a database server).
* '''Skills analysis:''' Identification of the diverse skill sets necessary to complete the project.
* '''User analysis:''' Identification of all intended users of the site, a more intricate process due to the varied range of users and technologies they may use.
* '''Cost analysis:''' Estimation of the development cost for the site or an evaluation of what is achievable within a predefined budget.
* '''Risk analysis:''' Examination of any major risks associated with site development.

Following this analysis, a more refined set of objectives is documented. Objectives that cannot be presently fulfilled are recorded in a Wish List, constituting part of the Objectives Document. This documentation becomes integral to the iterative process during the subsequent cycle of the methodology.<ref name="Howcroft-2000" />