Assessment Q and A

Q1 Describe the difference between an XML Sitemap and a HTML Sitemap. List the benefits and disadvantages of using each?

XML Sitemap: Helps search engines navigate the site and is usually stored in robots.txt. It offers a structured format for indexing website content.

Benefits:

  • Platform and programming language independent.
  • Supports Unicode for multilingual data.
  • Enables seamless data sharing across systems.

Disadvantages:

  • Verbose and redundant syntax compared to JSON.
  • High storage and transmission cost for large data.
  • No native array support.

HTML Sitemap: Helps users find pages through organized links and folders.

Benefits:

  • Simple to learn and use.
  • Readable code structure with few tags.
  • No need for special software or plug-ins.

Disadvantages:

  • Static by nature; requires manual updates.
  • Lacks dynamic functionality.
Q2

Evaluate three IDEs and discuss their pros, cons, and suitability for entry-level developers?

Visual Studio Code (VS Code): Lightweight and customizable.

Pros:

  • Cross-platform and fast.
  • Highly customizable interface and settings.

Cons:

  • Requires manual installation of extensions.
  • Not a full IDE—requires manual setup of debuggers and compilers.

PyCharm: Python-specific IDE with rich features.

Pros:

  • Advanced code completion and debugging tools.
  • Good for experienced developers transitioning to Python.

Cons:

  • Heavy resource usage.
  • Overwhelming for beginners.

IntelliJ IDEA: Java development environment.

Pros:

  • Free Community Edition.
  • Rich in features like JavaFX and Android support.

Cons:

  • High RAM usage.
  • Steep learning curve.

Recommendation: VS Code is best suited for beginners due to its simplicity and speed.

Q3

History of Web Browser Development and Developer Issues with Standards?

The first browsers like Mosaic and Netscape lacked standardization. Microsoft’s Internet Explorer intensified this with unique features, causing rendering inconsistencies across browsers. Developers had to write custom code for compatibility. W3C later established standards like HTML5 and CSS3, which browsers like Chrome and Firefox adopted. Ongoing issues include cross-browser compatibility, outdated browsers, and responsive design challenges.

Q4

Website Testing Methodologies (Browser Compatibility, Functionality)?

Website testing identifies bugs and checks whether applications meet requirements. Common methodologies include:

  • Browser Compatibility: Tests on various OS/browser combinations (e.g., Firefox on Win7, Safari on Mac).
  • Functionality: Ensures site meets business specs.
  • GUI Testing: Verifies interface behavior and visuals.
  • Security Testing: Validates session expiry and access control.
  • Database Testing: Ensures data integrity and transactions.
Q5

Accessibility Requirements for NT Government Websites?

The NT Government follows WCAG 2.0 Level AA standards to ensure accessibility. Key aspects include:

  • Cross-browser compatibility.
  • Support for assistive technologies (e.g., screen readers).
  • Optimized performance for low-bandwidth regions.

This ensures inclusivity and usability for all users, including those with disabilities.

Q6

How do you think it’s best to organise all the assets used for a specific webpage? Think locally on your computer AND within the root folder of the website?

I think the best way to organize all the assets used for a specfic webpage Website Root Folder - I will need to organize as ICTWEB305 unit at CDU. Website root name: and other sub folder inside the main website folder:

Example structure:

  • my-website/
  • index.html, about.html, contact.html
  • assets/ for images, logos, banners
  • css/ for stylesheets (e.g., style.css, theme.css)

This promotes clear organization and easier maintenance.