SDD Marathon v1 (1 Viewer)

[MarsBarz]

Simple. Post the solution to the question above you and ask a new question. It'd be a good idea to provide a solution for your question as well after someone else has attempted it to make sure that their solution is correct.

I'll start it off.

1. Outline the three levels of testing software programs.

 

[aaaman]

make the question specific since the coarse itself is very broad...fool

 

[Casmira]

The questions asked are rarely specific, usually broad so as to test who utilises the most correct syllabus dot points.

For example a case scenario where a team of programmers steal code and its asked to "Discuss Social and Ethical Issues in this scenario", you could mention viruses because it is part of the syllabus, but it's not the right one too. Instead you talk about Copyright, acknowledgement etc..

However they do sometimes ask "Discuss the feasibility study" or "Describe the technical feasibility of this solution"- usually those questions aren't worth as much.

 

[rn21]

program testing
unit or module testing
system testing

Next question

Name and describe the steps of the fetch-execute cycle

 

[Ghost1788]

program testing
unit or module testing
system testing

Outline - skitch in general terms, indicate main features of...

all you have done is identify

 

[MarsBarz]

Some of you guys are hopeless haha...

It is true that they generally ask very broad questions (although some questions can get pretty specific, ie: 2002 option1).

Anyway, if you're able to answer the specific questions, you'll be fine with the broad ones.

 

[sunny]

Most questions are scenario based, and will require you to apply knowledge to the particular scenario. Specific questions that only require rot learning aren't common - sometimes people can recall every detail about the development cycle but can't apply it to a scenario because they've never practiced it.