Please do the following questions in one sitting, without consulting anyone else or looking anything up, and press submit just once. (Feel free to discuss it after you've done it, with anyone else who either isn't on the course or has already done it, of course.)

Note that I do not get any information that will identify you, unless you choose to give it in the comment box: I'm interested in refining my understanding of what I can and can't assume in this course, not in assessing you as an individual.

Don't worry if you can't do all the questions; they are a mixture of things I expect you to know, things I don't expect you to know (but if it turns out that lots of you do know them, I will revise how I deliver parts of the course accordingly!) and areas where I'm just curious.

I'll make some comments, and correct answers where applicable, available next week.

Answer the following questions in roughly one sentence each:

  1. What does "statically typed" mean?

  2. In software engineering, what is encapsulation?

  3. Why is it important?

  4. Suppose you're considering whether a Java class that you plan to write (call it T) should be a subclass of an existing class (call it S), or not.
    1. What are the advantages of making it a subclass?

    2. What are the disadvantages?

    3. What's the main thing you should ask yourself, in order to decide?

  5. In object oriented programming, what is polymorphism?

  6. For these, please explain as many features of the diagrams as you understand (but you needn't explain the same feature more than once: I'm interested in which diagram elements you remember the meaning of).

    What kind of diagram is this, and what does it mean?
    diagram 1

  7. And this one?
    diagram 2

  8. In the topic diagram, which three topics do you know most about right now?

  9. Which three are you most interested in learning about?

  10. To what extent do you agree with each of the following statements? (I know, they could all be answered with "it's more complicated than that": just go with your gut. Remember I don't know who you are; be honest!)

    I feel well prepared for this course
    Strongly agree Agree Disagree Strongly disagree

    I am looking forward to this course
    Strongly agree Agree Disagree Strongly disagree

    I have chosen this course because I expect it to be easy
    Strongly agree Agree Disagree Strongly disagree

    I am well organised when it comes to work
    Strongly agree Agree Disagree Strongly disagree

    When I succeed, it is because I work hard
    Strongly agree Agree Disagree Strongly disagree

    When I succeed, it is because I am clever
    Strongly agree Agree Disagree Strongly disagree

    I expect software development to be part of what I do after university
    Strongly agree Agree Disagree Strongly disagree

    I am confident programming in Java
    Strongly agree Agree Disagree Strongly disagree

  11. Now think about the largest software system you've ever worked on.

    Roughly how big was it, in lines of code (written by humans, i.e. ignore generated code)?
    Under 1000
    Over 1,000,000

    Besides you, what was the largest number of people you ever knew to work on it (in software development) simultaneously?
    0 - it was just me
    Over 100

    How long were you (or have you been so far) involved in it?
    less than three weeks
    more than three weeks, less than three months
    more than three months, less than one year
    more than one year, less than five years
    more than five years

  12. Any comments? Anything you're concerned about, or would like me to know about your hopes for this course? (If you'd like an answer from me, either put your email address in this box, or mail me separately instead of writing here.)

Thank you!

This page is maintained by Perdita Stevens (

Home : Teaching : Courses : Seoc : 2015_2016 : Preassessment 

Informatics Forum, 10 Crichton Street, Edinburgh, EH8 9AB, Scotland, UK
Tel: +44 131 651 5661, Fax: +44 131 651 1426, E-mail:
Please contact our webadmin with any comments or corrections. Logging and Cookies
Unless explicitly stated otherwise, all material is copyright © The University of Edinburgh