IB Computer Science Dossiers Projects HL/ SL Help Tutors Examples Samples Solution Writers Internal Assessment IA Task

FOR IMMEDIATE RELEASE
South delhi, Delhi, India, Republic of (Free-Press-Release.com) February 5, 2012 -- IB COMPUTER SCIENCE: The Program Dossier
IB Computer Science Dossiers Projects HL/ SL Help Tutors Examples Samples Solution Writers Internal Assessment IA Task:
Introduction

The program dossier is an individual piece of work completed during the course. It must address a single problem that can be solved using computer systems and which has an identified end- user. Your analysis, design and production of the final system must be well documented. You must use a logical approach and analytical thinking, from definition and decomposition of the problem through to its solution by constructing appropriate classes implementing algorithms and data structures in Java. The dossier is internally assessed by RJo and externally moderated by the IBO.
Time allowed

Times quoted here are recommended teacher contact time and do not include the time required by you to work on your own to develop and complete your dossier:

Standard level - 25 hours;
Higher level - 35 hours.

Choice of problem

Avoid overly ambitious problems;
avoid overly simplistic ones;
you are free to choose a problem generated by yourself or RJo;
the problem must have an identified end-user;

you may share the same problem to be solved or the same initial scenario, but collaborative work is forbidden;
we will review the prototype fully together to ensure that the user's requirements can be met within your programming abilities and within the time available;
we will also review whether you can achieve a suitable number of skill mastery points from the project.

Approach

The work on your dossier falls into four main stages:

Analysis (completed by end of spring term Y12)
Detailed design (completed by end of summer term Y12)
The program (completed by end of automn term Y13)

Documentation (completed by half term of spring term Y13).

You will complete these stages in order, although it may occasionally be necessary for you to return from (c) to (b) one or more times to refine your detailed design in a spiral of design and development (this will depend on the nature of your problem, open or closed). You are free to choose your design methodology (structured, top-down or object-oriented), try to choose one that is flexible and extensible. Retain design documentation from earlier stages to present as evidence in the final dossier. The rough deadlines given will vary from year to year.
Format

All work must be submitted together as a single document;
the work can be stapled, put into a ring-binder or inserted into a folder;
all information required for the program dossier must appear as hard copy (CD-ROM's etc. must not be included within the program dossier;
there must be a table of contents
all written documentation should be word processed, except where it is felt necessary to include rough notes
program runs and sample screens may be annotated by hand
all the pages must be numbered either sequentially or by section (3–1, 3–2, 3–3, etc.);

the number of pages associated with each item may vary according to the problem, but guidance can be found in the program dossier template document.

Program dossier templete >>
Assessment criteria

You are assessed against criteria, not against each other.

Analysis
Analysing the problem
A thorough discussion of the problem that is being solved. You should concentrate on the problem and the goals that are being set, not on the method of solution. A good analysis includes information such as sample data, information and requests from the identified end-user, and possibly some background of how the problem has been solved in the past.

This section of the program dossier would typically be two to three pages in length. It should include a brief statement of the problem as seen by the end-user. A discussion of the problem from the end-user’s point of view should take place, including the user’s needs, required input and required output. For example, evidence could be sample data, interviews and so on, and could be placed in an appendix.
Criteria for success
Cclearly state the objectives/goals of the solution to the problem.
This section would typically be one to two pages in length. Objectives should include minimum performance and usability. These criteria for success will be referred to in subsequent criteria, for example criterion C3 (Success of the program) and D2 (Evaluating solutions).
Prototype solution

The prototype solution must be preceded by an initial design for some of the main objectives that were determined to be the criteria for success. A prototype of the solution should be created. A prototype is the construction of a simple version of the solution that is used as part of the design process to demonstrate how the system will work. The prototype need not be functional, it could be constructed using a number of tools such as presentation software (e.g. PowerPoint), mind mapping or other graphics application for a simple Java program. The intent is to show the user how the system is expected to operate, what inputs are required and what outputs will be produced. A number of screenshots will be required for the user to be able to evaluate the solution properly. The prototype, at its simplest, could be a series of clear, computer-generated drawings, a hierarchical outline of features in text mode, or a series of screenshots. Documentation of user feedback could be, for example, a report of the user’s comments on the prototype.
Detailed design
Data structures

You should choose data structures, at the design stage, that fully support the data-storage requirements of the problem, and that allow clear, efficient algorithms to be written. The data structures must fully support the objectives of the solution (criterion A2). The classes chosen should be logical in that the data is sensible for the objects in question and the methods are appropriate for the data given. This section of the program dossier could include class definitions, file structures, abstract data types (particularly at higher level) and some consideration of alternatives.
This section would typically be two to five pages in length. Data structures and data members that are to be used in the programmed solution should be discussed here. Sample data, sketches/illustrations, including discussion of the way data objects will be changed during program execution should be demonstrated to achieve a level 3 in criterion B1.
Algorithms

You should choose algorithms, at the design stage, that fully support the processes needed to achieve the objectives of the solution (criterion A2), and provide sufficient support for the required data structures. The classes chosen should be logical in that the methods are appropriate for the data given. You must include parameters and return values.
This section would typically be two to five pages in length. It can be a list or outline of all the algorithms, presented as text, possibly in outline format. Standard algorithms (such as search or sort) can simply be named (with parameters), but non-standard algorithms must be described in more detail.
Modular organization

You should choose modules, at the design stage, that incorporate the data structures and methods required for the solution (criteria B1 and B2) in a logical way. The data structures must fully support the objectives of the solution (criterion A2). You must present this organization in a structured way that clearly shows connections between modules (hierarchical decomposition or class dependencies). The connections between modules, algorithms and data structures must also be presented.
This section would typically be three to five pages in length. A variety of presentations are possible here. Some possibilities are:
a top-down hierarchical decomposition chart containing the names of modules, showing connections between modules and showing details of which data structures and methods are connected with (or part of) which modules;
a text outline showing hierarchical decomposition (equivalent to above)

a hard copy of CRC cards showing dependencies between collaborating classes, with details of which data structures and methods are connected with (or part of) which classes.

The design is assessed independently from the programming stage (stage C). The design should be complete, logical and usable, but you may deviate from it or expand it during stage (c), without penalty.
The program
Using good programming style

Program listings must contain all the code written by you and, if a program listing displays code that was automatically generated by the development system or copied from another source, then this code must be clearly identified and distinguishable from that code written by you. Only the code designed and written by you can be taken into account.
Good programming style can be demonstrated by program listings that are easily readable, even by a programmer who has never used the program. These would include small and clearly structured Java methods, sufficient and appropriate comments, meaningful identifier names and a consistent indentation scheme.

A typical program should be approximately 1,000–3,000 (HL) or 500–2,000 (SL) lines of code in length. Comments should be included to describe the purpose and parameters of each method, and also when code is difficult to understand. The program should demonstrate the use of good programming techniques. It should include:
an identification header indicating the program name;
author, date, schoo;
computer used, IDE used, purpose.

The program should possess good internal documentation, including:
constant, type and variable declarations that should have

computer dossier examples     computer dossier ia help     computer dossier samples     computer science dossier hl sl     computer science dossier tutor     ib computer dossier help     ib computer dossier projects     ib computer science dossier