Web development: Difference between revisions

Revision as of 15:09, 14 December 2023

Revision as of 11:06, 4 January 2024

Line 19:

The primary goal in the development of the Web was to fulfill the automated information-sharing needs of academics affiliated with institutions and various global organizations. Consequently, [[HTML]] was developed in 1993.<ref>{{Cite web |title=WebD2: A Brief History of HTML |url=https://www.washington.edu/accesscomputing/webd2/student/unit1/module3/html_history.html#:~:text=The%20first%20version%20of%20HTML,official%20standard%20in%20December%201999. |access-date=2023-12-10 |website=www.washington.edu}}</ref>

Web 1.0 is described as the first paradigm wherein users could only view material and provide a small amount of information.<ref name=":02">{{Cite journal |lastlast1=Soni |firstfirst1=Anuj |last2=Gupta |first2=Sachin |last3=Talwandi |first3=Navjot Singh |date=September 2023 |title=Evolution Of Web Technologies in Recent Years |url=https://www.jetir.org/papers/JETIR2309347.pdf |journal=Journal of emergingEmerging technologiesTechnologies and innovativeInnovative researchResearch |volume=10 |issue=9 |issn=2349-5162}}</ref> Core protocols of web 1.0 were [[HTTP]], HTML and [[Uniform Resource Identifier|URI]].<ref name=":1">{{Cite webbook |title=Some Trends in Web Application Development {{!}} IEEE Conference Publication {{!}} IEEE Xplore |url=https://ieeexplore.ieee.org/document/4221621/ |access-date=2023-11-30 |website=ieeexplore.ieee.org |doi=10.1109/fose.2007.26 |date=2007 |last1=Jazayeri |first1=Mehdi |pages=199–213 |isbn=978-0-7695-2829-8 |s2cid=7279594 }}</ref>

=== Web 2.0 ===

Line 33:

Web 3.0 aims to turn the web into a sizable, organized database, providing more functionality than traditional search engines. Users can customize navigation based on their preferences, and the core ideas involve identifying data sources, connecting them for efficiency, and creating user profiles.<ref name=":02" />

This version is sometimes also known as [[Semantic Web]].<ref>{{Citation |lastlast1=Du |firstfirst1=Xiaofeng |title=Semantic Service Description Framework for Address |date=2009 |url=http://link.springer.com/10.1007/978-0-387-78578-3_35 |work=Information Systems Development |pages=1033–1045 |editor-last=Barry |editor-first=Chris |access-date=2023-11-30 |place=Boston, MA |publisher=Springer US |language=en |doi=10.1007/978-0-387-78578-3_35 |isbn=978-0-387-78577-6 |last2=Song |first2=William |last3=Munro |first3=Malcolm |editor2-last=Lang |editor2-first=Michael |editor3-last=Wojtkowski |editor3-first=Wita |editor4-last=Conboy |editor4-first=Kieran}}</ref>

Line 42:

* Introduction of [[CSS]] (late 1990s)<ref>{{Cite web |date=2016-12-17 |title=20 Years of CSS |url=https://www.w3.org/Style/CSS20/ |access-date=2023-12-10 |website=W3C}}</ref>

* [[JavaScript]] and Dynamic HTML (1990s - early 2000s)<ref>{{Cite web |title=JavaScript History |url=https://www.w3schools.com/js/js_history.asp#:~:text=JavaScript%20was%20invented%20by%20Brendan,JavaScript%20for%20the%20Firefox%20browser. |access-date=2023-12-10 |website=www.w3schools.com |language=en-US}}</ref><ref>{{Cite web |title=A brief history of PHP |url=https://ifj.edu.pl/private/krawczyk/php/intro-history.html#:~:text=PHP%20was%20conceived%20sometime%20in,the%20Personal%20Home%20Page%20Tools. |access-date=2023-12-10 |website=ifj.edu.pl}}</ref>

* [[Ajax (programming)|AJAX]] (1998)<ref>{{Cite web |date=2007-06-23 |title=Wayback Machine |url=http://www.alexhopmann.com/xmlhttp.htm |access-date=2023-12-10 |archive-url=https://web.archive.org/web/20070623125327/http://www.alexhopmann.com/xmlhttp.htm |accessarchive-date=20232007-1206-1023 |website=web.archive.org}}</ref>

* Rise of [[Content management system]]s (CMS) (mid-2000s)

* [[Mobile web]] (late 2000s - 2010s)

Line 64:

=== 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=":2">{{Cite webjournal |lastlast1=Howcroft |firstfirst1=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 |lastlast1=Keil |firstfirst1=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 |url=http://dx.doi.org/10.1145/287831.287843 |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-

Line 182:

==== Front-end frameworks ====

A [[Web framework|framework]] is a high-level solution for the reuse of software pieces, a step forward in simple library-based reuse that allows for sharing common functions and generic logic of a ___domain application.<ref name=":3">{{Cite journal |lastlast1=Salas-Zárate |firstfirst1=María del Pilar |last2=Alor-Hernández |first2=Giner |last3=Valencia-García |first3=Rafael |last4=Rodríguez-Mazahua |first4=Lisbeth |last5=Rodríguez-González |first5=Alejandro |last6=López Cuadrado |first6=José Luis |date=May 2015 |title=Analyzing best practices on Web development frameworks: The lift approach |url=https://linkinghub.elsevier.com/retrieve/pii/S0167642314005735 |journal=Science of Computer Programming |language=en |volume=102 |pages=1–19 |doi=10.1016/j.scico.2014.12.004|doi-access=free }}</ref>

Frameworks and [[Library (computing)|libraries]] are essential tools that expedite the development process. These tools enhance developer productivity and contribute to the maintainability of large-scale applications. Some popular front-end frameworks are: