Search Header Logo

Software Development Quiz

Authored by Nivya Vineeth

Professional Development

Professional Development

Used 1+ times

Software Development Quiz
AI

AI Actions

Add similar questions

Adjust reading levels

Convert to real-world scenario

Translate activity

More...

    Content View

    Student View

23 questions

Show all answers

1.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

The real purpose of commenting is to explain

What the code does

Why the code is present

To make the code feel more readable

There is no specific purpose

2.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

What are the techniques to be liked in the workplace?

Greet people with Hi/Hello instead of names as it may seem rude

Do not always reach out to help others as it may seem you are always available and people might take advantage of you

Ask for others help as it builds comradery

It's ok to respond with 'I don't know' or 'It's not my job' to a coworkers question as it shows you are being real.

3.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

In SDLC which step comes immediately after the Development step?

Analysis

Deployment

Testing

Maintenence

4.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

Which one of the following tests customer facing functionality?

Unit testing

Integration testing

Software testing

Acceptance testing

5.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

What is one of the main warning signs of bad coding style according to Phil Copeman's tutorial?

The code is well-commented.

The code passes all tests but is difficult to understand.

The code is modular and organized.

The code uses consistent naming conventions.

6.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

Which of the following practices is recommended to improve code readability?

Using magic numbers directly in the code.

Writing comments that paraphrase the code.

Following consistent formatting and naming conventions.

Making the code as clever as possible to showcase programming skills.

7.

MULTIPLE CHOICE QUESTION

1 min • 1 pt

What is a key characteristic of a good software requirement?

It includes implementation details.

It is ambiguous and vague.

It is traceable and testable.

It is overly complex and wordy.

Access all questions and much more by creating a free account

Create resources

Host any resource

Get auto-graded reports

Google

Continue with Google

Email

Continue with Email

Classlink

Continue with Classlink

Clever

Continue with Clever

or continue with

Microsoft

Microsoft

Apple

Apple

Others

Others

Already have an account?

Discover more resources for Professional Development