It's UWAweek 48

help2200

This forum is provided to promote discussion amongst students enrolled in CITS2200 Data Structures and Algorithms.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 2 articles in this topic
Showing 2 of 176 articles.
Currently 5 other people reading this forum.


 UWA week 22 (1st semester, study break) ↓
SVG not supported

Login to reply

👍x1
helpful
6:17pm Sun 2nd Jun, ANONYMOUS

Hi, I was just wondering for exam questions that require us to explain the time complexity, should we explain just how the dominant term is reached or the time complexity for the entire algorithm? For example, if an algorithm takes an overall time of 'n + n^2', can we just explain why the algorithm is O(n^2) or do we have to describe all parts of the algorithm including the 'n' time? Apologies if that doesn't make sense or has been answered elsewhere. Any help would be much appreciated. Thanks.


 UWA week 23 (1st semester, 1st exam week) ↓
SVG not supported

Login to reply

👍?
helpful
3:05pm Mon 3rd Jun, Amitava D.

ANONYMOUS wrote:
> Hi, > > I was just wondering for exam questions that require us to explain the time complexity, should we explain just how the dominant term is reached or the time complexity for the entire algorithm? > > For example, if an algorithm takes an overall time of 'n + n^2', can we just explain why the algorithm is O(n^2) or do we have to describe all parts of the algorithm including the 'n' time? > > > > Apologies if that doesn't make sense or has been answered elsewhere. Any help would be much appreciated. > > > Thanks.
You should analyse the time complexities of all parts of an algorithm. The analysis of non-dominant parts will cost you (may be) two more sentences and half a minute of writing.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy