ASSESSMENT 1 Questioning

disadvantages of using each.

The differences between XML and HTML – HTML: its main purpose is to organise and present

content on the internet whilst XML was created to store and transfer data with an emphasis on

what is data. HTML tag makes use of present tags like <div>, <p>, <a>, <meta>, and etc whilst

XML uses tags which user-defined enable such as <book>, <author> and others. The syntax in

XML is strict, case-sensitive syntax that requires proper tag nesting and closing as opposed to

HTML where it is more tolerant of errors. Lastly, the XML’s focus is on data storage and

transmission and the focus of HTML is on the presentation of data. The benefits of HTML is that

it is user-friendly and easy to learn, making it accessible for beginners. It supports multimedia

integration, allowing the embedding of images, videos and audio. Also,aids in SEP optimisation

improving search engine rankings, and ensures cross-platform compatiblity working seamlessly

in various browsers and devices. Its disadvantages is that it has limited data-handling capabilities

as it is not designed for data storage or transport. It reies on predefined tags which makes it less

flexible. On the other hand, XML provides more flexibility with custom tags allowing users to

define their own structure making it ideal for data storage, transport and data-centric. A

platform-independent ensuring compatiblity across different systems and applications. XML

follows a well-formed structure that maintains data integrity and consistency. However, XML also

has disadvantages like its complex syntax that needs strict adherence to formatting rules. Thus,

it lacks presentation capabilities and is not designed for displaying data visually.

The HTML excel in web page structure and presentation whilst XML is better suited in data

storage and transport as it is customisable and structured environment.

Evaluate three IDE’s (Integrated development environments) and provide a brief summary on the

positive and negative aspects of each. Also, in your own words include how it would suit an entry level

trainee code developer.

Three examples of Integrated development environment – Notepad++, Sublime text and VS

code. The Notepad++ is an open-source free text and source code editor for Windows that is

popular due to its effectiveness and adaptability. It provides syntax highlighting and folding for

a number of programmng languages and has tabbed editing. With support for themes and plugins,

the interface is incredibly customisable and auto-completion increases effeciency by making

word, function and parameter suggestions. Due to its portability, speed, ans ease of use, the

Notepad++ is perfect for managing big files. Its functionality is further improved by its

extensibility through plugins. Notepad++ is less apropriate for more complex development

needs as it is windows-only and does not include all the sophisticated capabilities of other

editors. For writing, markup and coding Sublime text is a robust and flexible text editor. It has a

command palette for easy access to syntax and functions highlighting for different programming

languages and tabbed editing for handling numerous files. Whilst there are many customisation

options that let users customise the interface with themes and plugins, features like split editing,

multiple selections and distraction-free mode improve productivity and focus. Cross-platform

compatibility, makes it accessible on Windows and other platform. In addition, it is quite

extensible, supporting a large number of plugins, and easy to use with a rich interface. However,

its primary drawbacks are that it has a learning curve for becoming proficient with some of its

more complex features and that it necessitates a paid licence for continous use following the

evaluation time. VS code is free, an open -source code editor from Microsoft that has become a

favourite among developers for its flexibility and powerful features. It works seamlessly across

Windows, macOS and Linux making it a great choice foe developers on any platform. With an

integrated terminal, you can run Bash, Zsh, PowerShell or Command prompt right within the

editor. The extension marketplace offers thousands of plugins to enhance coding in different

langauages and tools. Built-in Git integration makes version control easy whilst IntelliSense

provides smart code suggestions based on variables, functions and modules. Debuggin is made

simple with its built-in debugger and the Live share feature allows real-time collaboration with

teammates. Whether you are a beginners or an experienced developer, VS code offers a smooth

and efficient coding experience. The Notepad++ suits beginners for its simplicity and lightweight

text editor that provides trainees a great starting experience with basic programming concepts

and want a distraction-free environment. The Sublime text is best for speed and efficient editing

and it suits beginners due to its sleek interface and features like multiple selections and split

editing making coding easier for them and the VS code suits beginners as it has the most feature

among the three. Offering built in Git integration, a vast extension marketplace and IntelliSense

for smart code completion. Its great for beginners who want to explore more advances features

like debugging and real-time collaboration.

Provide a brief history on web browser development and the issues encountered by web developers,

specifically, the adherence to web standards.

The development of web browsers has evolved significantly over time. In the early 1990’s

Gopher was one of the first systems used for retrieving information online and in 1991 Tim

Berners-Lee created WorlWideWeb at CERN, laying the foundation for modern browsing. The

mid-90s saw the beginning of the browsers wars with Netscape Navigator launching in 1994

followed by Microsoft’s Internet Explorer in 1995 sparking fierce competition. To bring order to

the rapidly growing web, Berners-Lee established the World Wide Web Consortium (W3C) in

1994 to set standards for web technologies. In 1998, the Web Standards Project (WaSP) was

formed to encourage browsers to follow these standards and improve compatibility across the

web. As time went on, browsers began to take web standards more seriously, one of the first to

do so was Internet Explorer 5 for Mac, which was released in 2000. By 2003, CSS Zen Garden had

shown how strong and adaptable CSS could be, demonstrating that clean code was not

necessary for effective design. These turning points contributed to the development of the

modern web by making surfing more streamlined, uniform and aesthetically pleasing.

Challenges faced by web developers – web developers have long struggles with browser

compatibility issues. In the early days, Netscape and Microsoft introduced their own proprietary

features making their browsers incompatible with each other. This forced developers to write

multiple version of their code just to ensure websites worked across different browsers. A major

problem was the lack of standardisation as many browsers didn’t fully comply with W3C

recommendations leading to inconsistencies in how web pages were displayed. This

fragmentation made web development frustrating and time-consuming. In response the Web

Standards Projecct (WaSP) was formed to push for better adherence to web standards,

advocating for a more unified web experience. Developers and organisations also worked to

educate otheres about the importance of standardisation helping to drive imporvements in

browser support over time.

What are website testing methodologies? Your answer MUST cover browser compatibility, and website

functionality.

The website testing is a process that ensures a site functions correctly across different browsers,

devices and user interactions. With the browser compatibility testing and functional testing

combined, the developers can ensure a website works smoothly across all platforms and

provides a seamless experience for the users. The browser compatibility process ensures that

the website works consistently across different browsers like Chrome, Firefox, Safari, Edge and

others. To do this, first you must open the site in multiple browsers to check for inconsistencies.

Also, make sure that the site adapts well to all different screen sizes as well as resolutions. The

website functionality test is a process which validates that all website features work as intended.

Things or items like forms, buttons or links are individual components that needs to be tested.

Next, verify the user interface like layout, navigation and the user interactions. In the testing,

ensure different modules are working properly like the login page, the database if it is connected

to and also if the site is selling an item check if the process is being followed especially the

checkout section. Another testing methodology is performance testing – this measures the load

time, responsiveness and speed of a site. The test involves simulating the high traffic to see how

the site performs under pressure and there are tools used to optimise performance of a page

speed testing. Lastly, usability and security testing – by assessing how simple it is for people to

navigate a website, usability testing aims to provide an enjoyable and user-friendly experience.

This procedure evaluate several features to identify the best design whilst navigation test make

sure visitors can navigate the website with ease. On the other hand, security testing looks for

and addresses flaws that hackers might exploit. An example of security testing is SSL testing, this

process guarantees safe data transmission over HTTPS. And penetration testing is to find

vulnerabilities, these two testing techniques improve the website security and user experience.

What are the endorsed requirements of accessibility for all NT Government webpages?

The Northern Territory Government (NTG) has endorsed the following accessibility requirements

for its webpages: Web Content Accessibility Guidelines version 2.0 and the National Transition

Strategy. The NTG aims to meet the WCAG 2.0 Level AA compliance. Also, NTG is implementing

the Australian Government’s Web Accessibility National Transition Strategy to achieve WCAG 2.0

compliance. Currently, not all NTG web content has been optimised for accessibility and some

content may not meet the Level AA compliance.

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.

When setting up a website keeping your files organiseed is key to making development easier.

Below is a simple way to structure a project:

• Project root folder – the main folder that holds everything realted to the website. All the

  HTML files should be kept directly here together with the main page named index.html

  for easy access

• CSS folder – stores all the CSS files, ideally using a main stylesheet like style.css to keep

  things neat

• Image folder – it is where all the photos (.jpg, .png, .gif) are kept

• Javascript folder – all Javascript files should be kept here

With the naming conventions:

• Stick to lowercase for file and folder names

• Avoid spaces and use underscores or hyphens instead

• Letter or number is utilised when naming and not a special character

The above structure keeps the project organised, making it easier to find and manage files as the

website expands.