RMIT · COSC3044 · Web Programming Bootcamp

COSC3044: ace the project, not just read the notes

Your complete guide to RMIT University's web programming bootcamp unit. See where the marks are, work real practice questions, and study with an AI tutor that knows COSC3044.

12 credit points Undergraduate Offered Sem 1 / Sem 2 School of Computing Technologies

Sia generates COSC3044 practice questions, walks through the world wide web and web protocols step by step, and quizzes you on the material the project that weights most heavily.

Spot the bug

Find what is wrong

Multiple choice · the fix is revealed after you answer

A button should reveal a hidden panel when clicked. Which approach is best practice, and why?

The fix

Separate the three concerns. HTML carries structure, CSS carries presentation, JavaScript carries behaviour. This separation is the organising principle of the whole course and it decides the answer.

Place the behaviour correctly. addEventListener attaches the interaction in the JavaScript layer, keeps the markup clean, and allows several handlers on one element — which an onclick attribute does not.
Place the presentation correctly. Toggling a class leaves the visual rule in the stylesheet, so how the panel appears stays in CSS. Setting element.style.display in script hard-codes presentation into behaviour and overrides the stylesheet in a way that is difficult to undo.
Judge the alternatives on their real limits. Option C is genuinely clever and fails on interaction semantics — focus is lost the moment the user clicks elsewhere, so the panel closes unexpectedly. Option D works, and it discards the entire point of client-side programming, which is responding without a round trip.

The trap: Option B is the most common answer from anyone who learned web programming from tutorials, and it is not broken — it is simply the version that stops scaling. Inline handlers scatter behaviour through the markup and inline styles fight the stylesheet, and both problems only surface once a page grows beyond one developer's head. The course assesses the maintainable version. classic slip!

your whole grade
Where your grade comes from Projects 90% · Coursework 10%

One project decides 40% of your grade. Continual assessment. This whole page is built around that.

Overview

What COSC3044 is, and where it sits

COSC3044 is run in what RMIT calls a bootcamp learning style — the description defines it as a focussed mode teaching approach based around workshops over a period of four to six weeks. A full course compressed into roughly a third of a semester is the defining fact about it.

The content is a technical introduction to web programming: the essential concepts of the World Wide Web, an overview of Internet technology, current web protocols, client-side programming, communication and design. It builds on Programming Bootcamp 1 and serves as a prerequisite for more specialised courses that require web programming.

Two published facts change how this course should be approached. It awards a pass or fail mark only — RMIT states this explicitly — so there is no distinction to chase, only a standard to meet. And the assessment is four programming challenges of rising weight, 10, 20, 30 and 40 percent, each building on the last through HTML, then CSS, then JavaScript.

How it differs from its first-year siblings. The pass/fail grading and the four-to-six week compression pull in opposite directions: the bar is lower than in a graded course, but you have a third of the usual time to clear it.

Always treat your own course outline and the exam timetable as authoritative.

Difficulty & time commitment

Is COSC3044 hard, and how much time does it take?

COSC3044 is manageable if you keep a weekly rhythm and treat the back half as the main event. The pattern is consistent: it starts gently and steepens, and the heaviest assessment is the part that separates grades.

Difficulty
2.9 / 5
Moderate. Gentle early, demanding back half. Hard to fail with steady work; a top grade takes consistent practice.
Coursework
100%
Coursework carries most of the grade. The heaviest single component is the project at 40%.
Weekly time
~9 hrs
Around 9 hours per week including class, across lectures, study and assessment.
Web fundamentals, HTML and CSSfast but gentle
JavaScript and the final challengecompressed

The difficulty curve and the assessment weighting point the same way: the back half is harder and worth more. Front-loading effort there is the highest-return decision in the unit.

Is this unit for you

Who tends to do well, and who tends to struggle

You will likely do well if

  • You keep up with the compressed schedule; four to six weeks leaves no room to catch up later.
  • You separate structure, presentation and behaviour from the first challenge onward.
  • You build things beyond the set tasks, since the skill is practical and grows by repetition.
  • You treat challenge 1 seriously even at 20%, because challenges 2 and 3 build directly on it.

You may struggle if

  • You expect a normal semester's pace; this course is compressed into a third of one.
  • You write inline styles and inline handlers because they work at small scale.
  • You assume pass/fail means low effort — the standard still has to be met inside a short window.
  • You skip the self-directed activities; at 10% they are cheap and they track whether you are keeping pace.
do this ↘
What top students do differently
  • Build one small page a day during the bootcamp. Web programming rewards volume of practice more than study time.
  • Learn the DOM properly rather than copying snippets; it is what the JavaScript challenges actually test.
  • Validate your HTML and check the page without CSS — if the structure is meaningless, the markup is wrong.
  • Keep every challenge's code, since each one builds on the last and rewriting from scratch wastes the compressed time you have.

Syllabus

The 11 topics, topic by topic

The exam-weight marker on each topic shows where the marks concentrate. The amber topics carry the highest exam weight.

1

T1 · The World Wide Web and Internet technology

Course description

How the web actually works beneath the browser.

2

T2 · Web protocols

Course description

HTTP and the request-response model that everything else sits on.

3

T3 · HTML and document structure

Assessment Task 2 (HTML and CSS)

Marking up content so it is meaningful, not merely visible.

High exam weightQuiz me on html →
4

T4 · CSS and layout

Assessment Task 2 (HTML and CSS)

Separating presentation from structure, and controlling layout predictably.

High exam weightQuiz me on css →
5

T5 · Responsive and accessible design

Course description (design)

Building for varied devices and users rather than for one screen.

6

T6 · JavaScript fundamentals

Assessment Task 3 (HTML, CSS and JavaScript)

Adding behaviour: variables, control flow, functions and events.

7

T7 · The document object model

Standard client-side canon

How a script reaches into and changes a rendered page.

8

T8 · Client-side problem solving

CLO2

Designing algorithmic solutions for small to medium client-side problems.

9

T9 · Communication between client and server

Course description (communication)

How a page exchanges data with a server after it has loaded.

10

T10 · Evaluating a web solution

CLO3

Judging a solution rather than only building one.

11

T11 · Professional practice and standards

CLO4

Industry-informed practice in designing and implementing web solutions.

How it's assessed

Assessment structure

ComponentWeightFormat & timing
Programming Challenge 3 (HTML, CSS and JavaScript)40%Third programming challenge, published as the Melbourne version's largest task and supporting all four course learning outcomes. End of the bootcamp. Continual assessment.
Programming Challenge 2 (HTML, CSS and JavaScript)30%Second programming challenge, supporting all four course learning outcomes. Mid bootcamp. Continual assessment.
Programming Challenge 1 (HTML and CSS)20%First programming challenge, supporting course learning outcomes 1, 2 and 3. Early bootcamp. Continual assessment.
Self-directed progress checking activities10%Self-directed progress checking activities, supporting course learning outcomes 1, 2 and 4. Throughout. Continual assessment.
Programming Challenge 3 (HTML, CSS and JavaScript)40%
Third programming challenge, published as the Melbourne version's largest task and supporting all four course learning outcomes.
Programming Challenge 2 (HTML, CSS and JavaScript)30%
Second programming challenge, supporting all four course learning outcomes.
Programming Challenge 1 (HTML and CSS)20%
First programming challenge, supporting course learning outcomes 1, 2 and 3.
Self-directed progress checking activities10%
Self-directed progress checking activities, supporting course learning outcomes 1, 2 and 4.
  • The four published Melbourne tasks sum to 100. RMIT states that this course has no hurdle requirements and that it awards a pass or fail mark only.
  • There is no examination. The most important published fact is the grading basis: pass or fail only, with no graded distinction band. The four challenges rise in weight and build on each other technically, so falling behind in the HTML and CSS challenge compounds directly into the JavaScript ones. Note that the Vietnam version of this course uses a different split (10/20/70); the weights above are the published Melbourne version.
read this! If you read nothing else

This is a coursework unit. Coursework carries 100% of the grade and the programming challenge 3 (html, css and javascript) is the single heaviest piece at 40%, so steady work across the semester decides your result more than any one sitting. Continual assessment.

Final exam timing: No examination in this course. Confirm the exact date and venue on your exam timetable.

How to actually pass it

A weekly rhythm, two checklists, and the traps to avoid

The unit rewards consistency over cramming, and practice over re-reading. Here is the loop that works, then what to have nailed before each exam.

The weekly loop

Daily during the bootcamp
Build something small. The format is too compressed for weekly rhythms.
Per challenge
Get a minimal working version first, then improve it — partial credit favours something that runs.
Throughout
Do the self-directed progress checks; they are 10% and they show whether you are on pace.
Before challenge 3
Consolidate JavaScript and the DOM; the 40% task rests on both.

Before the mid-semester checklist

  • Explain how the World Wide Web and its protocols work.
  • Structure a document correctly in HTML.
  • Control layout and presentation with CSS, separately from structure.
  • Apply problem-solving techniques to small client-side problems.

Before the final heaviest topics

  • Write JavaScript to add behaviour, using events and the DOM.
  • Create and evaluate client-side web solutions using current tools.
  • Handle communication between client and server.
  • Demonstrate industry-informed professional practice in designing and implementing web solutions.

The mistakes that cost marks

01

Inline styles and inline handlers. They work until a page grows. The course assesses the separated version because that is the one that survives a second developer.

02

Presentation set from JavaScript. Toggling a class keeps the visual rule in CSS. Setting style properties in script overrides the stylesheet in ways that are hard to undo.

03

Falling behind in a compressed course. Four to six weeks means a missed week is a quarter of the course, not a tenth.

04

Treating pass/fail as a low bar. There is no distinction band, but the pass standard is still a standard, and the timeline to reach it is short.

Teaching team

Who teaches COSC3044

The bios below are factual. We do not rate lecturers; any star ratings are submitted by students who have taken COSC3044.

Course Coordinator

Gayan Wijesinghe

Student ratingNo student ratings yet

Teaching team as listed in public course information. AskSia does not rate lecturers; star ratings are submitted by students who have taken COSC3044.

Formula & concept sheet

The vocabulary and formulas you must own

HTTP
The request-response protocol the web is built on.
HTML
The markup language giving a document its structure and meaning.
CSS
The language controlling presentation, kept separate from structure by design.
JavaScript
The language adding behaviour to a page in the browser.
Document object model
The in-memory tree representing a page, through which scripts read and change it.
Event listener
A function registered to run when a particular interaction occurs.
Separation of concerns
Keeping structure, presentation and behaviour in their own layers; the organising principle of the course.
Responsive design
Building a layout that adapts to varying screen sizes and devices.
Accessibility
Designing so that people using assistive technology can use the page.
Client-side and server-side
Code running in the browser versus code running on the server.
Semantic markup
Choosing HTML elements for their meaning rather than their default appearance.
Pass or fail grading
This course's published grading basis: a threshold to meet, with no graded distinction band.

Common acronyms: CSS · CLO · DOM · HTML · HTTP.

Where it fits

Prerequisites, related units & why it matters

Recommended prior study published by RMIT: COSC2801 Java Programming Bootcamp and COSC2803 Java Programming Studio — recommended rather than enforced. Worth 12 credit points at City Campus, delivered face to face in bootcamp mode over four to six weeks. It is a prerequisite for more specialised courses requiring web programming.

Why it matters beyond the grade. Client-side web programming is the most immediately visible skill in a computing degree and among the most directly employable. The specific habit this course builds — keeping structure, presentation and behaviour separate — is what makes a codebase survivable once more than one person works on it.

FAQ

Frequently asked questions

Is COSC3044 hard?

It rates moderate, and it is the least risky course in this network. RMIT awards a pass or fail mark only and publishes no hurdle requirements, so there is no distinction band to chase. The real demand is pace: the whole course runs in a four to six week bootcamp.

What is the assessment breakdown?

For the Melbourne version: self-directed progress checking activities 10%, Programming Challenge 1 (HTML and CSS) 20%, Programming Challenge 2 30%, Programming Challenge 3 40%. The Vietnam version uses a different split, which does not apply at City Campus.

Is it really pass or fail?

Yes. RMIT states plainly that this course awards a pass or fail mark only, and that it has no hurdle requirements.

What do I need before taking it?

COSC2801 Java Programming Bootcamp and COSC2803 Java Programming Studio are recommended, not enforced. You are expected to have Programming Bootcamp 1 behind you.

What is bootcamp mode?

RMIT defines it as a focussed mode teaching approach based around workshops over four to six weeks, mixing self-directed online material with timetabled face-to-face sessions. You will need your own laptop.

What does it lead to?

the description states it serves as a prerequisite for more specialised courses that require web programming.

Study COSC3044 with Sia

Work through the world wide web, web protocols, html and the rest of the unit with a tutor that knows it and quizzes you on the topics the assessments weight most heavily.

Start studying with Sia