Glossary for Web Engineering:
1. Web Engineering: The discipline of designing, developing, and maintaining web-based applications.
2. World Wide Web (WWW): A system of interlinked hypertext documents accessed via the internet.
3. Hypertext Markup Language (HTML): The standard markup language for creating web pages and applications.
4. Cascading Style Sheets (CSS): A stylesheet language used for describing the presentation of a document written in HTML.
5. JavaScript: A high-level programming language used for creating dynamic and interactive web content.
6. Responsive Web Design: A design approach that ensures web pages adapt to different screen sizes and devices.
7. User Interface (UI): The visual elements and layout of a web page or application that users interact with.
8. User Experience (UX): The overall experience and satisfaction users have when interacting with a web page or application.
9. Front-End Development: The development of the client-side components and interactions of a web application.
10. Back-End Development: The development of the server-side logic and database components of a web application.
11. Full-Stack Development: The development of both the front-end and back-end components of a web application.
12. Web Server: A software or hardware system that serves web pages and responds to client requests.
13. Client: A device or software that requests and displays web pages or accesses web services.
14. Server: A device or software that processes and responds to client requests on a network.
15. HTTP (Hypertext Transfer Protocol): The protocol used for transferring hypertext documents over the internet.
16. HTTPS (Hypertext Transfer Protocol Secure): The secure version of HTTP that encrypts data transmission.
17.
API (Application Programming Interface): A set of rules and protocols
that allow different software applications to communicate with each
other.
18. REST (Representational State Transfer): An
architectural style for designing networked applications using standard
HTTP protocols.
19. JSON (JavaScript Object Notation): A
lightweight data-interchange format that is easy for humans to read and
write and easy for machines to parse and generate.
20. XML
(eXtensible Markup Language): A markup language that defines rules for
encoding documents in a format that is both human-readable and
machine-readable.
21. SQL (Structured Query Language): A programming language used for managing and manipulating relational databases.
22.
NoSQL (Not Only SQL): A term used to describe non-relational databases
that provide flexible and scalable data storage options.
23. Content Management System (CMS): A software application used for creating, managing, and publishing web content.
24. Framework: A reusable set of libraries, components, and tools that provide a foundation for building web applications.
25.
Version Control System (VCS): A system that manages changes to files
and directories, enabling multiple people to collaborate on a project.
26. Git: A distributed version control system widely used for tracking changes in source code during software development.
27.
Agile Development: An iterative and incremental approach to software
development that emphasizes flexibility and collaboration.
28.
Waterfall Model: A sequential software development model in which
progress flows downward like a waterfall through distinct phases.
29. Scrum: An agile project management framework that emphasizes collaboration, iterative progress, and flexibility.
30. Kanban: An agile project management method that visualizes work on a kanban board and focuses on continuous delivery.
31.
DevOps (Development and Operations): A software development approach
that combines development and operations teams to improve collaboration
and software delivery.
32. Continuous Integration (CI): The
practice of frequently merging code changes into a central repository,
followed by automated testing and building.
33. Continuous
Deployment (CD): The practice of automatically deploying software
changes to production environments after passing automated tests.
34.
Test-Driven Development (TDD): A development approach where tests are
written before writing the actual code, driving the design and
development process.
35. Cross-Platform Development: The development of software that can run on multiple platforms or operating systems.
36.
Progressive Web App (PWA): A web application that provides an app-like
experience with features such as offline functionality and push
notifications.
37. Single-Page Application (SPA): A web
application that loads a single HTML page and dynamically updates the
content without reloading the entire page.
38. Microservices: An
architectural style that structures an application as a collection of
loosely coupled services that can be developed, deployed, and scaled
independently.
39. Web Components: A set of web platform APIs
that allow for the creation of reusable custom elements with
encapsulated functionality.
40. Web Accessibility: The practice of ensuring that web content is accessible and usable by people with disabilities.
41. Search Engine Optimization (SEO): The process of improving the visibility and ranking of a website in search engine results.
42. Web Analytics: The collection, measurement, and analysis of web data to understand and optimize web usage and performance.
43. Wireframe: A visual representation of the layout and structure of a web page or application.
44. Prototype: A preliminary model or version of a web page or application used for testing and evaluation.
45. User Persona: A fictional character that represents a target user group and helps in understanding user needs and behaviors.
46. Information Architecture: The process of organizing and structuring content to support usability and findability.
47.
Usability Testing: The evaluation of a web page or application by real
users to identify usability issues and gather feedback.
48. A/B Testing: A technique for comparing two versions of a web page or application to determine which one performs better.
49. Front-End Framework: A collection of pre-written, reusable code that helps in developing the front-end of a web application.
50. Back-End Framework: A collection of pre-written, reusable code that helps in developing the back-end of a web application.
51. Content Delivery Network (CDN): A network of geographically distributed servers that cache and deliver web content to users.
52.
Scalability: The ability of a web application to handle increasing
amounts of traffic and workload without performance degradation.
53. Performance Optimization: The process of improving the speed and efficiency of a web application to enhance user experience.
54. Security: The protection of web applications and data from unauthorized access, attacks, and vulnerabilities.
55. Authentication: The process of verifying the identity of users accessing a web application.
56. Authorization: The process of granting or denying access to specific resources or functionalities based on user permissions.
57.
Cross-Site Scripting (XSS): A security vulnerability where attackers
inject malicious scripts into web pages viewed by other users.
58.
Cross-Site Request Forgery (CSRF): A security vulnerability where
attackers trick users into performing unintended actions on a web
application.
59. SQL Injection: A security vulnerability where
attackers manipulate SQL queries to gain unauthorized access to a web
application's database.
60. Clickjacking: A technique where attackers deceive users into clicking on hidden or disguised elements on a web page.
61.
Secure Sockets Layer (SSL): A cryptographic protocol that provides
secure communication over the internet by encrypting data transmission.
62.
Transport Layer Security (TLS): The successor to SSL, a cryptographic
protocol that provides secure communication over the internet.
63.
Content Security Policy (CSP): A security mechanism that helps prevent
cross-site scripting and other code injection attacks.
64. OWASP
(Open Web Application Security Project): An organization that provides
resources and guidance on web application security.
65. Web Application Firewall (WAF): A
security device or software that filters and monitors HTTP traffic to protect web applications from attacks.
66.
Load Balancing: The distribution of incoming network traffic across
multiple servers to ensure optimal resource utilization and performance.
67.
High Availability: The design and implementation of systems that
minimize downtime and ensure uninterrupted access to web applications.
68. Fault Tolerance: The ability of a system to continue functioning even in the presence of hardware or software failures.
69. Scalable Vector Graphics (SVG): An XML-based vector image format used for creating high-quality graphics on the web.
70. Canvas: A HTML element that provides a drawing space for dynamic rendering of graphics and animations.
71.
WebSocket: A communication protocol that provides full-duplex
communication channels over a single TCP connection, enabling real-time
web applications.
72. WebRTC (Web Real-Time Communication): A set
of APIs and protocols that enable real-time communication, such as
audio and video streaming, directly in web browsers.
73. Local Storage: A web storage mechanism that allows web applications to store data locally on a user's device.
74. Session Storage: A web storage mechanism similar to local storage but scoped to a specific browsing session.
75.
IndexedDB: A database system built into web browsers that allows web
applications to store and retrieve large amounts of structured data.
76.
Web Workers: A JavaScript API that enables running scripts in the
background to perform tasks without blocking the main web page's
execution.
77. Service Worker: A JavaScript API that enables offline caching and background processing for web applications.
78.
Progressive Enhancement: A web development strategy that focuses on
building a basic functional experience and progressively enhancing it
with advanced features.
79. Graceful Degradation: A web
development strategy that ensures a web application remains functional
even on older or less-capable devices and browsers.
80. Mobile
First: A design approach that prioritizes the development of web
applications for mobile devices before considering desktop versions.
81.
Accessibility API: A set of programming interfaces that allows
assistive technologies to interact with web content for users with
disabilities.
82. Geolocation API: A JavaScript API that enables web applications to access the user's geographical location information.
83. File API: A JavaScript API that provides access to files and allows for reading, writing, and manipulating file data.
84.
Web Storage: A mechanism that allows web applications to store data
locally on a user's device, including local storage and session storage.
85.
Geospatial Data: Data that represents objects or locations on the
Earth's surface, such as latitude and longitude coordinates.
86. Geocoding: The process of converting an address or place name into geographic coordinates.
87. Reverse Geocoding: The process of converting geographic coordinates into a corresponding address or place name.
88. Web Scraping: The automated extraction of data from websites, typically using web crawling techniques.
89.
Single Sign-On (SSO): A mechanism that allows users to authenticate
once and access multiple web applications without re-authentication.
90. Content Delivery Network (CDN): A network of geographically distributed servers that cache and deliver web content to users.
91. Web Hosting: The service of providing storage space and access for websites on servers connected to the internet.
92. Domain Name System (DNS): The system that translates domain names (e.g., www.example.com) into IP addresses.
93.
Web Caching: The process of storing and serving frequently accessed web
content to reduce bandwidth usage and improve performance.
94. Web Crawling: The automated process of systematically browsing web pages to extract information for indexing or analysis.
95. Web Scraping: The automated extraction of data from websites, typically using web crawling techniques.
96. Web Analytics: The collection, measurement, and analysis of web data to understand and optimize web usage and performance.
97.
Heatmap: A graphical representation of data where values are
represented by colors, often used to visualize user interaction on web
pages.
98. Funnel Analysis: The analysis of the steps a user takes to complete a specific goal or conversion on a website.
99. Conversion Rate Optimization (CRO): The process of increasing the percentage of website visitors who take a desired action.
100. Key Performance Indicators (KPIs): Metrics used to evaluate the performance and success of a website or web application.
101. Wireframe: A visual representation of the layout and structure of a web page or application.
102. Mockup: A visual representation of a web page or application that shows its design, layout, and functionality.
103. Prototype: A preliminary model or version of a web page or application used for testing and evaluation.
104. User Interface (UI) Design: The design of the visual elements and interactions of a web page or application.
105.
User Experience (UX) Design: The design of the overall experience and
satisfaction users have when interacting with a web page or application.
106. Information Architecture: The process of organizing and structuring content to support usability and findability.
107.
Interaction Design: The design of the way users interact with a web
page or application, including interface elements and user flows.
108.
Usability Testing: The evaluation of a web page or application by real
users to identify usability issues and gather feedback.
109. Responsive Web Design: A design approach that ensures web pages adapt to different screen sizes and devices.
110.
Mobile-First Design: A design approach that prioritizes the development
of web applications for mobile devices before considering desktop
versions.
111. Cross-Browser Compatibility: The design and
development of web applications that work consistently across different
web browsers.
112. Accessibility: The practice of ensuring that web content is accessible and usable by people with disabilities.
113.
Search Engine Optimization (SEO): The process of improving the
visibility and ranking of a website in search engine results.
114. Call to Action (CTA): A prompt or button on a web page that encourages users to take a specific action.
115. Landing Page: A web page designed specifically for users to land on after clicking a promotional link or advertisement.
116.
Error Handling: The process of managing and displaying error messages
to users when they encounter issues on a web page or application.
117.
Performance Optimization: The process of improving the speed and
efficiency of a web application to enhance user experience.
118. Page Load Time: The time it takes for a web page to fully load and become visible to the user.
119. Browser Rendering: The process of a web browser interpreting and displaying the HTML, CSS, and JavaScript of a web page.
120.
Progressive Enhancement: A web development strategy that focuses on
building a basic functional experience and progressively enhancing it
with advanced features.
121. Graceful Degradation: A web
development strategy that ensures a web application remains functional
even on older or less-capable devices and browsers.
122.
Cross-Site Scripting (XSS): A security vulnerability where attackers
inject malicious scripts into web pages viewed by other users.
123.
Cross-Site Request Forgery (CSRF): A security vulnerability where
attackers trick users into performing unintended actions on a web
application.
124. SQL Injection: A security vulnerability where
attackers manipulate SQL queries to gain unauthorized access to a web
application's database.
125. Clickjacking: A technique where attackers deceive users into clicking on hidden or disguised elements on a web page.
126.
Secure Sockets Layer (SSL): A cryptographic protocol that provides
secure communication over the internet by encrypting data transmission.
127.
Transport Layer Security (TLS): The successor to SSL, a cryptographic
protocol that provides secure communication over the internet.
128. Content Security Policy (CSP): A security mechanism that helps prevent cross
-site scripting and other code injection attacks.
129.
OWASP (Open Web Application Security Project): An organization that
provides resources and guidance on web application security.
130.
Web Application Firewall (WAF): A security device or software that
filters and monitors HTTP traffic to protect web applications from
attacks.
131. Load Balancing: The distribution of incoming
network traffic across multiple servers to ensure optimal resource
utilization and performance.
132. High Availability: The design
and implementation of systems that minimize downtime and ensure
uninterrupted access to web applications.
133. Fault Tolerance: The ability of a system to continue functioning even in the presence of hardware or software failures.
134.
Scalability: The ability of a web application to handle increasing
amounts of traffic and workload without performance degradation.
135. Scalable Vector Graphics (SVG): An XML-based vector image format used for creating high-quality graphics on the web.
136. Canvas: A HTML element that provides a drawing space for dynamic rendering of graphics and animations.
137.
WebSockets: A communication protocol that provides full-duplex
communication channels over a single TCP connection, enabling real-time
web applications.
138. WebRTC (Web Real-Time Communication): A
set of APIs and protocols that enable real-time communication, such as
audio and video streaming, directly in web browsers.
139. Local Storage: A web storage mechanism that allows web applications to store data locally on a user's device.
140. Session Storage: A web storage mechanism similar to local storage but scoped to a specific browsing session.
141.
IndexedDB: A database system built into web browsers that allows web
applications to store and retrieve large amounts of structured data.
142.
Web Workers: A JavaScript API that enables running scripts in the
background to perform tasks without blocking the main web page's
execution.
143. Service Worker: A JavaScript API that enables offline caching and background processing for web applications.
144.
Progressive Web App (PWA): A web application that provides an app-like
experience with features such as offline functionality and push
notifications.
145. Single-Page Application (SPA): A web
application that loads a single HTML page and dynamically updates the
content without reloading the entire page.
146. Microservices: An
architectural style that structures an application as a collection of
loosely coupled services that can be developed, deployed, and scaled
independently.
147. Web Components: A set of web platform APIs
that allow for the creation of reusable custom elements with
encapsulated functionality.
148. Web Scraping: The automated extraction of data from websites, typically using web crawling techniques.
149.
Single Sign-On (SSO): A mechanism that allows users to authenticate
once and access multiple web applications without re-authentication.
150.
Content Delivery Network (CDN): A network of geographically distributed
servers that cache and deliver web content to users.
151. Web Hosting: The service of providing storage space and access for websites on servers connected to the internet.
152. Domain Name System (DNS): The system that translates domain names (e.g., www.example.com) into IP addresses.
153.
Web Caching: The process of storing and serving frequently accessed web
content to reduce bandwidth usage and improve performance.
154. Web Crawling: The automated process of systematically browsing web pages to extract information for indexing or analysis.
155. Web Scraping: The automated extraction of data from websites, typically using web crawling techniques.
156. Web Analytics: The collection, measurement, and analysis of web data to understand and optimize web usage and performance.
157.
Heatmap: A graphical representation of data where values are
represented by colors, often used to visualize user interaction on web
pages.
158. Funnel Analysis: The analysis of the steps a user takes to complete a specific goal or conversion on a website.
159. Conversion Rate Optimization (CRO): The process of increasing the percentage of website visitors who take a desired action.
160. Key Performance Indicators (KPIs): Metrics used to evaluate the performance and success of a website or web application.
161. Wireframe: A visual representation of the layout and structure of a web page or application.
162. Mockup: A visual representation of a web page or application that shows its design, layout, and functionality.
163. Prototype: A preliminary model or version of a web page or application used for testing and evaluation.
164. User Interface (UI) Design: The design of the visual elements and interactions of a web page or application.
165.
User Experience (UX) Design: The design of the overall experience and
satisfaction users have when interacting with a web page or application.
166. Information Architecture: The process of organizing and structuring content to support usability and findability.
167.
Interaction Design: The design of the way users interact with a web
page or application, including interface elements and user flows.
168.
Usability Testing: The evaluation of a web page or application by real
users to identify usability issues and gather feedback.
169. Responsive Web Design: A design approach that ensures web pages adapt to different screen sizes and devices.
170.
Mobile-First Design: A design approach that prioritizes the development
of web applications for mobile devices before considering desktop
versions.
171. Cross-Browser Compatibility: The design and
development of web applications that work consistently across different
web browsers.
172. Accessibility: The practice of ensuring that web content is accessible and usable by people with disabilities.
173.
Search Engine Optimization (SEO): The process of improving the
visibility and ranking of a website in search engine results.
174. Call to Action (CTA): A prompt or button on a web page that encourages users to take a specific action.
175. Landing Page: A web page designed specifically for users to land on after clicking a promotional link or advertisement.
176.
Error Handling: The process of managing and displaying error messages
to users when they encounter issues on a web page or application.
177.
Performance Optimization: The process of improving the speed and
efficiency of a web application to enhance user experience.
178. Page Load Time: The time it takes for a web page to fully load and become visible to the user.
179. Browser Rendering: The process of a web browser interpreting and displaying the HTML, CSS, and JavaScript of a web page.
180.
Progressive Enhancement: A web development strategy that focuses on
building a basic functional experience and progressively enhancing it
with advanced features.
181. Graceful Degradation: A web
development strategy that ensures a web application remains functional
even on older or less-capable devices and browsers.
182.
Cross-Site Scripting (XSS): A security vulnerability where attackers
inject malicious scripts into web pages viewed by other users.
183.
Cross-Site Request Forgery (CSRF): A security vulnerability where
attackers trick users into performing unintended actions on a web
application.
184. SQL Injection: A security vulnerability where
attackers manipulate SQL queries to gain unauthorized access to a web
application's database.
185. Clickjacking: A technique where attackers deceive users into clicking on hidden or disguised elements on a web page.
186.
Secure Sockets Layer (SSL): A cryptographic protocol that provides
secure communication over the internet by encrypting data transmission.
187.
Transport Layer Security (TLS): The successor to SSL, a cryptographic
protocol that provides secure communication over the internet.
188.
Content Security Policy (CSP): A security mechanism that helps prevent
cross-site scripting and other code injection attacks.
189. OWASP
(Open Web Application Security Project): An organization that provides
resources and guidance on web application security.
190. Web
Application Firewall (WAF): A security device or software that filters
and monitors HTTP traffic to protect web applications from attacks.
191. Load Balancing: The distribution of
incoming network traffic across multiple servers to ensure optimal resource utilization and performance.
192.
High Availability: The design and implementation of systems that
minimize downtime and ensure uninterrupted access to web applications.
193. Fault Tolerance: The ability of a system to continue functioning even in the presence of hardware or software failures.
194.
Scalability: The ability of a web application to handle increasing
amounts of traffic and workload without performance degradation.
195. Scalable Vector Graphics (SVG): An XML-based vector image format used for creating high-quality graphics on the web.
196. Canvas: A HTML element that provides a drawing space for dynamic rendering of graphics and animations.
197.
WebSockets: A communication protocol that provides full-duplex
communication channels over a single TCP connection, enabling real-time
web applications.
198. WebRTC (Web Real-Time Communication): A
set of APIs and protocols that enable real-time communication, such as
audio and video streaming, directly in web browsers.
199. Local Storage: A web storage mechanism that allows web applications to store data locally on a user's device.
200. Session Storage: A web storage mechanism similar to local storage but scoped to a specific browsing session.