Web System Reviewer
Web System Reviewer
UNIT I
Introduction to Web Systems
Web architecture
● The web is typically structured as a client-server architecture, where
clients (web browsers) send requests to servers (web servers) for web
content.
● The server processes the request and sends the requested content back to the
client.
FRONT-END DEVELOPER
- Focuses on the visual elements of a website, including the layout, design,
and user interface.
- They primarily work with HTML, CSS, and JavaScript
BACK-END DEVELOPER
- Handles the server-side logic and functionality of a website, such as
database interactions and API integrations.
- They often work with languages like PHP, Python, Ruby, or Java.
FULL-STACK DEVELOPER
- Possesses skills in both front-end and back- end development, allowing them
to work on all aspects of a website.
UI/UX DESIGNER
- Designs the user interface and user experience of a website, focusing on
creating intuitive and visually appealing designs.
WEB DESIGNER
- Creates the overall look and feel of a website, including the layout, color
scheme, and typography
- A professional responsible for designing a website's user interface focuses on
creating a visually appealing and user-friendly experience that effectively
communicates the website's mission. Poor design leads 38% of visitors to
stop engaging, while 48% consider design the most crucial factor in
determining a business’s credibility. Additionally, 98% of users who have a
bad experience will turn to a competitor.
PROJECT PLANNING:
● Define project goals and objectives.
● Identify target audience and their needs.
● Determine project scope and timeline.
● Assign roles and responsibilities to team members.
● Create a project plan with milestones and deadlines.
USER EXPERIENCE
● Consider usability factors such as navigation, accessibility, and load times.
● Conduct user testing to gather feedback and make improvements.
● Ensure that the website is intuitive and easy to use for the target audience
• GET
Purpose: Send data to the server to be processed
Example: Submitting a form with user input
• POST
Purpose: Send data to the server to be processed
Example: Submitting a form with user input
• PUT
Purpose: Update existing data on the server
Example: Modifying user profile information
• DELETE
Purpose: Remove data from the server
Example: Deleting a user account
STATUS CODES
HTTP RESPONSES INCLUDE STATUS CODES THAT INDICATE THE OUTCOME OF THE
REQUEST.
● 200 OK
The request was successful, and the server has returned the requested data
Example Use: When a user accesses a web page, and the page loads
successfully
● 404 NOT FOUND
The requested resource was not found on the server
Example Use: When a user tries to access a URL that doesn't correspond to an
existing web page or resource
● 400 BAD REQUEST: The server cannot process the request due to client error
(e.g., malformed syntax).
● Example: A user submits a form without filling out the required fields,
triggering a "400 Bad Request" error.
● 401 UNAUTHORIZED: Authentication is required but has not been provided or
failed. Example: Trying to access a website’s dashboard without logging in
causes a "401 Unauthorized" error.
● 403 FORBIDDEN: The server understands the request but refuses to authorize
it. Example: Attempting to view restricted content without proper permissions
results in a "403 Forbidden" error.
● 500 INTERNAL SERVER ERROR: The server encountered an unexpected
condition that prevented it from fulfilling the request.
● Example: A website crashes due to server misconfiguration, causing a "500
Internal Server Error."
● 503 SERVICE UNAVAILABLE: The server is temporarily unable to handle the
request, often due to maintenance or overload.
Example: A website undergoing server maintenance returns a "503
Service Unavailable" error.
● 302 FOUND: The requested resource has been temporarily moved to a
different URL. Example: A webpage temporarily redirects users to a new page,
showing a "302 Found" status.
● 301 MOVED PERMANENTLY: The requested resource has been permanently
moved to a new URL.
Example: A website changes its domain name, and users are redirected to the
new URL with a "301 Moved Permanently" status.
● 204 NO CONTENT: The server successfully processed the request but
returns no content.
Example: A user submits a form that doesn’t require a new webpage, leading
to a "204 No Content" response.