DP Computer Science Handbook HL & SL

Diploma Programme computer science students should become aware of how computer scientists work and communicate with each other and with other stakeholders in the successful development and implementation of IT solutions. While the methodology used to solve problems in computer science may take a wide variety of forms, the group 4 computer science course emphasizes the need for both a theoretical and practical approach.

 It is in this context that the Diploma Programme computer science course should aim to: 

1. provide opportunities for study and creativity within a global context that will stimulate and challenge students developing the skills necessary for independent and lifelong learning 

2. provide a body of knowledge, methods and techniques that characterize computer science 

3. enable students to apply and use a body of knowledge, methods and techniques that characterize computer science 

4. demonstrate initiative in applying thinking skills critically to identify and resolve complex problems

 5. engender an awareness of the need for, and the value of, effective collaboration and communication in resolving complex problems 

6. develop logical and critical thinking as well as experimental, investigative and problem-solving skills 

7. develop and apply the students’ information and communication technology skills in the study of computer science to communicate information confidently and effectively 

8. raise awareness of the moral, ethical, social, economic and environmental implications of using science and technology 

9. develop an appreciation of the possibilities and limitations associated with continued developments in IT systems and computer science 

10. encourage an understanding of the relationships between scientific disciplines and the overarching nature of the scientific method. 

The objectives for all group 4 subjects reflect those parts of the aims that will be assessed. Wherever appropriate, the assessment will draw upon a range of contexts and identify the social, moral and economic effects of science and technology.

 It is the intention of the Diploma Programme computer science course that students achieve the following objectives :

1. Know and understand: 

a. relevant facts and concepts 

b. appropriate methods and techniques 

c. computer science terminology 

d. methods of presenting information 

2. Apply and use: 

a. relevant facts and concepts 

b. relevant design methods and techniques 

c. terminology to communicate effectively 

d. appropriate communication methods to present information. 

3. Construct, analyse, evaluate and formulate: 

a. success criteria, solution specifications including task outlines, designs and test plans 

b. appropriate techniques within a specified solution. 

4. Demonstrate the personal skills of cooperation and perseverance as well as appropriate technical skills for effective problem-solving in developing a specified product. 

Core Computer Science -  KOSTAS DIMITRIOU  & MARKOS HATZITASKOS 

Advanced Computer Science - KOSTAS DIMITRIOU  & MARKOS HATZITASKOS 

Paper 1

Duration: 1 hour 30 minutes

Maximum mark: 70

Weighting: 45%

The purpose of the paper is to assess the student’s ability to demonstrate the following objectives in relation to the syllabus:

• Assessment objective 1—know and understand

• Assessment objective 2—apply and use

• Assessment objective 3—construct, analyse and evaluate

Section A (30 minutes approximately) consists of several compulsory short answer questions testing mainly objectives 1 and 2. The maximum mark for this section is 25. Some of the questions are common to this paper and HL paper 1, section A.

Section B (60 minutes approximately) consists of three compulsory structured questions that may be subdivided. The maximum mark for this section is 45. Some questions may be common to this paper and HL paper 1, section B.

The number of marks for each part will be given on the paper, and is linked to the command term used. This will indicate to students the depth of the response required.

Paper 2

Duration: 1 hour

Maximum mark: 45

Weighting: 25%

The purpose of the paper is to assess the student’s ability to demonstrate the following objectives in relation to the option chosen:

• Assessment objective 1—know and understand

• Assessment objective 2—apply and use

• Assessment objective 3—construct, analyse and evaluate

Students are required to answer all the questions for the option chosen. The questions are common to this paper and HL paper 2, section A.

Students are not expected to construct code in the following options:

• databases

• modelling and simulation

• web science.

Students will be expected to interpret and/or construct code in Java in the OOP option.

Paper 1

Duration: 2 hours 10 minutes

Maximum mark: 100

Weighting: 40%

The purpose of the paper is to assess the student’s ability to demonstrate the following objectives in relation to the syllabus:

•  Assessment objective 1—know and understand

• Assessment objective 2—apply and use

• Assessment objective 3—construct, analyse and evaluate

Section A (30 minutes approximately) consists of several compulsory short answer questions testing mainly objectives 1 and 2. The maximum mark for this section is 25. Some of the questions are common to this paper and SL paper 1, section A.

Section B (100 minutes approximately) consists of five compulsory structured questions that may be subdivided. The maximum mark for this section is 75. Some questions may be common to this paper and SL paper 1, section B.

The number of marks for each part will be given on the paper, and is linked to the command term used. This will indicate to students the depth of the response required.

Paper 2

Duration: 1 hour 20 minutes

Maximum mark: 65

Weighting: 20%

The purpose of the paper is to assess the student’s ability to demonstrate the following objectives in relation to the option chosen:

•  Assessment objective 1—know and understand

•  Assessment objective 2—apply and use

• Assessment objective 3—construct, analyse and evaluate

Section A consists of common questions (to the SL/HL core) for the option chosen. The maximum mark is 45. Section B consists of questions for the option chosen relating to the HL extension. The maximum mark is 20. Students are not expected to construct code in the following options:

•  databases

• modelling and simulation

• web science.

Students will be expected to interpret and/or construct code in Java in the OOP option.

Paper 3

Duration: 1 hour

Maximum mark: 30

Weighting: 20%

This paper is based on a case study produced annually by the IB and available on the OCC.

A clean copy of the case study must be downloaded by the IB coordinator and issued to the students with their examination paper.

The purpose of the paper is to assess the student’s ability to demonstrate the following objectives in relation to the syllabus:

•  Assessment objective 1—know and understand

• Assessment objective 2—apply and use

• Assessment objective 3—construct, analyse, evaluate and formulate

This paper consists of four structured questions, which assess the whole syllabus in an integrated way. Students are required to answer all of the questions. The questions are related to the scenario in the case study. In addition to the case study further stimulus material may be provided in the examination paper.

Questions 1, 2 and 3 may be subdivided. Question 4 will require the synthesis of information from a range of sources, including independent research and investigations beyond the case study, to develop an extended response to a specified issue.

The number of marks for each part will be given on the paper, and is linked to the command term used. This will indicate to students the depth of the response required.

The Case study

The case study is a valuable teaching tool that can be used to integrate all aspects of the syllabus.

This case study will be provided 12 months before the May examination session (18 months before the November session) so that students can carry out detailed research prior to the HL paper 3 examination, which contributes 20% of the final mark.

The computer science case study provides the stimulus material for the investigation of a scenario involving current developments and/or issues in computer science. The information obtained will prepare students and form the basis of the requirements for answering the questions in HL paper 3. The case study is an opportunity to keep the course abreast of current technology by introducing new technical concepts or issues requiring a more in-depth investigation than that required in the rest of the course.

Through their investigation of the case study, students should be able to:

•  demonstrate an understanding of the computer science concepts fundamental to the system(s) in the case study (objective 1)

•   demonstrate an understanding of how the system(s) in the case study work (objective 1)

•  apply material from the course syllabus in the context of the case study (objective 2)

•  explain how scenarios specified in the case study may be related to other similar local and global scenarios (objective 3)

•  discuss the social impacts and ethical issues relevant to the case study (objective 3)

•  explain technical issues relating to the case study (objective 3)

•  evaluate information that may be gathered from local and global sources including field trips, interviews, primary and secondary research, invited guest speakers and online interviews (objective 3)

• evaluate, formulate or justify strategic solutions based on the synthesis of information from the case study itself, additional research and new stimulus material provided in the examination paper (objective 3).

Solution

Duration: 30 hours Weighting at SL: 30% Weighting at HL: 20%

Introduction

The requirement of the internal assessment is to develop a solution for a specified client to a specified problem or an unanswered question.

The solution is assessed using five criteria.

• Planning

• Solution overview

• Development

• Functionality and extensibility of product

•  Evaluation

 Key terms

The term “solution” refers to all the work submitted by the student for the internal assessment; the term “product” refers to the completed software only. The product is a subset of the solution.

The terms “developer” and “student” are synonymous.

The term “client” refers to the person for whom the product is being developed. The student may also be the client.

The term “adviser” refers to a third party the student must identify to assist him or her in the development of the product.

There are three scenarios for the development of the product.

1.      The student is developing the product for a third party who is the client and also acts as the adviser.

2.       The student is developing the product for a third party who is the client. Another person acts as the adviser.

3.       The student is the client (developing the product for himself or herself). An appropriate adult must act as the adviser.

Choice of topic

In identifying a problem, students can select any topic that interests them. It does not have to be directly related to the specified themes in the syllabus or to the option studied.

Students should undertake a challenging task using appropriate techniques to showcase their algorithmic thinking and organizational skills.

The solution may take one of these forms:

• Creating a new system, such as an OOP program, a relational database, a simulation or a stand-alone/ web-based application

• Adding functionality to an existing system, such as connecting a webpage(s) to a database, writing a function for Moodle, writing a plug-in, or developing a stand-alone application. It is essential that whatever form the solution takes it ensures the student can explicitly demonstrate and document his or her algorithmic thinking skills.

Examples are illustrated in the teacher support material.

It should be noted that products created using templates that show no evidence of modification in their structure, design or functionality are not permitted. Examples of inappropriate products include:

•  the development of a programming product only using copied code

•  the development of a website (product) using a web-based template that determines its structure and layout

• the use of unmodified exemplar products or templates provided with software such as the Northwind database in MS Access

• a product that does not meet the ethical requirements outlined in the “Requirements and recommendations” section of this document.

Choice of adviser

Students will need to work closely with the adviser throughout the development of the solution. Therefore it is recommended that wherever possible, students select an adviser who is known to them or their family. This could include members of the school community, local clubs or businesses.

Requirements

The internal assessment consists of three parts:

1.        A cover page

–        The cover page form to be used is included in HTML format within the zip file available on the OCC.

–        The cover page must be submitted in HTML format and should provide access to the product and associated documentation via relative   

            hyperlinks.

–        The cover page is not included in the overall word count for the project, nor is its functionality assessed.

–        Information to access or locate the product, for example, a username and password, must be provided in the cell on the cover page.

–        The cover page must be called [cand_no]_[cand_name]_CoverPage.htm and be located in the top level folder.

2.       The product

3.       The documentation including a video

3.1   The video must be in a commonly used format such as .avi or .wmv. All three of these must be submitted digitally for moderation.

Instructions for the submission of student work can be found in the Handbook of procedures for the Diploma Programme.

Documentation

This information must be read in conjunction with that in the “Organization of documentation” section.

A zip file is available on the OCC that contains the cover page and templates required for submitting the solution.

The final documentation consists of:

Information added to the Record of tasks form and in the information linked to the design overview

The information added must be in the following style(s):

• bullet points or tables to list information

• scanned diagrams or other appropriate images as part of the design process

• other styles of non-extended writing or diagrammatic representation such as flow charts, Gantt charts or spider diagrams where appropriate.

• If the student includes extended writing, the words will be included in the word count and the student will self-penalize if the total number of words in the documentation exceeds 2,000.